Difference between revisions of "Development:Missions"

From VsWiki
Jump to: navigation, search
m (EDITING MISSIONS)
m (Conclusions)
Line 26: Line 26:
 
===Conclusions===
 
===Conclusions===
 
Well this is the best I can do so far. Please read this documentation over and let me know if you have any suggestions or clarifications. And best yet give it a shot and try it out. And at least look at  
 
Well this is the best I can do so far. Please read this documentation over and let me know if you have any suggestions or clarifications. And best yet give it a shot and try it out. And at least look at  
'''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/cargo_mission.py?rev=HEAD&content-type=text/vnd.viewcvs-markup modules/cargo_mission.py]''' (which is called from a number of missions I think) as well as '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/privateer.py?rev=HEAD&content-type=text/vnd.viewcvs-markup modules/privateer.py]''' called by '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/mission/explore_universe.mission?rev=HEAD&content-type=text/vnd.viewcvs-markup mission/explore_universe.mission]''' And certainly try to understand '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/quest_drone.py?rev=HEAD&content-type=text/vnd.viewcvs-markup modules/quest_drone.py]''' before trying to write a quest (or while trying to write one)
+
'''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data4.x/modules/cargo_mission.py?view=markup modules/cargo_mission.py]''' (which is called from a number of missions I think) as well as '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data4.x/modules/privateer.py?view=markup modules/privateer.py]''' called by '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data4.x/mission/explore_universe.mission?view=markup mission/explore_universe.mission]'''. And certainly try to understand '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data4.x/modules/quest_drone.py?view=markup modules/quest_drone.py]''' before trying to write a quest (or while trying to write one).
 +
 
 +
Please also have a look in [[Development:Quests]] for a detailed explanation on the structure of quests and an explanation on how they work.
  
 
==See also==
 
==See also==

Revision as of 14:06, 21 April 2008

arrow_left.png Edit relationships arrow_up.png HowTos Edit News arrow_right.png

EDITING MISSIONS

Introduction

Vega Strike has a powerful missions scripting interface that allows you to nearly modify Vega Strike at whatever level you choose, from the AI scripts (and the physics thereof) to the missions... to the overall plot and goal of the game.

Basic XML integration

Python Inheritance In Missions

Python Inheritance with AI Scripts

Python - Vega Strike Bindings

Summary about python-Vegastrike class relationships

Sample Missions

Conclusions

Well this is the best I can do so far. Please read this documentation over and let me know if you have any suggestions or clarifications. And best yet give it a shot and try it out. And at least look at modules/cargo_mission.py (which is called from a number of missions I think) as well as modules/privateer.py called by mission/explore_universe.mission. And certainly try to understand modules/quest_drone.py before trying to write a quest (or while trying to write one).

Please also have a look in Development:Quests for a detailed explanation on the structure of quests and an explanation on how they work.

See also


arrow_left.png Edit relationships arrow_up.png HowTos Edit News arrow_right.png