Difference between revisions of "HowTo:Edit Missions:Python:Summary"
| Line 16: | Line 16: | ||
| previous=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]] | | previous=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]] | ||
| up=[[HowTo:Edit_Missions|Edit Missions]] | | up=[[HowTo:Edit_Missions|Edit Missions]] | ||
| − | | next=[[HowTo:Edit_Missions:Writing_addon_adventures|Writing AddOn | + | | next=[[HowTo:Edit_Missions:Writing_addon_adventures|Writing AddOn Adventures]] |
}} | }} | ||
Revision as of 07:46, 21 March 2005
 Python Bindings
|
 Edit Missions
|
Writing AddOn Adventures 
|
- Missions must inherit from Director.Mission
- AI's must inherit from VS.PythonAI
- Missions must have an __init__ function with any number of arguments that calls Director.Mission.__init__ (self); to trigger the C++ binding
- AI's must have an init(self, un) function with those exact 2 arguments... the second one is the parent Unit. I don't recommend you save the unit currently--I'm not sure if it will garbage collect the unit in that case... just call the self.GetParent() function as the AI script.
- Both AI's and Missions may have an Execute(self) function that does somethign each frame depending on the disired result.
- Missions may have a Pickle and Unpickle function in order to save and load the state of a campaign (this can be incredibly complex!)
| Python Bindings
|
Edit Missions
|
Writing AddOn Adventures
|
