AllowableUnitMaximums: Difference between revisions
en>Crimsonum Added info on bugs, fixed some formatting, and removed repetive text. |
Rain-Islet (talk | contribs) m [bot] Batch update {{Bugs}} templates. |
||
| (One intermediate revision by one other user not shown) | |||
| Line 15: | Line 15: | ||
Specified in a map's [[Basic]] section in conjunction with {{f|StartingDropships|link}} and {{f|AllowableUnits|link}}. The value is a comma-separated list that has the same number of entries as {{f|AllowableUnits|link}}. Each entry defines how many of the corresponding unit the player can select for dropship reinforcement using the [[Dropship loadout]] feature. Positive integer sets a limit, while -1 signifies no limit, although a practical limit of 15 exists anyway due to [[StartingDropships|a maximum of three available Dropships]], each with five passenger slots. By default the player can select an unlimited number of units, including [[BuildLimit|build-limited]] units like the Cyborg Commando in {{ts}} and Tanya in {{yr}}, and this flag provides a way to maintain the limitations for the reinforcements. | Specified in a map's [[Basic]] section in conjunction with {{f|StartingDropships|link}} and {{f|AllowableUnits|link}}. The value is a comma-separated list that has the same number of entries as {{f|AllowableUnits|link}}. Each entry defines how many of the corresponding unit the player can select for dropship reinforcement using the [[Dropship loadout]] feature. Positive integer sets a limit, while -1 signifies no limit, although a practical limit of 15 exists anyway due to [[StartingDropships|a maximum of three available Dropships]], each with five passenger slots. By default the player can select an unlimited number of units, including [[BuildLimit|build-limited]] units like the Cyborg Commando in {{ts}} and Tanya in {{yr}}, and this flag provides a way to maintain the limitations for the reinforcements. | ||
{{bugs}} | =={{bugs}}== | ||
There are at least two bugs involved with this flag. | There are at least two bugs involved with this flag. | ||
* If this flag is not specified, depending on the number of entires in {{f|AllowableUnits|link}}, some of the units cannot be selected during loadout (they appear to have invalid cost). | * If this flag is not specified, depending on the number of entires in {{f|AllowableUnits|link}}, some of the units cannot be selected during loadout (they appear to have invalid cost). | ||
Latest revision as of 17:07, 2 July 2025
|
|
|
|
|
|
| Flag: | AllowableUnitMaximums |
| File(s): | Maps |
| Values: | Comma-separated list of integers. |
| Default: | -1 for any entry in AllowableUnits |
| Applicable to: | Basic |
Specified in a map's Basic section in conjunction with StartingDropships and AllowableUnits. The value is a comma-separated list that has the same number of entries as AllowableUnits. Each entry defines how many of the corresponding unit the player can select for dropship reinforcement using the Dropship loadout feature. Positive integer sets a limit, while -1 signifies no limit, although a practical limit of 15 exists anyway due to a maximum of three available Dropships, each with five passenger slots. By default the player can select an unlimited number of units, including build-limited units like the Cyborg Commando in Tiberian Sun and Tanya in Yuri's Revenge, and this flag provides a way to maintain the limitations for the reinforcements.
Bugs/Side-Effects/Unexpected Limitations
There are at least two bugs involved with this flag.
- If this flag is not specified, depending on the number of entires in AllowableUnits, some of the units cannot be selected during loadout (they appear to have invalid cost).
- Defining a limit for a unit, then selecting the maximum number of those units in the loadout, will prevent those units from appearing with the Dropship. If there are no other units, the Dropship won't appear at all.