OmniCrusher: Difference between revisions
No edit summary |
OmniCrusher must Crusher=yes |
||
| (7 intermediate revisions by 5 users not shown) | |||
| Line 6: | Line 6: | ||
|default=no | |default=no | ||
|types={{Categ|VehicleTypes}} | |types={{Categ|VehicleTypes}} | ||
| | |yr=yes | ||
|rp=yes | |||
}} | }} | ||
Specifies whether this VehicleType can crush other objects, including those labeled {{ | Specifies whether this VehicleType can crush other objects, including those labeled {{f|Crushable|no|link}}. Also apparently makes the vehicle approach mobile targets while firing its weapons at them in an attempt to crush them, rather than fire from stand-off range as normal units do, when ordered to attack. | ||
This {{f|OmniCrusher|link}} should best have the tag {{f|OmniCrushResistant|yes|link}} set, to prevent two of the same type trying to crush each other. | |||
In fact, the reason why it can ignore {{f|Crushable|no|link}} is because it only follows the setting of {{f|OmniCrushResistant|yes|link}}, rather than having a "higher-level crush"<br> | |||
for example: <br> | |||
{{f|Crusher|yes|link}} & {{f|OmniCrusher|yes|link}} vehicles can take effect on a {{f|Crushable|yes|link}} & {{f|OmniCrushResistant|yes|link}} vehicle | |||
{{Bugs}} | |||
Although the operation of the two compaction methods is separate as shown in the example, but {{f|OmniCrusher|yes|link}} only takes effect when <font style="color:red"><b>Crusher=yes</b></font>, which means it cannot be used alone. | |||
==See also== | ==See also== | ||
*[[Who crushes whom]] | *[[Who crushes whom]] | ||
Latest revision as of 07:45, 20 July 2024
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Flag: | OmniCrusher |
| File(s): | Rulesmd.ini |
| Values: | boolean |
| Special Values: | None |
| Default: | no |
| Applicable to: | VehicleTypes |
Specifies whether this VehicleType can crush other objects, including those labeled Crushable=no. Also apparently makes the vehicle approach mobile targets while firing its weapons at them in an attempt to crush them, rather than fire from stand-off range as normal units do, when ordered to attack.
This OmniCrusher should best have the tag OmniCrushResistant=yes set, to prevent two of the same type trying to crush each other.
In fact, the reason why it can ignore Crushable=no is because it only follows the setting of OmniCrushResistant=yes, rather than having a "higher-level crush"
for example:
Crusher=yes & OmniCrusher=yes vehicles can take effect on a Crushable=yes & OmniCrushResistant=yes vehicle
Bugs/Side-Effects/Unexpected Limitations
Although the operation of the two compaction methods is separate as shown in the example, but OmniCrusher=yes only takes effect when Crusher=yes, which means it cannot be used alone.