Development:Python:AI Scripts - Revision history

Turbo beholder: ah, yes, one more

2010-08-15T12:09:31Z

ah, yes, one more

Turbo beholder: how ancient is this one?

2010-08-13T21:57:48Z

how ancient is this one?

pyramid: HowTo:Edit Missions:Python:AI scripts moved to Development:Python:AI Scripts

2008-04-21T13:54:12Z

HowTo:Edit Missions:Python:AI scripts moved to Development:Python:AI Scripts

pyramid at 13:42, 21 April 2008

2008-04-21T13:42:32Z

pyramid at 09:07, 21 April 2008

2008-04-21T09:07:37Z

Pirx at 18:13, 28 May 2005

2005-05-28T18:13:55Z

202.50.187.13 at 05:34, 23 March 2005

2005-03-23T05:34:21Z

Pirx: added categories

2005-03-21T15:20:39Z

added categories

202.50.187.13 at 05:11, 21 March 2005

2005-03-21T05:11:04Z

202.50.187.13 at 05:09, 21 March 2005

2005-03-21T05:09:57Z

New page

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

Let me talk about AI scripts briefly.

You'll notice a nice AI script named printhello.py in the data/printhello.py. It is very similar to a mission with a few notable differences.

* First of all the AI class you make must inherit from the class '''VS.PythonAI'''.
* Secondly instead of having an '''__init__ ''' function it must have an '''init()''' function. The reasons for this have something to do with how inheritance works from C++, but this init function takes in self of course and the unit to which thie AI script belongs. '''__init__''' may start off some AI scripts from the get go, or you may wait until you execute each frame. in this case printhello loads the XML script '''++turntowards.xml''' (which is the hard coded C++ equivalent to '''ai/scripts/turntowards.xml'''). After loading that AI script it replaces its parents order with the last AI script, in this case the XML script. In the Execute function this AI script calls Execute on the higher level (which takes care of responding to communications) and then prints h to the console for no apparent reason.
* Lastly and most importantly, the AI script makes a new class for itself. So when the C++ code executes '''printhello.py''' it will call the C++ constructor which will take care of binding it. So when you make a new unit like so:
<pre>
VS.launch (fgname,type,faction,"unit","printhello.py",nr_ships,nr_waves,vec,logo)
</pre>
it will have this python AI attached to it. However if you are too lazy to write AI's you can use the most excellent default AI
<pre>
VS.launch (fgname,type,faction,"unit","default",nr_ships,nr_waves,vec,logo)
</pre>

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

@@ Line 4: / Line 4: @@
 In the <code>modules</code> directory, you'll notice a nice AI script named '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data/modules/ai/ai_sitting_duck.py?view=markup ai_sitting_duck.py]'''. It is very similar to a mission with a few notable differences:
 * First of all, the AI class you make must inherit from the class <code>VS.PythonAI</code>.
-* Secondly, instead of having an <code>__init__</code> function it must have an <code>init()</code> function. The reasons for this have something to do with how inheritance works from C++, but this init function takes in self of course and the unit to which the AI script belongs. <code>__init__</code> may start off some AI scripts from the get go, or you may wait until you execute each frame. In this case ''ai_sitting_duck.py'' loads the XML script <code>++turntowards.xml</code> (which is the hard coded C++ equivalent to '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data4.x/ai/script/turntowards.xml?view=markup ai/scripts/turntowards.xml]'''). After loading that AI script it replaces its parents order with the last AI script, in this case the XML script. In the Execute function this AI script calls Execute on the higher level (which takes care of responding to communications) and then prints h to the console for no apparent reason.
+* Secondly, instead of having an <code>__init__</code> function it must have an <code>init()</code> function. The reasons for this have something to do with how inheritance works from C++, but this init function takes in self of course and the unit to which the AI script belongs. <code>__init__</code> may start off some AI scripts from the get go, or you may wait until you execute each frame. In this case ''ai_sitting_duck.py'' loads the XML script <code>++turntowards.xml</code> (which is the hard coded C++ equivalent to '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data/ai/script/turntowards.xml?view=markup ai/scripts/turntowards.xml]'''). After loading that AI script it replaces its parents order with the last AI script, in this case the XML script. In the Execute function this AI script calls Execute on the higher level (which takes care of responding to communications) and then prints h to the console for no apparent reason.
 * Lastly and most importantly, the AI script makes a new class for itself. So when the C++ code executes <code>ai_sitting_duck.py</code> it will call the C++ constructor which will take care of binding it. So when you make a new unit like this:
 <code><pre>

@@ Line 2: / Line 2: @@
 Let me talk about AI scripts briefly.
