Development:AIScripts - Revision history

AzureSky: Removed duplicate text

2008-08-27T14:47:43Z

Removed duplicate text

Shark at 00:57, 16 August 2008

2008-08-16T00:57:18Z

Shark at 00:56, 16 August 2008

2008-08-16T00:56:49Z

Shark at 00:41, 16 August 2008

2008-08-16T00:41:11Z

Shark at 20:38, 15 August 2008

2008-08-15T20:38:24Z

Show changes

Shark at 18:44, 14 August 2008

2008-08-14T18:44:52Z

Shark at 16:25, 13 August 2008

2008-08-13T16:25:31Z

New page

Vega Strike has completely programmable python AI scripts--but often times just editing an XML file with a list of actions at various distances and probabilities is sufficient and quite a bit more performant

@@ Line 1: / Line 1: @@
 Vega Strike has completely programmable python AI scripts--but often times just editing an XML file with a list of actions at various distances and probabilities is sufficient and quite a bit more performant
 AI scripts are selected as follows:
 the following two excel files in the ai/ folder are consulted

@@ Line 210: / Line 210: @@
            fire up afterburners and wiggle up and down
-   kick stop
 For a description of what each of these do see hard_coded_scripts.cpp

@@ Line 114: / Line 114: @@
 the prebaked scripts are listed as follows:
+   loop around fast
-   loop around fast
+    hits the afterburner and aims just to the left or above or right of the target in order to hopefully pass it and come around on its tail
    aggressive loop around fast
    loop around slow
    aggressive loop around slow
    loop around
    aggressive loop around
    barrel roll
    veer away
    veer away itts
    veer and turn away
    veer and vector away
    afterburn veer away
    afterburn vector away
    match velocity
    fly straight
    fly straight afterburner
    afterburn fly straight
    do nothing
    take off
    coast to stop
    self destruct
    take off every zig
    afterburn turn towards
    afterburn turn towards itts
    cloak
    evade
    kick stop
    move to

@@ Line 41: / Line 41: @@
 Lets take a look at an example:
-<hull max=".03" script="drop cargo" time="1" priority="8">
+  <hull max=".03" script="drop cargo" time="1" priority="8">
-  <hull max=".03" script="afterburn turn away" time="10" priority="8">
+    <hull max=".03" script="afterburn turn away" time="10" priority="8">
-  </hull>
+    </hull>
-</hull>
+  </hull>
 This says if the hull is at most .03 and the hull is at most .03 drop cargo for a second and then turn away for 10 seconds with a priority of 8
 nested script actions are conjoined together and if all their conditions evaluate to true they are performed in sequence.
@@ Line 50: / Line 50: @@
 Lets fish up a little more complex example:
-<hull max=".6" script="evade up down" time="4" timetointerrupt="3" priority="7">
+  <hull max=".6" script="evade up down" time="4" timetointerrupt="3" priority="7">
-  <fshield max=".25" script="evade up down" time="1" timetointerrupt="0" priority="7">
+    <fshield max=".25" script="evade up down" time="1" timetointerrupt="0" priority="7">
-    <rand max=".13" script="evade up down" time=".5" timetointerrupt="0" priority="7"/>
+      <rand max=".13" script="evade up down" time=".5" timetointerrupt="0" priority="7"/>
-  </fshield>
+    </fshield>
-</hull>
+  </hull>
 This translates into:  if the hull is at most at 60% strength, the forward shields are at most 25% and the random number generator selects a number with 13% probability then evade up and down for 4 seconds, 3 of which are uninterruptible, then evade up and down for another 1.5 seconds which are interruptible
@@ Line 63: / Line 63: @@
 Collision Avoidance:
-<meterdistance max="30" script="afterburn turn away" time="7" timetointerrupt="3" priority="6">
+  <meterdistance max="30" script="afterburn turn away" time="7" timetointerrupt="3" priority="6">
-    <rand min=".4" script="afterburn fly straight" time=".5" timetointerrupt="1" priority="6"/>
+      <rand min=".4" script="afterburn fly straight" time=".5" timetointerrupt="1" priority="6"/>
-</meterdistance>
+  </meterdistance>
@@ Line 76: / Line 76: @@
 The script that needs to be interrupted by the above script follows later in the file:
