ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.
InvisibleInGame: Difference between revisions
Jump to navigation
Jump to search
added info about reconnection errors caused by objects with InvisibleInGame |
mNo edit summary |
||
| Line 14: | Line 14: | ||
{{Bugs}} | {{Bugs}} | ||
Player-owned objects with {{f|InvisibleInGame|yes|link}} will cause | Player-owned objects with {{f|InvisibleInGame|yes|link}} will cause [[Reconnection_Error|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. | ||
Revision as of 12:11, 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 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.