Development:Missions
Contents
EDITING MISSIONS
Introduction
Vega Strike has a powerful missions scripting interface that allows you to nearly modify Vega Strike at whatever level you choose, from the AI scripts (and the physics thereof) to the missions... to the overall plot and goal of the game.
Basic XML integration
First let me start by explaining how to run a python class... in this case we start with the prebuild "privateer.py" script to run our mission. Open up mission/explore_universe.mission First come the variables that designate how the mission should normally start. By normally I mean if they don't have any save game present.
Variables Section
It loads Crucible/Cephid_17.system as the star system (which is in XML and stores all present planets) After this, comes the actors in the mission, the flightgroups of fighters. If a mission has more than one player, then each player is the leader (first ship) in each respective flightgroup.
Notice that so far there are a lot of values you don't see for long in the default vegastrike game. Credits, System, first flightgroup fighter, difficulty--these are all initial values but can change.... since there is specified a savegame. The savegame makes the mission more of a campaign type mission where things may be saved to disk and reloaded at a later point. If no savegame variable is specified (this is where the autosave goes) then the mission will not save and will be a one time play mission.
<mission> <settings> <origin planet="earth" x="0000" y="100" z="000.0"/> </settings> <variables> <!-- <var name="continuousterrain" value="continuousterrain.txt"/>--> <var name="credits" value="13500"/> <var name="defaultplayer" value="blue"/> <var name="mission_name" value="Privateer Mission" /> <var name="difficulty" value=".05"/><!--starting difficulty--> <var name="system" value="Crucible/Cephid_17" /> <var name="description" value="Like, as if." /> <var name="savegame" value="explore_universe_difficulty" /> </variables>
Flightgroup Section
The rot flag is ignored, and the position specifies the x,y,z coords of the Shlimazel flightgroup, which is of type llama.begin.
<flightgroups>
<flightgroup name="Shlimazel" faction="privateer" type="llama.begin"
ainame="default" waves="1" nr_ships="1">
<pos x="-95124024.543917" y="412089916.256812"
z="-110779667.398050"/>
<rot x="180.0" y="180.0" z="180.0"/>
<order order="tmptarget" target="omikron"/>
<order priority="0" order="superiority" target="enemy"/>
<order priority="1" order="bomber" target="omikron"/>
<order priority="2" order="escort" target="blue"/>
</flightgroup>
</flightgroups>
Python Section
Future note: If you wanted to add a campaign to the privateer mission you would most likely modify privateer.py to have a campaign module get loaded.... so you wouldn't necessarily need to modify explore_universe.mission just to add a campaign... lets dig further into the meat of the scripting.
If a mission has python tags...then it is a python mission and may have some embedded python in it. In this case the python makes a new python object of type privateer in the privateer.py module in the modules/ directory.
<python>
from privateer import privateer
my_obj=privateer(8000,40000,500,3,2,.6,.25,.1,400000,2000)
</python>
<!-- <module name="director">
<import name="privateer"/>
<script name="initgame">
<exec module="privateer" name="init">
<const type="float" value="8000.0"/><!-- significant distance-->
<const type="float" value="40000.0"/><!-- detection distance-->
<const type="float" value="500.0"/><!-- generation distance -->
<const type="int" value="3"/> <!-- min ships -->
<const type="int" value="2"/><!--gen ships-->
<const type="float" value="0.6"/><!--fighter prob-->
<const type="float" value="0.25"/><!--enemy prob-->
<const type="float" value="0.02"/><!--capship prob-->
<const type="float" value="400000.0"/><!--Max diff credits-->
<const type="float" value="2000.0"/><!--capship distance-->
</exec>
</script>
<script name="gameloop">
<exec module="privateer" name="loop"/>
</script>
<script name="initstarsystem">
<exec name="initstarsystem" module="privateer" />
</script>
</module>-->
</mission>
You have to be careful about newlines, etc in the XML, but it shoudl usually work just dandy. You notice that the mission may pass in arguments to the privateer module that can make slight changes in teh gameplay. This allows many cargo missions to use the same module in order to change the parameters of the cargo missions. In this case the values I have selected appear to work relatively well.
Python Inheritance In Missions
Ok lets dig further into the privateer.py 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.
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
Director.Mission.__init__ (self)
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).
Each mission module must have an execute function so that something can happen every physics frame. In this case it just calls execute on all the submodules... not very interesting.
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. Then Unpickle (self, str) would be called (with str being a string) and the expectation that the mission would be reloaded. data/newmission.py has an example of this. 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):
There are 4 functions at your disposal for this older way to save missions:
This function adds the key for later retrieval (even after VS quits ) and pushes the float to the end of the hashtable indexed by stringkey:
myindex=Director.pushSaveData(int whichplayer, stringkey,floatVal);
This function modifies a index in a key that has already been pushed back at one point:
Director.putSaveData (intWhichPlayer, stringkey, myIndex, floatVal);
This function gets the number of float values for a given player:
Director.getSaveDataLength (int whichplayer, string key)
This function gets save data saved at that number:
Director.getSaveData(int whichplayer, stringkey, int num)
You can make up stringkeys and save only 1 float per key if you wish... each key is allowed to have an vector of possible values. Use as you wish! For the privateer mission I save things with key 31337ness and the one value in there is the difficulty that I write out.... If a campaign is more global rather than player specific you may just choose to pickle it...however if something is on a per-player basis, it may be best going in these SaveData float vectors.
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.
