InvisibleInGame: Difference between revisions

Revision as of 14:08, 26 July 2013

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 a Reconnection_Error 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.

@@ Line 1: / Line 1: @@
-{{DeeZireInclusion}}<br />
+{{Flag
-Can be set to 'yes' or 'no' and determines whether or not this object is always totally invisible to all players in the game. Note that the difference between this and the Invisible= statement is that in this case the object cannot normally be targeted or destroyed which could cause problems - for this reason, it should not be applied to player-owned objects.
+|values={{values|bool}}
+|default=false
+|types={{Categ|BuildingTypes}}
+|ts=yes
+|fs=yes
+|ets=yes
+|ra2=yes
+|yr=yes
+|rp=yes
+}}
+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}}
+Player-owned objects with {{f|InvisibleInGame|yes|link}} will cause a [[Reconnection_Error]] 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.