-In the <code>modules</code> directory, you'll notice a nice AI script named '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data4.x/modules/ai_sitting_duck.py?view=markup ai_sitting_duck.py]'''. It is very similar to a mission with a few notable differences:
+In the <code>modules</code> directory, you'll notice a nice AI script named '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data/modules/ai/ai_sitting_duck.py?view=markup ai_sitting_duck.py]'''. It is very similar to a mission with a few notable differences:
 * First of all, the AI class you make must inherit from the class <code>VS.PythonAI</code>.
 * Secondly, instead of having an <code>__init__</code> function it must have an <code>init()</code> function. The reasons for this have something to do with how inheritance works from C++, but this init function takes in self of course and the unit to which the AI script belongs. <code>__init__</code> may start off some AI scripts from the get go, or you may wait until you execute each frame. In this case ''ai_sitting_duck.py'' loads the XML script <code>++turntowards.xml</code> (which is the hard coded C++ equivalent to '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data4.x/ai/script/turntowards.xml?view=markup ai/scripts/turntowards.xml]'''). After loading that AI script it replaces its parents order with the last AI script, in this case the XML script. In the Execute function this AI script calls Execute on the higher level (which takes care of responding to communications) and then prints h to the console for no apparent reason.

@@ Line 1: / Line 1: @@
-{{NAV_Manual |
+=Python AI Scripts=
 Let me talk about AI scripts briefly.
-You'll notice a nice AI script named <code>[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data/printhello.py?rev=HEAD&content-type=text/vnd.viewcvs-markup printhello.py]</code>. It is very similar to a mission with a few notable differences.  {{fixme}} ''This is a reference to the old pre 4.0 data''
+In the <code>modules</code> directory, you'll notice a nice AI script named '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data4.x/modules/ai_sitting_duck.py?view=markup ai_sitting_duck.py]'''. It is very similar to a mission with a few notable differences:
+* First of all, the AI class you make must inherit from the class <code>VS.PythonAI</code>.
-* First of all the AI class you make must inherit from the class <code>VS.PythonAI</code>.
+* Secondly, instead of having an <code>__init__</code> function it must have an <code>init()</code> function. The reasons for this have something to do with how inheritance works from C++, but this init function takes in self of course and the unit to which the AI script belongs. <code>__init__</code> may start off some AI scripts from the get go, or you may wait until you execute each frame. In this case ''ai_sitting_duck.py'' loads the XML script <code>++turntowards.xml</code> (which is the hard coded C++ equivalent to '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data4.x/ai/script/turntowards.xml?view=markup ai/scripts/turntowards.xml]'''). After loading that AI script it replaces its parents order with the last AI script, in this case the XML script. In the Execute function this AI script calls Execute on the higher level (which takes care of responding to communications) and then prints h to the console for no apparent reason.
-* Secondly instead of having an <code>__init__</code> function it must have an <code>init()</code> function. The reasons for this have something to do with how inheritance works from C++, but this init function takes in self of course and the unit to which the AI script belongs. <code>__init__</code> may start off some AI scripts from the get go, or you may wait until you execute each frame. in this case printhello loads the XML script <code>++turntowards.xml</code> (which is the hard coded C++ equivalent to <code>[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/ai/scripts/turntowards.xml?rev=HEAD&content-type=text/vnd.viewcvs-markup ai/scripts/turntowards.xml]</code>). After loading that AI script it replaces its parents order with the last AI script, in this case the XML script. In the Execute function this AI script calls Execute on the higher level (which takes care of responding to communications) and then prints h to the console for no apparent reason.
+* Lastly and most importantly, the AI script makes a new class for itself. So when the C++ code executes <code>ai_sitting_duck.py</code> it will call the C++ constructor which will take care of binding it. So when you make a new unit like this:
-* Lastly and most importantly, the AI script makes a new class for itself. So when the C++ code executes <code>printhello.py</code> it will call the C++ constructor which will take care of binding it. So when you make a new unit like so:
+<code><pre>
-<pre>
+VS.launch (fgname,type,faction,"unit","ai_sitting_duck.py",nr_ships,nr_waves,vec,logo)
-VS.launch (fgname,type,faction,"unit","printhello.py",nr_ships,nr_waves,vec,logo)
+</pre></code>
-</pre>
+it will have this python AI attached to it. However, if you are too lazy to write AI's you can use the most excellent default AI:
-it will have this python AI attached to it. However if you are too lazy to write AI's you can use the most excellent default AI
+<code><pre>
 VS.launch (fgname,type,faction,"unit","default",nr_ships,nr_waves,vec,logo)
