Skip to content

SmallVisceroid

Makes a UnitType behave as a small visceroid, or picks the UnitType that Tiberium deaths spawn.

Small visceroid behavior

Specification — Small visceroid behavior
Applies to
UnitType
File
rules.ini
Section
[<ObjectType ID>]
Value
boolean
When omitted
no

The flag puts the vehicle on the creature’s conduct instead of a vehicle’s. Standing still on a guard or empty mission with no destination and no target, it picks one of the eight directions — keeping the last one two times in three — and steps into that cell when it can enter it. Below ConditionYellow health it heads instead for Tiberium within a sixteen-cell search radius, and once it is standing on Tiberium it accepts only another Tiberium cell as its next step.

Merging is what separates it from a LargeVisceroid=yes type. Standing still, it looks at the eight cells around it from north clockwise and stops at the first that holds another small visceroid; if that one has no destination and no target of its own, it is sent here. Finding a neighbor ends the pass either way, so a visceroid with one beside it neither wanders nor makes for Tiberium that frame. Two small visceroids never block each other’s cell, so the one that was sent drives all the way onto this one — and on arrival the visceroid it was sent to is turned into the UnitType named by LargeVisceroid at that type’s full strength, while the arriving one deletes itself.

Both visceroid flags carry the same handful of exemptions. NonVehicle is forced on after this key is read, whatever the section said. An EM pulse passes over the creature without stunning it, and being immobilized does not stop it firing, which no other object may do. It is not required to bring a turret to bear before it shoots, a Jellyfish=yes unit never stings it, and it is drawn without a shadow — from its ordinary artwork while wandering and from AltImage for the five frames of an attack.

Spawned visceroid type

Specification — Spawned visceroid type
Applies to
global rules
File
rules.ini
Section
[General]
Value
class
When omitted
none

The named UnitType is the creature Tiberium leaves behind, and it is created for the Neutral house rather than for whoever owned the victim. Two deaths reach it, both only while the scenario declares TiberiumDeathToVisceroid=yes: an infantryman killed by the Tiberium under its feet, and any object killed by a damaging particle. In each case the new creature appears on the cell the death happened in, and is left uncreated if a vehicle already occupies that cell.

Damage covers the hit that produces the first of those deaths.

The name here does not have to belong to a declared UnitType. A name that matches nothing 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.