HowTo:Edit Missions:Python:Missions - Revision history

Nabaco: Replaced one SVN URL

2020-03-22T17:54:03Z

Replaced one SVN URL

pyramid at 13:45, 21 April 2008

2008-04-21T13:45:49Z

pyramid at 09:06, 21 April 2008

2008-04-21T09:06:48Z

Pirx at 18:24, 28 May 2005

2005-05-28T18:24:22Z

202.50.187.13 at 05:26, 23 March 2005

2005-03-23T05:26:28Z

202.50.187.13 at 05:22, 23 March 2005

2005-03-23T05:22:24Z

202.50.187.13 at 05:21, 23 March 2005

2005-03-23T05:21:58Z

202.50.187.13 at 05:15, 23 March 2005

2005-03-23T05:15:48Z

Pirx: added categories

2005-03-21T15:23:58Z

added categories

202.50.187.13 at 05:42, 21 March 2005

2005-03-21T05:42:43Z

@@ Line 1: / Line 1: @@
 ==Python Inheritance In Missions==
-Ok lets dig further into the <code>[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/privateer.py?rev=HEAD&content-type=text/vnd.viewcvs-markup privateer.py]</code> module:
+Ok lets dig further into the <code>[https://github.com/vegastrike/Assets-Production/blob/master/modules/missions/privateer.py privateer.py]</code> module:
 It is a very short module written in more or less pure python... I say more or less for a very specific reason: it inherits from a C++ class!

@@ Line 1: / Line 1: @@
 ==Python Inheritance In Missions==
@@ Line 59: / Line 52: @@
 With the exception of AI modules from here on out it's straight python. I will go over some of the functions you can call inside Vega Strike in a minute.
 [[Category:HowTos|Edit Missions:Python:Missions]]
 [[Category:Development|Edit Missions:Python:Missions]]

@@ Line 1: / Line 1: @@
 {{NAV_Manual |
 | previous=[[HowTo:Edit_Missions:XML_integration|XML Integration]]
-| up=[[HowTo:Edit_Missions|Editing Missions]]
+| up=[[Development:Missions|Editing Missions]]
 | next=[[HowTo:Edit_Missions:Python:AI_scripts|AI Scripts]]
 }}
@@ Line 62: / Line 62: @@
 {{NAV_Manual |
 | previous=[[HowTo:Edit_Missions:XML_integration|XML Integration]]
-| up=[[HowTo:Edit_Missions|Editing Missions]]
+| up=[[Development:Missions|Editing Missions]]
 | next=[[HowTo:Edit_Missions:Python:AI_scripts|AI Scripts]]
 }}
 [[Category:HowTos|Edit Missions:Python:Missions]]
 [[Category:Development|Edit Missions:Python:Missions]]

@@ Line 8: / Line 8: @@
 ==Python Inheritance In Missions==
-Ok lets dig further into the '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/privateer.py?rev=HEAD&content-type=text/vnd.viewcvs-markup privateer.py]''' module:
+Ok lets dig further into the <code>[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/privateer.py?rev=HEAD&content-type=text/vnd.viewcvs-markup privateer.py]</code> module:
 It is a very short module written in more or less pure python... I say more or less for a very specific reason: it inherits from a C++ class!
-Director is a C++ class exported to python. All missions must inherit from director.... in this case the mission is very short as it uses other (pure python) modules. random_encounters.random_encounters, difficulty.difficulty and ,trading.trading all do NOT inherit from C++ as this class takes care of the C++ inheritance.
+Director is a C++ class exported to python. All missions must inherit from director.... in this case the mission is very short as it uses other (pure python) modules. <code>random_encounters.random_encounters</code>, <code>difficulty.difficulty</code> and ,<code>trading.trading</code> all do NOT inherit from C++ as this class takes care of the C++ inheritance.
-The constructor '''__init__''' takes the arguments that we passed in from the XML file and passes them on to the various submodules. The only really really important thing you do in the constructor is call
+The constructor <code>__init__</code> takes the arguments that we passed in from the XML file and passes them on to the various submodules. The only really really important thing you do in the constructor is call
 <pre>
-  Director.Mission.__init__ (self)
+Director.Mission.__init__ (self)
 </pre>
 If you do not do this, Vegastrike will not load your module and will silently fail (this calls the C++ constructor, which actually triggers the binding of your module to the python mission).
@@ Line 24: / Line 24: @@
 Missions also may have 2 functions:
-* '''Pickle (self)''' which returns a string with a XML mission file that will load the mission properly as well as a string representing the mission in serialized form... if the mission were reloaded that mission would be loaded and its corresponding python would be run.
+* <code>Pickle (self)</code> which returns a string with a XML mission file that will load the mission properly as well as a string representing the mission in serialized form... if the mission were reloaded that mission would be loaded and its corresponding python would be run.
-* Then '''Unpickle (self, str)''' would be called (with str being a string) and the expectation that the mission would be reloaded. '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/newmission.py?rev=HEAD&content-type=text/vnd.viewcvs-markup modules/newmission.py]''' has an example of this. {{fixme}} ''LINK IS WRONG!! - OLD DATA MODULE REFERENCE''
+* Then <code>Unpickle (self, str)</code> would be called (with str being a string) and the expectation that the mission would be reloaded. <code>[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/newmission.py?rev=HEAD&content-type=text/vnd.viewcvs-markup modules/newmission.py]</code> has an example of this. {{fixme}} ''LINK IS WRONG!! - OLD DATA MODULE REFERENCE''
 You may also choose to save data in a float by float format as follows (the advantage to this format is that it is saved on a PER PLAYER basis... so that each player may have a different value):
@@ Line 34: / Line 34: @@
 <pre>
-  myindex=Director.pushSaveData(int whichplayer, stringkey,floatVal);
+myindex=Director.pushSaveData(int whichplayer, stringkey,floatVal);
 </pre>
@@ Line 65: / Line 65: @@
 | next=[[HowTo:Edit_Missions:Python:AI_scripts|AI Scripts]]
 }}
-[[Category:HowTo|Edit Missions:Python:Missions]] [[Category:Development|Edit Missions:Python:Missions]]
+[[Category:HowTos|Edit Missions:Python:Missions]]

@@ Line 25: / Line 25: @@
 * '''Pickle (self)''' which returns a string with a XML mission file that will load the mission properly as well as a string representing the mission in serialized form... if the mission were reloaded that mission would be loaded and its corresponding python would be run.
-* Then '''Unpickle (self, str)''' would be called (with str being a string) and the expectation that the mission would be reloaded. '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/newmission.py?rev=HEAD&content-type=text/vnd.viewcvs-markup modules/newmission.py]''' {{FIXME}} has an example of this.
+* Then '''Unpickle (self, str)''' would be called (with str being a string) and the expectation that the mission would be reloaded. '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/newmission.py?rev=HEAD&content-type=text/vnd.viewcvs-markup modules/newmission.py]''' has an example of this. {{fixme}} ''LINK IS WRONG!! - OLD DATA MODULE REFERENCE''
 You may also choose to save data in a float by float format as follows (the advantage to this format is that it is saved on a PER PLAYER basis... so that each player may have a different value):

← Older revision		Revision as of 15:23, 21 March 2005
Line 63:		Line 63:
	\| next=[[HowTo:Edit_Missions:Python:AI_scripts\|AI Scripts]]		\| next=[[HowTo:Edit_Missions:Python:AI_scripts\|AI Scripts]]
	}}		}}
		+	[[Category:HowTo\|Edit Missions:Python:Missions]] [[Category:Development\|Edit Missions:Python:Missions]]