-<meterdistance min="60" max="500" script="turn towards itts" priority="4" time="5">
+  <meterdistance min="60" max="500" script="turn towards itts" priority="4" time="5">
-  <meterdistance max="500" script="turn towards" priority="4" time="8">
+    <meterdistance max="500" script="turn towards" priority="4" time="8">
-   <rand min=".5" script="loop around" priority="4" time="5">
+     <rand min=".5" script="loop around" priority="4" time="5">
-   </rand>
+     </rand>
-  </meterdistance>
+    </meterdistance>
-</meterdistance>
+  </meterdistance>
 This says "if the distance is between 60 and 500, is at most 500 and the random number generator gives a number that has probability 50% then turn towards the target, giving it itts lead if available, then turn towards it without lead, then loop around it.   Notice that this script is entirely interruptible if the AI ever gets within 30--and since the priority is lower than 6, it will indeed be overridden by the afterburn turn away listed above.  But the above script is essentially the bread and butter of the AI--it directs it to turn towards its opponent and shoot like crazy (the shooting is handled in C code right now)
 Another important facet of this attacking part of the AI is to have something that's true in all conditions...this means including a fallback that happens if the random number fails like so:
-<meterdistance min="60" max="500" script="afterburn veer away" priority="4" tim\
+  <meterdistance min="60" max="500" script="afterburn veer away" priority="4" tim\
 e="2">
-  <meterdistance max="500" script="turn towards" priority="4" time="8">
+    <meterdistance max="500" script="turn towards" priority="4" time="8">
-  </meterdistance>
+    </meterdistance>
-</meterdistance>
+  </meterdistance>
 and also some things to do if far away:
 <!-- meterdistance far out-->
-<meterdistance min="500" script="barrel roll" time="2" timetointerrupt="1">
+  <meterdistance min="500" script="barrel roll" time="2" timetointerrupt="1">
-  <fshield max=".1"  script="barrel roll" time="1">
+    <fshield max=".1"  script="barrel roll" time="1">
-  </fshield>
+    </fshield>
-</meterdistance>
+  </meterdistance>
-<meterdistance min="500" script="barrel roll" time="2" timetointerrupt="1">
+  <meterdistance min="500" script="barrel roll" time="2" timetointerrupt="1">
-  <bshield max=".1"  script="barrel roll" time="1">
+    <bshield max=".1"  script="barrel roll" time="1">
-  </bshield>
+    </bshield>
-</meterdistance>
+  </meterdistance>
-<meterdistance min="500" script="afterburn turn towards itts" priority="4" time="3">
+  <meterdistance min="500" script="afterburn turn towards itts" priority="4" time="3">
-</meterdistance>
+  </meterdistance>

← Older revision		Revision as of 18:44, 14 August 2008
Line 1:		Line 1:
	Vega Strike has completely programmable python AI scripts--but often times just editing an XML file with a list of actions at various distances and probabilities is sufficient and quite a bit more performant		Vega Strike has completely programmable python AI scripts--but often times just editing an XML file with a list of actions at various distances and probabilities is sufficient and quite a bit more performant
		+
		+	AI scripts are selected as follows:
		+	the following two excel files in the ai/ folder are consulted
		+	ai/VegaEvents.csv
		+	The VegaEvents file is a table mapping combat_roles of the attacker to roles of his target. Combat roles are stored in the Combat_Role column in units.csv
		+	For instance if my starship is a BOMBER and I am targeting a BASE then vega strike will look in row BOMBER and column BASE and find the beginning of the name of the AI script thus it would be
		+	bomber.* where * might be .agg.xml or .civ.xml depending on the next file:
		+
		+	ai/VegaPersonalities.csv
		+	VegaPersonalities is a list of a factions and what AI scripts they wish to use
		+	Each listed faction is followed by a comma and then by a space separated list of extensions to use on their AI script.
		+	so if bomber was selected from VegaEvents.csv and the faction is merchant which has the second column "scared scared civ" there will be a 1/3 chance that bomber.civ.xml will be selected, otherwise bomber.scared.xml will be selected
		+
		+	if the file is not found bomber.agg.xml will be searched then default.civ.xml then default.agg.xml (I believe .py files are also searched)
		+
		+
		+	Once an XML file is selected, it is parsed every frame to select an AI behavior for the starship to use when attacking its target.