Difference between revisions of "Development:Missions"
(→See also) |
|||
| Line 28: | Line 28: | ||
==See also== | ==See also== | ||
| − | + | * [[HowTo:Edit_Missions:Samples]] | |
| − | * [[HowTo:Edit_Missions: | + | * [[HowTo:Edit_News]] |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | * [[HowTo: | ||
| − | |||
| − | |||
Revision as of 06:38, 21 March 2005
 Add Conversation
|
 HowTo
|
Edit News 
|
Contents
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
Writing Add On Adventures
Conclusion
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/exploration/explore_universe.mission) And certainly try to understand modules/quest_drone.py before trying to write a quest (or while trying to write one)
See also
| Add Conversation
|
HowTo
|
Edit News
|