-</pre>
+</pre></code>
-----
+[[Category:HowTos|Edit Missions:Python:AI scripts]]
-{{NAV_Manual |
+[[Category:Development]]
-| previous=[[HowTo:Edit_Missions:Python:Missions|Missions]]
+[[Category:Development|Edit Missions:Python:AI scripts]]

@@ Line 1: / Line 1: @@
 {{NAV_Manual |
 | previous=[[HowTo:Edit_Missions:Python:Missions|Missions]]
-| up=[[HowTo:Edit_Missions|Edit Missions]]
+| up=[[Development:Missions|Edit Missions]]
 | next=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]]
 }}
@@ Line 24: / Line 24: @@
 {{NAV_Manual |
 | previous=[[HowTo:Edit_Missions:Python:Missions|Missions]]
-| up=[[HowTo:Edit_Missions|Edit Missions]]
+| up=[[Development:Missions|Edit Missions]]
 | next=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]]
 }}
 [[Category:HowTos|Edit Missions:Python:AI scripts]] [[Category:Development|Edit Missions:Python:AI scripts]]

@@ Line 8: / Line 8: @@
 Let me talk about AI scripts briefly.
-You'll notice a nice AI script named '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data/printhello.py?rev=HEAD&content-type=text/vnd.viewcvs-markup printhello.py]'''. It is very similar to a mission with a few notable differences.  {{fixme}} ''This is a reference to the old pre 4.0 data''
+You'll notice a nice AI script named <code>[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data/printhello.py?rev=HEAD&content-type=text/vnd.viewcvs-markup printhello.py]</code>. It is very similar to a mission with a few notable differences.  {{fixme}} ''This is a reference to the old pre 4.0 data''
-* First of all the AI class you make must inherit from the class '''VS.PythonAI'''.
+* First of all the AI class you make must inherit from the class <code>VS.PythonAI</code>.
-* Secondly instead of having an '''__init__ ''' function it must have an '''init()''' function. The reasons for this have something to do with how inheritance works from C++, but this init function takes in self of course and the unit to which thie AI script belongs. '''__init__''' may start off some AI scripts from the get go, or you may wait until you execute each frame. in this case printhello loads the XML script '''++turntowards.xml''' (which is the hard coded C++ equivalent to '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/ai/scripts/turntowards.xml?rev=HEAD&content-type=text/vnd.viewcvs-markup ai/scripts/turntowards.xml]'''). After loading that AI script it replaces its parents order with the last AI script, in this case the XML script. In the Execute function this AI script calls Execute on the higher level (which takes care of responding to communications) and then prints h to the console for no apparent reason.
+* Secondly instead of having an <code>__init__</code> function it must have an <code>init()</code> function. The reasons for this have something to do with how inheritance works from C++, but this init function takes in self of course and the unit to which the AI script belongs. <code>__init__</code> may start off some AI scripts from the get go, or you may wait until you execute each frame. in this case printhello loads the XML script <code>++turntowards.xml</code> (which is the hard coded C++ equivalent to <code>[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/ai/scripts/turntowards.xml?rev=HEAD&content-type=text/vnd.viewcvs-markup ai/scripts/turntowards.xml]</code>). After loading that AI script it replaces its parents order with the last AI script, in this case the XML script. In the Execute function this AI script calls Execute on the higher level (which takes care of responding to communications) and then prints h to the console for no apparent reason.
-* Lastly and most importantly, the AI script makes a new class for itself. So when the C++ code executes '''printhello.py''' it will call the C++ constructor which will take care of binding it. So when you make a new unit like so:
+* Lastly and most importantly, the AI script makes a new class for itself. So when the C++ code executes <code>printhello.py</code> it will call the C++ constructor which will take care of binding it. So when you make a new unit like so:
 <pre>
 VS.launch (fgname,type,faction,"unit","printhello.py",nr_ships,nr_waves,vec,logo)
@@ Line 27: / Line 27: @@
 | next=[[HowTo:Edit_Missions:Python:Bindings|Python Bindings]]
 }}
-[[Category:HowTo|Edit Missions:Python:AI scripts]] [[Category:Development|Edit Missions:Python:AI scripts]]
+[[Category:HowTos|Edit Missions:Python:AI scripts]] [[Category:Development|Edit Missions:Python:AI scripts]]

← Older revision	Revision as of 13:54, 21 April 2008
(No difference)

← Older revision		Revision as of 15:20, 21 March 2005
Line 27:		Line 27:
	\| next=[[HowTo:Edit_Missions:Python:Bindings\|Python Bindings]]		\| next=[[HowTo:Edit_Missions:Python:Bindings\|Python Bindings]]
	}}		}}
		+	[[Category:HowTo\|Edit Missions:Python:AI scripts]] [[Category:Development\|Edit Missions:Python:AI scripts]]