Passengers: Difference between revisions
en>ATHSE No edit summary |
m 22 revisions imported |
||
| (One intermediate revision by one other user not shown) | |||
| Line 19: | Line 19: | ||
Functionality difference between games: | Functionality difference between games: | ||
*RA/CS/AM | |||
::*capacity is an absolute passenger capacity, every passenger unit using up one slot. | ::*capacity is an absolute passenger capacity, every passenger unit using up one slot. | ||
*TS/FS/RA2/YR | |||
::*passenger capacity equals the transport units own {{f|Size|link}} if not specified. | ::*passenger capacity equals the transport units own {{f|Size|link}} if not specified. | ||
::*capacity is the limit of all passenger {{f|Size|link}} values combined allowed to enter. | ::*capacity is the limit of all passenger {{f|Size|link}} values combined allowed to enter. | ||
Latest revision as of 22:00, 31 March 2025
|
|
|
|
|
|
| Flag: | Passengers |
| File(s): | Rules(md).ini |
| Values: | integers |
| Default: | 0 |
| Applicable to: | VehicleTypes, AircraftTypes, BuildingTypes |
On VehicleTypes and AircraftTypes
This tag defines the transport units capacity, and is required for all transports. A transport vehicle is defined by the Category=Transport tag.
Functionality difference between games:
- RA/CS/AM
- capacity is an absolute passenger capacity, every passenger unit using up one slot.
- TS/FS/RA2/YR
- passenger capacity equals the transport units own Size if not specified.
- capacity is the limit of all passenger Size values combined allowed to enter.
- passengers exceeding this transport units SizeLimit are not allowed to enter.
- transport unit should have PipScale=Passengers set.
Caveat: Certain objects have additional hardcoded conditions preventing some objects from entering others.
On BuildingTypes
In YR, this tag determines the amount of objects allowed inside if this structure has InfantryAbsorb=yes or UnitAbsorb=yes.
Unlike on transports, each object takes up exactly one slot.