Random script for AI and three tanks



<event name="start_game">
<element type="ActivateRandomGroup" group1="mainroad_1a" chance1="25" group2="mainroad_1b" chance2="50" group3="mainroad_1c" chance3="75" group4="mainroad_1d" chance4="100" start_time="1"/>
<element type="ActivateRandomGroup" group1="mainroad_2a" chance1="33" group2="mainroad_2b" chance2="67" group3="mainroad_2c" chance3="100" start_time="1"/>
<element type="ActivateRandomGroup" group1="start_1a" chance1="25" group2="start_1b" chance2="50" group3="start_1c" chance3="75" group4="start_1d" chance4="100" start_time="1"/>
<element type="ActivateRandomGroup" group1="start_2a" chance1="33" group2="start_2b" chance2="67" group3="start_2c" chance3="100" start_time="1"/>
<element type="UnitInArea" area="exit" state="activate" start_time="3"/>
<element type="UnitInArea" area="south" state="activate" start_time="3"/>
<element type="UnitInArea" area="east" state="activate" start_time="3"/>
<element type="UnitInArea" area="west" state="activate" start_time="3"/>
<element type="UnitInArea" area="bridge" state="activate" start_time="3"/>
<element type="TriggerRandomEvent" event1="exit_tank_active" chance1="30" event2="south_tank_active" chance2="60" event3="west_tank_active" chance3="90" event4="no_tank" chance4="100" start_time="3.0"/>
</event>

<event name="exit_tank_active">
<element type="OrderTank" vehicle_id="exit_tank" ai="true" order="move" world_x="6668" world_y="6513" start_time="1.0"/>
<element type="RemoveVehicle" vehicle_id="south_tank" start_time="2"/>
<element type="RemoveVehicle" vehicle_id="west_tank" start_time="2"/>
</event>

<event name="south_tank_active">
<element type="OrderTank" vehicle_id="south_tank" ai="true" order="move" world_x="6362" world_y="4351" start_time="1.0"/>
<element type="RemoveVehicle" vehicle_id="exit_tank" start_time="1"/>
<element type="RemoveVehicle" vehicle_id="west_tank" start_time="1"/>
</event>

<event name="west_tank_active">
<element type="OrderTank" vehicle_id="west_tank" ai="true" order="move" world_x="-3316" world_y="7004" start_time="1.0"/>
<element type="RemoveVehicle" vehicle_id="exit_tank" start_time="1"/>
<element type="RemoveVehicle" vehicle_id="south_tank" start_time="1"/>
</event>

<event name="no_tank">
<element type="RemoveVehicle" vehicle_id="west_tank" start_time="1"/>
<element type="RemoveVehicle" vehicle_id="exit_tank" start_time="1"/>
<element type="RemoveVehicle" vehicle_id="south_tank" start_time="1"/>
</event>


Added to patch 1.35: the ability for OGR-Coop to have single-player style objectives, and with them a new few map-script-commands.

1) When OgrSetGameOver is used in an event, the match ends, if we are playing ogr-coop. This is so that mission-scripters can create any win condition they desire in an ogr-coop game.



<event name="start_game">

<element type="OgrSetGameOver" start_time="10.0"/>

</event>





2) When OgrEnableExtractionCheck is set to false, the game won't end even though players reach at the extraction point in ogr-recon mode.
When it's set to true, the check is turned on again. It is turned on by default when a game starts, so that games that does not use the tag will function like normal.



<event name="start_game"/>

<element type="OgrEnableExtractionCheck" enable="false" start_time="5.0"/>

</event>





3) TriggerRandomEvent will make it possible to randomize events.
You can at random make one out of four different events occur.
The events-tags are called event1,event2,event3 and event4, they are paired with chance-tags called chance1,chance2,chance3,chance4.
When TriggerRandomEvent is executed, a random number between 0 and 100 is generated, and compared with each chance-tag in order.



These are the parameters:



· event1 – name of the first event

· chance1 – a number between 0 and 100

· event2 - name of the second event

· chance2 – between chance1 and 100

· event3 - name of the third event

· chance3 – a number between chance2 and 100

· event4 - name of the fourth event

· chance4 – a number between chance3 and 100

If chance1=40, chance2=55, chance3=74, chance4=90 then...

event1 will run if number >0 and number<40
event2 will run if number =>40 and number<55
event3 will run if number =>55 and number<74
event4 will run if number =>74 and number<90
no event will if the number was => than 90!

....so if the random number was 42, event2 would have run.

You do not have to specify all four events, one or more is sufficient.
Example:
Here is an example with two different events occurring at 50/50 chance:

<event name="start_game">
<element type="TriggerRandomEvent" event1="event_AAA" chance1="50" event2="event_BBB" chance2="100" start_time="30.0"/>
</event>

<event name="event_AAA" once="true">
<!-- do some things here--/> 
</event>

<event name="event_BBB" once="true">
<!-- do some things here--/> 
</event>



