Difference between revisions of "HowTo:Edit Missions:Python:Summary"
m |
m |
||
| Line 2: | Line 2: | ||
| previous=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]] | | previous=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]] | ||
| up=[[Development:Missions|Edit Missions]] | | up=[[Development:Missions|Edit Missions]] | ||
| − | | next=[[ | + | | next=[[Development:Quests & Campaigns|Quests & Campaigns]] |
}} | }} | ||
---- | ---- | ||
| Line 16: | Line 16: | ||
| previous=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]] | | previous=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]] | ||
| up=[[Development:Missions|Edit Missions]] | | up=[[Development:Missions|Edit Missions]] | ||
| − | | next=[[ | + | | next=[[Development:Quests & Campaigns|Quests & Campaigns]] |
}} | }} | ||
[[Category:HowTos|Edit Missions:Python:Summary]] | [[Category:HowTos|Edit Missions:Python:Summary]] | ||
[[Category:Development|Edit Missions:Python:Summary]] | [[Category:Development|Edit Missions:Python:Summary]] | ||
Revision as of 13:08, 21 April 2008
 Python Bindings
|
 Edit Missions
|
Quests & Campaigns 
|
- 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 callsDirector.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 parentUnit. 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 theself.GetParent()function as the AI script. - Both AI's and Missions may have an
Execute(self)function that does something each frame depending on the disired result. - Missions may have a
PickleandUnpicklefunction in order to save and load the state of a campaign (this can be incredibly complex!)
| Python Bindings
|
Edit Missions
|
Quests & Campaigns
|
