PMC Editing Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Trigger ======

**Trigger files** revisited, directly from Codec:

Trigger files (.tri)

Syntax: Comments start with a / and the rest of the line is ignored.

Keywords are:

How many events there are in total:
<code>
#TOTAL_EVENTS [number]
</code>

Then follows an initialisation section that has the following fields. This is read at the start of a new campaign. Section ends with the **ENDINIT**

This event is set:
<code>
#SET_EVENT [event]
</code>

This event is cleared (not set):
<code>
#RESET_EVENT [event]
</code>

Redundant, use to set the campaign tempo:
<code>
#SET_TEMPO [number]
</code>

Redundant, use to read a teams priority file:
<code>
#CHANGE_PRIORITIES [teamno] [number]
</code>

The following only apply to special initialisations.

Bullseye reference point X position. X-position of relative map point to calculate best new Bullseye position (closest FLOT objective to this point will become new bullseye position):
<code>
#BULLSEYE_X [number]
</code>

Bullseye reference point Y position. Y-position of relative map point to calculate best new Bullseye position (closest FLOT objective to this point will become new bullseye position):
<code>
#BULLSEYE_Y [number]
</code>

FLOT sort direction; 0 = West-East, 1 = North-South. 0: Sort FLOT by X-coordinates (default), 1: Sort FLOT by Y-coordinates:
<code>
#FLOT_SORTDIRECTION [number]
</code>

FLOT distance position. Maximum distance between two FLOT objects (in km) to draw a line:
<code>
#FLOT_DRAWDISTANCE [number]
</code>
These parameters must be placed in the first setup part between **#TOTAL_EVENTS** and **#ENDINIT**.\\
Defaults are:

<code>
#BULLSEYE_X 512
#BULLSEYE_Y 512 (center of Korea, which is original value)
#FLOT_SORTDIRECTION 0
#FLOT_DRAWDISTANCE 50
</code>

End of initialisation section:
<code>
#ENDINIT
</code>

The remaining parts can occur anywhere in the file

End of the trigger file - everything else is ignored:
<code>
#ENDSCRIPT
</code>

A family of tests for certain conditions chosen from the following:
<code>
#IF
</code>

True if event number has been fired (set in the EVT camp sub file):
<code>
#IF_EVENT_PLAYED [event]
</code>

True if friendly/enemy team has ground task manager priorityObjective set to [number]:
<code>
#IF_MAIN_TARGET [F|E] [number]
</code>

True if team friendly/enemy camp_id primary objective has ground_assigned set:
<code>
#IF_TROOPS_COMMITTED [F|E] [camp_id]
</code>

True if the team controls the list of objectives. With type of 'A' it must own all the objectives in the list, else it must own any of them (and/or logic):
<code>
#IF_CONTROLLED [team] [type] [obj list]
</code>

True if team has initiative level greater/less than or equal to the number given:
<code>
#IF_INITIATIVE [team] [G|L] [number]
</code>

True if the team has current stats of greater/less than or equal to the number:
<code>
#IF_SUPPLY [team] [G|L] [number]
</code>

True if the player option for enemy ground experience is greater/less than or equal to the number:
<code>
#IF_PLAYER_DIFFICULTY [G|L] [number]
</code>

True if the friendly/enemy team controls more than number objectives:
<code>
#IF_PRI_CONTROLLED_LT [F|E] [number]
</code>

True if team has ground action offensive type set:
<code>
#IF_ON_OFFENSIVE [team]
</code>

True if force ratio is of the right ratio. - type is A for current aircraft, G for current ground vehicles, N for current no ships, anything else is aircraft + ground The number is calculated for the given team and the opposite team. Then the ratio is (team no * 10) / (opposite number) which to be true must be greater/less than or equal to the number:
<code>
#IF_FORCE_RATIO [type] [team] [opposite] [G|L] [number]
</code>

True if this many hours have elapsed since the last major campaign event:
<code>
#IF_BORDOM_HOURS [hours]
</code>

If G is present, true if the current campaign day is ]= the number, else true if less that or equal:
<code>
#IF_CAMPAIGN_DAY [G|L] [number]
</code>

With a G, true if the team has reinforcements ]= number. Else less than or equal:
<code>
#IF_REINFORCEMENT [team] [G|L] [number]
</code>

True if a random number isless than the given number, which is between 0 and 100:
<code>
#IF_RANDOM_CHANCE [number]
</code>

True if the given condition above is false #ENDIF - closes the:
<code>
#ELSE
</code>

Play the given movie number:
<code>
#IF #PLAY_MOVIE [num]
</code>

Change the relations between team and with to the given rel state. If rel is Allied, then the teams merge:
<code>
#CHANGE_RELATIONS [team] [with] [rel]
</code>

<rel> according to tacedit teams page relations\\
0 = none. Used or not?\\
1 = Allied\\
2 = Friendly\\
3 = Neutral\\
4 = Hostile\\
5 = At War

Set the event number:
<code>
#DO_EVENT [num]
</code>

Move the initiative by amount from the fromteam to the toteam:
<code>
#SHIFT_INITIATIVE [fromteam] [toteam] [amount]
</code>

Clear number event:
<code>
#RESET_EVENT [number]
</code>

End the campaign with the given type:
<code>
#END_GAME [type]
</code>

Update the last major event to now:
<code>
#RESET_BORDOM_TIMEOUT
</code>

No longer used:
<code>
#CHANGE_PRIORITIES
</code>

Supply level for team is set to at least s, fuel is set to at least f and replacements set to at least r:
<code>
#SET_MINIMUM_SUPPLIES [team] [s] [f] [r]
</code>

For primary objective camp_id, set the teams ground and air priority to the number. This also sets the primary objective flag scripted_priority:
<code>
#SET_PAK_PRIORITY [team] [camp_id] [number]
</code>

Few entries found in AF tri files, the effect these have are unknown at this time.
<code>
#PARENTRECALCDEPTH 4
#FLOT_SORTDISTANCE 20
#MINEVALUATEAIRBASEDISTANCE 20
</code>


====== Mission.dat ======

You can use campaign specific mission.dat file selected with trigger file.

The init section can now contain
<code>
#MISSION_DATFILE
</code>
to specify a campaign-specific mission.dat. If not specified, normal mission.dat is loaded.

So for example if save2.tri contains 

<code>
#TOTAL_EVENTS ...
...
...
#MISSION_DATFILE missionRF
...
...
#ENDINIT
</code>
(command must be between TOTAL_EVENTS and ENDINIT), then Falcon loads the mission data of

<campaign_dir>\missionRF.dat

When the other campaigns .tri files don't contain this line, then they default to the normal mission.dat.

Note that the ".dat" is NOT to be specified in the trigger file, but the file itself must have this extension.

Thus not only each theater but each campaign can have its own mission.dat file now.


====== Falcon4.aii ======

Falcon4.aii is switched using
<code>
#FALCON4_AIIFILE
</code>
in .tri file.

The default Falcon4.aii is loaded for all modes first to make sure we have valid values (TE uses some variables from there), and then if campaign, the specific one is loaded, or Falcon4.AII when no one is specified.
PMC Editing Wiki

User Tools

Site Tools

Page Tools
