Skip to content

AllowableUnitMaximums

How many of each restricted type a mission's dropship loadout may hold.

Specification
Applies to
scenarios
File
map file
Section
[Basic]
Value
list of integers
When omitted
ComputedRoughly half the missing numbers: the padding loop re-reads both list lengths on every turn, so it closes only half the gap between the two, and the pairing lookup then reads past the end of the shorter list for every name beyond it.
map file
[Basic]
AllowableUnits=E1,E2,SMECH
AllowableUnitMaximums=-1,-1,2

Each number pairs by position with the name at the same place in AllowableUnits and caps how many of that type may be loaded across all of the mission’s dropships together. Three values behave distinctly:

ValueEffect
-1The type is offered and never counted, so it may fill the whole loadout
0The type is dropped from the cameo list and cannot be loaded at all
PositiveThe type is offered until that many have been taken aboard, then its cameo stops responding

A list shorter than its companion is padded with -1, but the padding closes only half the gap — three names and no numbers leave two numbers behind. Every name past the end of the number list is then paired against whatever lies beyond it in memory. A longer list keeps its extra numbers, and they pair with nothing and do nothing.