Differences

This shows you the differences between two versions of the page.

--- falcon4:campaign:trigger [2007-07-10 18:17]
snakeman created trigger initial page
+++ falcon4:campaign:trigger [2009-08-18 11:14] (current)
@@ Line 38: / Line 38: @@
 The following only apply to special initialisations.
-Bullseye reference point X position:
+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:
+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:
+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:
+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>
@@ Line 159: / Line 168: @@
 #CHANGE_RELATIONS [team] [with] [rel]
 </code>
+<rel> according to tacedit teams page relations\\
+= none. Used or not?\\
+= Allied\\
+= Friendly\\
+= Neutral\\
+= Hostile\\
+= At War
 Set the event number:
@@ Line 199: / Line 216: @@
 #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

Differences

Page Tools