LargeVisceroid: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 18: | Line 18: | ||
{{f|LargeVisceroid}} is read in {{ra2}} and {{yr}}, but as Visceroids will not merge, it is obsolete. | {{f|LargeVisceroid}} is read in {{ra2}} and {{yr}}, but as Visceroids will not merge, it is obsolete. | ||
== On [[VehicleTypes]] == | == On [[VehicleTypes]] == | ||
Latest revision as of 21:12, 5 April 2015
In [General]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Flag: | LargeVisceroid |
| File(s): | rules(md).ini |
| Values: | Strings: Normal text. (Limited to: VehicleTypes) |
| Applicable to: | General |
| |
The type representing the large Visceroid resulting from the merger of two small Visceroids that came within cell range of each other.
In Tiberian Sun, this has to be set to a valid type if there are SmallVisceroid=yes units, otherwise merging will result in an IE.
LargeVisceroid is read in Red Alert 2 and Yuri's Revenge, but as Visceroids will not merge, it is obsolete.
On VehicleTypes
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Flag: | LargeVisceroid |
| File(s): | rules(md).ini |
| Values: | Boolean values: yes or no, true or false, 1 or 0 |
| Default: | no |
| Applicable to: | VehicleTypes |
Defines whether this unit is a small Visceroid. Visceroids randomly wander around on their own, are immune to EMP and Jellyfish, use attack animations, retreat to the nearest patch of Tiberium when damaged into yellow health, and have a few more special properties. Large Visceroids do not try to merge with other Visceroids.
This can be used to trigger trains to move without needing map triggers, although they will be unstoppable.
In Red Alert 2 and Yuri's Revenge Visceroids will not retreat to patches of Tiberium.