InvisibleInGame: Difference between revisions
en>Testid123 mNo edit summary |
en>Testid123 mNo edit summary |
||
| Line 19: | Line 19: | ||
*Ignore {{f|CanOccupyFire|yes|link}} | *Ignore {{f|CanOccupyFire|yes|link}} | ||
*Ignore [[Buildup]] | *Ignore [[Buildup]] | ||
*Ignore {{f|RevealToAll|yes|link}} | |||
*Gain the {{f|CanC4|no|link}} effect. | *Gain the {{f|CanC4|no|link}} effect. | ||
*Gain the {{f|Immune|yes|link}} effect. | *Gain the {{f|Immune|yes|link}} effect. | ||
*Gain the {{f|ImmuneToPsionics|yes|link}} effect. | *Gain the {{f|ImmuneToPsionics|yes|link}} effect. | ||
*Receives the {{f|IvanBomb|yes|link}} effect but does not take damage. | *Receives the {{f|IvanBomb|yes|link}} effect but does not take damage. | ||
Revision as of 18:31, 11 October 2024
|
|
|
|
|
|
| Flag: | InvisibleInGame |
| File(s): | rules(md).ini |
| Values: | Boolean values: yes or no, true or false, 1 or 0 |
| Default: | false |
| Applicable to: | BuildingTypes |
Determines whether or not this object is invisible to all players ingame, including the owner. It also cannot be targeted or destroyed by any other object on the map.
Bugs/Side-Effects/Unexpected Limitations
Player-owned objects with InvisibleInGame=yes will cause reconnection errors if their presence somehow affects other players (for example, by firing a weapon). While not all uses cause problems, as a general rule, it isn't recommended to set this tag to 'yes' on anything owned by the player.
- Adding InvisibleInGame=yes to BuildingTypes will make the building unarmed (Even if BuildingTypes has weapons).
- Ignore the number of cells between which a new wall can be connected to an existing wall (assuming there are no obstructions)GuardRange.
- Ignore tag UndeploysInto
- Ignore CanOccupyFire=yes
- Ignore Buildup
- Ignore RevealToAll=yes
- Gain the CanC4=no effect.
- Gain the Immune=yes effect.
- Gain the ImmuneToPsionics=yes effect.
- Receives the IvanBomb=yes effect but does not take damage.