falcon4:campaign:trigger
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
falcon4:campaign:trigger [2007-07-13 08:43] snakeman added some bullseye/flot information |
falcon4:campaign:trigger [2009-08-18 11:14] (current) |
||
|---|---|---|---|
| Line 168: | Line 168: | ||
| #CHANGE_RELATIONS [team] [with] [rel] | #CHANGE_RELATIONS [team] [with] [rel] | ||
| </code> | </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: | Set the event number: | ||
| Line 208: | Line 216: | ||
| #SET_PAK_PRIORITY [team] [camp_id] [number] | #SET_PAK_PRIORITY [team] [camp_id] [number] | ||
| </code> | </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. | ||
falcon4/campaign/trigger.1184316221.txt.gz ยท Last modified: 2007-07-13 08:43 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
