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

ComputedHalf the names, rounded up, receive -1, starting from the front of the list. The names after them get no number, and their limits are unpredictable.

map file

[Basic]
AllowableUnits=E1,E2,SMECH
AllowableUnitMaximums=-1,-1,2

Each number caps how many of one type may be loaded across all of the mission’s dropships together. It applies to the name at the same position in AllowableUnits.

Value	Effect
-1	The type is offered and never counted, so it may fill the whole loadout
0	The type is left off the cameo list and cannot be loaded
Positive	The type is offered until that many are aboard, then its cameo stops responding
Other negative	The type is offered, but its cameo never responds

Give every name a number

Write one number for each name in AllowableUnits. A shorter number list is padded with -1, but the padding supplies only half of the missing numbers, rounded up. For example, four names and one number gain two -1 entries, and the fourth name has none. A name without a number gets an unpredictable limit.

Extra numbers beyond the last name have no effect.

Keep both lists in the same order

Nothing checks that the two lists match. If they are written in a different order, or a name is removed and its number left in place, each later limit applies to whichever type now sits at that position.

See also — AllowableUnits, StartingDropships

Page feedback

Report an error or missing detail. The issue includes this page and revision.

Open issueSource revision 51b52aa38392