LargeVisceroid
Makes a UnitType behave as a large visceroid, or picks the UnitType two merging small visceroids become.
Large visceroid behavior
- Applies to
- UnitType
- File
rules.ini- Section
[<ObjectType ID>]- Value
- boolean
- When omitted
no
The flag puts the vehicle on the same creature conduct that SmallVisceroid=yes describes — the aimless wandering, the run for Tiberium below ConditionYellow health, the attack frames from AltImage, and the exemptions from EM pulses, immobilization, turret facing, jellyfish stings and shadows — and it forces NonVehicle on in the same way.
What it does not carry is merging. A large visceroid neither summons a neighbor nor is summoned by one, and two of them standing beside each other block one another’s cells like any other pair of vehicles. Marking a type this way is therefore the whole of the difference: whether it grows by absorbing its own kind, or is what that absorption produces.
A type is not obliged to be reachable through merging to carry the flag. The UnitType a merge actually produces is the one named by LargeVisceroid in the global rules, which is a separate choice from this one; a type carrying this flag that nothing names there simply behaves as a large visceroid wherever it is placed.
Merged visceroid type
- Applies to
- global rules
- File
rules.ini- Section
[General]- Value
- class
- When omitted
none
The named UnitType is what a small visceroid turns into when another merges into it. The creature that was standing still keeps its position, its house and its identity on the map, and is simply given this type and that type’s full strength; the one that drove onto it deletes itself. SmallVisceroid=yes covers the approach that leads to it.
Nothing checks that the named type carries LargeVisceroid=yes itself, so the two settings can name different things: a merge produces whatever is named here, and that result behaves as a large visceroid only if its own section says so.
A name that matches no declared UnitType does not resolve to no type; a UnitType of that name is brought into existence instead, configured by a section of the same name if the rules go on to supply one and left blank if they do not. The literals none and <none> are the exception: those do resolve to no type.