4) ActivateRandomGroup will... guess what, activate a random group!
Works like just like TriggerRandomEvent, i.e one out of four groups will be activated.
The group-tags are called group1,group2,group3 and group4, they are paired with chance-tags called chance1,chance2,chance3,chance4.
When ActivateRandomGroup is executed, a random number between 0 and 100 is generated, and compared with each chance-tag in order.

These are the parameters:



· group1 – name of the first event

· chance1 – a number between 0 and 100

· groupt2 - name of the second event

· chance2 – between chance1 and 100

· group3 - name of the third event

· chance3 – a number between chance2 and 100

· group4 - name of the fourth event

· chance4 – a number between chance3 and 100



If chance1=40, chance2=55, chance3=74, chance4=90 then...

group1 will activate if number >0 and number<40
group2 will activate if number =>40 and number<55
group3 will activate if number =>55 and number<74
group4 will activate if number =>74 and number<90
no group will be activated if the number was => than 90!

....so if the random number was 56, group3 would have been activated.
Example:

<event name="start_game">
<element type="ActivateRandomGroup" group1="coders" chance1="50" group2="graphic_artists" chance2="100" start_time="30.0"/>
</event>





5) Objective - Used to add, remove or update a mission objective!



These are the parameters:

· id - name of the objective

· state - ( add/update/completed/aborted )

o add - creates a new objective.

o update - updates an objective with new way_point, txt, headline and mode.

o remove - marks an objective as completed. / done.

o aborted - marks an objective as aborted.

· txt - mission description text. (or use txt_id.)

· txt_id - the name of the localized mission description text.

· headline - the headline that is written on the mission button in the nav-com. (or use headline_id)

· headline_id - the name of the localized headline text.

· waypoint - (x y z) - a vector with the world position of the objective.

· waypoint_id - either the name of the localized text-string hovering at the objective in the crosscom, or the text itself if no localized id was found.

· mode - (1,2)

o 1 - primary objective.

o 2 - secondary objective.



Example:

<event name="start_game"/>



<element type="Objective" id="my_objective" headline_id="Destroy tanks" waypoint_id="Tanks" txt_id="Take our the mex tanks on the plaza.” waypoint="-12263.8428 9108.7314 -985.3781" state="add" mode="1" start_time="0"/>



</event>





6) ShowMessage – Prints a message in the chat window to all players in a ogr-coop game.



· msg – the string you want to display for all players.



Example:



<event name="start_game"/>

<element type="ShowMessage" msg=”You have completed the mission successfully!” />

</event>





Some small tips.

If you want to create a stationary MG-nest you simply create a m2hb_tripod in the props layer, and name it to whatever you want.

Now create any group you want, but with a ‘1’ after it, and give it the same group_id as the gun nest.

When you now activate the group through a <element type=”ActivateGroup” it will spawn on the stationary MG.



The group Friendly is used in singleplayer levels (and GRAW coop), and spawns the ghosts.



In the human layer there are also those that are named vehicle_crew and vehicle_passangers.

If they share a vehicle_ID with a vehicle from the vehicle layer they will spawn with the vehicle. Feel free to experiment with these, as I will not cover vehicle management in this tutorial.

These are activated in events through:

<element type="ActivateVehicle" vehicle_id="whatever" start_time="2"/>

<element type="RemoveVehicle" vehicle_id="whatever" start_time="2"/>

<element type="ExplodeVehicle" vehicle_id="whatever" start_time="2"/>



To order a car, you press f12 in the editor and write down the position, to where you want the car to move.

Then in the missionscript add:

<element type="OrderCar" vehicle_id="whatever" order="move" position="0 0 0" start_time="14"/>



Heli orders, feel free to experiment.



<element type="OrderHeli" vehicle_id="heli_name " order="move" position="0 0 2000" speed="0.2" target="true" start_time="12"/>


<element type="OrderHeli" vehicle_id="heli_name " order="land" position="0 0 2000" speed="0.5" target="false" start_time="15"/>


<element type="OrderHeli" vehicle_id="heli_name" order="target" position0 0 2000" speed="0.8" start_time="15"/>


<element type="SetTransportType" vehicle_id="heli_name" transport_type="insertion" start_time="16"/>



<element type="SetHeliStand" vehicle_id="heli_name" start_time="30.0"/>

<element type="SetHeliDropRope" vehicle_id="heli_name" start_time="32"/>

<element type="SetHeliDrop" vehicle_id="heli_name" start_time="35"/>



To add compositions, just add one in the editor, name it, and in the missionscipt add:

<element type="Composition" id="composition_name" start_time="3"/>



To be able to resupply at an apc, place a stryker, name it “whatever” and add

<element type="SetToSupply" vehicle_id="whatever" event="supplied"/>

This will trigger an event called ‘supplied’. Create that event and in it add this to make it so that you no longer can supply at that vehicle.

<element type="SetToSupply" vehicle_id="whatever" mode="false"/>