HowTo:Edit Missions:Python:Summary - Revision history

pyramid at 14:03, 21 April 2008

2008-04-21T14:03:25Z

pyramid at 11:08, 21 April 2008

2008-04-21T11:08:15Z

pyramid at 09:08, 21 April 2008

2008-04-21T09:08:24Z

Pirx at 18:22, 28 May 2005

2005-05-28T18:22:01Z

Pirx: added categories

2005-03-21T15:24:37Z

added categories

202.50.187.13 at 05:46, 21 March 2005

2005-03-21T05:46:01Z

202.50.187.13 at 05:45, 21 March 2005

2005-03-21T05:45:26Z

202.50.187.13 at 05:20, 21 March 2005

2005-03-21T05:20:41Z

New page

{{NAV_Manual |
| previous=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]]
| up=[[HowTo:Edit_Missions|Edit Missions]]
| next=[[HowTo:Edit_Missions:Python:Bindings]]
}}
----

* 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!)
----
{{NAV_Manual |
| previous=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]]
| up=[[HowTo:Edit_Missions|Edit Missions]]
| next=[[HowTo:Edit_Missions:Python:Bindings]]
}}

@@ Line 1: / Line 1: @@
 * Missions must inherit from <code>Director.Mission</code>
@@ Line 12: / Line 6: @@
 * Both AI's and Missions may have an <code>Execute(self)</code> function that does something each frame depending on the disired result.
 * Missions may have a <code>Pickle</code> and <code>Unpickle</code> function in order to save and load the state of a campaign (this can be incredibly complex!)
-----
 [[Category:HowTos|Edit Missions:Python:Summary]]
 [[Category:Development|Edit Missions:Python:Summary]]

@@ Line 2: / Line 2: @@
 | previous=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]]
 | up=[[Development:Missions|Edit Missions]]
-| next=[[HowTo:Edit_Missions:Writing_addon_adventures|Writing AddOn Adventures]]
+| next=[[Development:Quests & Campaigns|Quests & Campaigns]]
 }}
 ----
@@ Line 16: / Line 16: @@
 | previous=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]]
 | up=[[Development:Missions|Edit Missions]]
-| next=[[HowTo:Edit_Missions:Writing_addon_adventures|Writing AddOn Adventures]]
+| next=[[Development:Quests & Campaigns|Quests & Campaigns]]
 }}
 [[Category:HowTos|Edit Missions:Python:Summary]]
 [[Category:Development|Edit Missions:Python:Summary]]

@@ Line 1: / Line 1: @@
 {{NAV_Manual |
 | previous=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]]
-| up=[[HowTo:Edit_Missions|Edit Missions]]
+| up=[[Development:Missions|Edit Missions]]
 | next=[[HowTo:Edit_Missions:Writing_addon_adventures|Writing AddOn Adventures]]
 }}
@@ Line 15: / Line 15: @@
 {{NAV_Manual |
 | previous=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]]
-| up=[[HowTo:Edit_Missions|Edit Missions]]
+| up=[[Development:Missions|Edit Missions]]
 | next=[[HowTo:Edit_Missions:Writing_addon_adventures|Writing AddOn Adventures]]
 }}
 [[Category:HowTos|Edit Missions:Python:Summary]]
 [[Category:Development|Edit Missions:Python:Summary]]

@@ Line 6: / Line 6: @@
 ----
-* Missions must inherit from '''Director.Mission'''
+* Missions must inherit from <code>Director.Mission</code>
-* AI's must inherit from '''VS.PythonAI'''
+* AI's must inherit from <code>VS.PythonAI</code>
-* Missions must have an '''__init__ '''function with any number of arguments that calls '''Director.Mission.__init__ (self)'''; to trigger the C++ binding
+* Missions must have an <code>__init__</code> function with any number of arguments that calls <code>Director.Mission.__init__ (self);</code> 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.
+* AI's must have an <code>init(self, un)</code> function with those exact 2 arguments... the second one is the parent <code>Unit</code>. 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 <code>self.GetParent()</code> 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.
+* Both AI's and Missions may have an <code>Execute(self)</code> function that does something 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!)
+* Missions may have a <code>Pickle</code> and <code>Unpickle</code> function in order to save and load the state of a campaign (this can be incredibly complex!)
 ----
 {{NAV_Manual |
@@ Line 18: / Line 18: @@
 | next=[[HowTo:Edit_Missions:Writing_addon_adventures|Writing AddOn Adventures]]
 }}
-[[Category:HowTo|Edit Missions:Python:Summary]] [[Category:Development|Edit Missions:Python:Summary]]
+[[Category:HowTos|Edit Missions:Python:Summary]]

← Older revision		Revision as of 15:24, 21 March 2005
Line 18:		Line 18:
	\| next=[[HowTo:Edit_Missions:Writing_addon_adventures\|Writing AddOn Adventures]]		\| next=[[HowTo:Edit_Missions:Writing_addon_adventures\|Writing AddOn Adventures]]
	}}		}}
		+	[[Category:HowTo\|Edit Missions:Python:Summary]] [[Category:Development\|Edit Missions:Python:Summary]]