AltNextScenario: Difference between revisions
No edit summary |
Added some links and stuff. |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{Flag | ||
|name={{PAGENAME}} | |||
|files={{Categ|Maps}} | |||
|types={{Categ|Basic}} | |||
|values={{Values|STRINGS|Map file name}} | |||
|default=none | |||
|ts=yes | |||
|fs=yes | |||
|ets=yes | |||
|hp=yes | |||
|ra2=yes | |||
|yr=yes | |||
|ares=yes | |||
}}<br /> | |||
Specifies an alternate mission that the player can proceed to after this mission, usually by completing a special objective. This is achieved by setting the [[VariableNames|global variable]] number 1 (namely {{tt|<Alternate Next Scenario>}} as defined in {{ini|rules}}{{arr|r}}{{sl|VariableNames}}) to a value of 1 during the mission, either by [[Actions_(maps)/RA2YR|map trigger action #28 (set global variable)]] or [[ScriptTypes/ScriptActions|script action #12]]. This causes the game to use the map file defined by this flag as the next mission rather than the map in {{f|NextScenario|link}}. {{f|SkipMapSelect|link}} should be enabled to skip the normal map selection procedure. | |||
Note that the file name specified here must match and correspond exactly with the file name for a mission as detailed in the {{ini|mapsel}} and {{ini|mission}} files. In {{ini|mapsel}}, the progression from the current map should have both the entries of the normal mission map and the alternative mission map. | |||
==See also== | |||
*[[NextScenario]] | |||
*[[Campaign Progression]] | |||
Latest revision as of 09:29, 4 September 2019
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Flag: | AltNextScenario |
| File(s): | Maps |
| Values: | Strings: Normal text. (Limited to: Map file name) |
| Default: | none |
| Applicable to: | Basic |
Specifies an alternate mission that the player can proceed to after this mission, usually by completing a special objective. This is achieved by setting the global variable number 1 (namely <Alternate Next Scenario> as defined in rules(md).ini→[VariableNames]) to a value of 1 during the mission, either by map trigger action #28 (set global variable) or script action #12. This causes the game to use the map file defined by this flag as the next mission rather than the map in NextScenario. SkipMapSelect should be enabled to skip the normal map selection procedure.
Note that the file name specified here must match and correspond exactly with the file name for a mission as detailed in the mapsel(md).ini and mission(md).ini files. In mapsel(md).ini, the progression from the current map should have both the entries of the normal mission map and the alternative mission map.