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 gives the vehicle the creature behavior that SmallVisceroid=yes describes, except merging. It wanders aimlessly, heads for Tiberium below ConditionYellow health, and draws its attack frames from AltImage.
It also has the same exemptions as a small visceroid:
NonVehicleis forced on, whatever its section says;- an EM pulse does not stun it;
- being immobilized does not stop it firing;
- it does not have to bring a turret to bear before it shoots;
- a
Jellyfish=yesunit never stings it; - it is drawn without a shadow.
A large visceroid never merges. It neither calls a neighbor over nor is called over by one, and two of them beside each other block each other’s cells like any other pair of vehicles.
This flag is separate from the type a merge produces, which LargeVisceroid in the global rules names. A type with this flag behaves as a large visceroid wherever it is placed, whether or not a merge can produce it.
Merged visceroid type
- Applies to
- global rules
- File
rules.ini- Section
[General]- Value
- class
- When omitted
none
The named UnitType is what two small visceroids become when they merge. The one that was standing still becomes this type at the type’s maximum strength and keeps its position and its house. The one that drove onto it is deleted. SmallVisceroid=yes covers how the two come together.
A merge produces exactly the type named here. Nothing checks that the type sets LargeVisceroid=yes, and the result behaves as a large visceroid only if its own section does.
A name that matches no declared UnitType creates a UnitType of that name. It is configured by a section of the same name if the rules supply one, and left blank if they do not. Only the values none and <none> name no type.