Insignificant - Revision history

MarkJFox: 8 revisions imported

2025-03-31T19:53:19Z

8 revisions imported

← Older revision	Revision as of 21:53, 31 March 2025
(No difference)

en>Mrwinde at 07:42, 19 May 2017

2017-05-19T07:42:56Z

← Older revision		Revision as of 09:42, 19 May 2017
Line 3:		Line 3:
	\|values={{values\|bool}}		\|values={{values\|bool}}
	\|default=false		\|default=false
	\|types={{Categ\|~~InfantryTypes}}, {{Categ\|VehicleTypes}}, {{Categ\|AircraftTypes}}, {{Categ\|BuildingTypes~~}}		\|types={{Categ\|TechnoTypes}}
	\|ts=yes		\|ts=yes
	\|fs=yes		\|fs=yes
Line 9:		Line 9:
	\|ra2=yes		\|ra2=yes
	\|yr=yes		\|yr=yes
	\|rp=yes		\|ares=yes
	}}		}}

en>Crimsonum at 11:49, 4 December 2016

2016-12-04T11:49:16Z

← Older revision		Revision as of 13:49, 4 December 2016
Line 18:		Line 18:

	== Notes ==		== Notes ==
	Setting it to 'yes' for a building will make some Super Weapons unable to fire or fire incorrectly from it. Also, if the building has a [[NumberOfDocks\|dock]], units won't be able to automatically dock on it, even if the structure is listed in their [[Dock\|docking]] list.		* Setting it to 'yes' for a building will make some Super Weapons unable to fire or fire incorrectly from it. Also, if the building has a [[NumberOfDocks\|dock]], units won't be able to automatically dock on it, even if the structure is listed in their [[Dock\|docking]] list.
			* All objects with this tag ignore their {{f\|BuildLimit\|link}}, if they have any.
	All objects with this tag ignore their {{f\|BuildLimit\|link}}, if they have any.		* Using an object with Insignificant=yes with a trigger [[Events\|event]] will cause the event to be ignored. Hence if the trigger is [[Triggers#td_REPEATING\|dependent on this event]], it will not be able to spring.

en>Mevitar at 17:02, 2 September 2015

2015-09-02T17:02:57Z

← Older revision		Revision as of 19:02, 2 September 2015
Line 14:		Line 14:
	Setting this tag makes the object ignored for scoring and killing purposes. Although still owned by the player, the object isn't treated as such for the purpose of winning condition. Furthermore, enemy attackers will ignore this object when scanning for targets.		Setting this tag makes the object ignored for scoring and killing purposes. Although still owned by the player, the object isn't treated as such for the purpose of winning condition. Furthermore, enemy attackers will ignore this object when scanning for targets.

	==In ~~{{ra2}} and~~ {{yr}}==		==In {{yr}}==
	Units that are affected by a weapon with {{f\|MindControl\|yes\|link}} are still considered valid targets by the AI.		Units that are affected by a weapon with {{f\|MindControl\|yes\|link}} are still considered valid targets by the AI.

en>Mevitar: added information about MindControl special case

2015-09-02T17:00:05Z

added information about MindControl special case

← Older revision		Revision as of 19:00, 2 September 2015
Line 13:		Line 13:

	Setting this tag makes the object ignored for scoring and killing purposes. Although still owned by the player, the object isn't treated as such for the purpose of winning condition. Furthermore, enemy attackers will ignore this object when scanning for targets.		Setting this tag makes the object ignored for scoring and killing purposes. Although still owned by the player, the object isn't treated as such for the purpose of winning condition. Furthermore, enemy attackers will ignore this object when scanning for targets.

			==In {{ra2}} and {{yr}}==
			Units that are affected by a weapon with {{f\|MindControl\|yes\|link}} are still considered valid targets by the AI.

	== Notes ==		== Notes ==

en>Mevitar: doesn't suppress "unit lost" announcement after all

2013-08-01T19:38:19Z

doesn't suppress "unit lost" announcement after all

← Older revision		Revision as of 21:38, 1 August 2013
Line 12:		Line 12:
	}}		}}

	Setting this tag makes the object ignored for scoring and killing purposes~~, also disabling EVA 'unit lost' announcements for it~~. Although still owned by the player, the object isn't treated as such for the purpose of winning condition. Furthermore, enemy attackers will ignore this object when scanning for targets.		Setting this tag makes the object ignored for scoring and killing purposes. Although still owned by the player, the object isn't treated as such for the purpose of winning condition. Furthermore, enemy attackers will ignore this object when scanning for targets.

	== Notes ==		== Notes ==

en>Mevitar at 16:19, 26 July 2013

2013-07-26T16:19:45Z

← Older revision		Revision as of 18:19, 26 July 2013
Line 15:		Line 15:

	== Notes ==		== Notes ==
	Setting it to 'yes' for a building will make some Super Weapons unable to fire or fire incorrectly from it. If the building has a [[NumberOfDocks\|dock]], units won't be able to automatically dock on it, even if the structure is listed in their [[Dock\|docking]] list.		Setting it to 'yes' for a building will make some Super Weapons unable to fire or fire incorrectly from it. Also, if the building has a [[NumberOfDocks\|dock]], units won't be able to automatically dock on it, even if the structure is listed in their [[Dock\|docking]] list.

	All objects with this tag ignore their {{f\|BuildLimit\|link}}, if they have any.		All objects with this tag ignore their {{f\|BuildLimit\|link}}, if they have any.

en>Mevitar: expanded info on the tag

2013-07-26T16:18:52Z

expanded info on the tag

← Older revision		Revision as of 18:18, 26 July 2013
Line 1:		Line 1:
	{{~~DeeZireInclusion~~}}~~<br />~~		{{Flag
	~~Can be set to '~~yes' ~~or 'no~~'. ~~This defaults to 'no~~' for ~~all objects as setting it to 'yes' means that~~ the object ~~is not counted for scoring and kills purposes~~ when ~~destroyed and therefore will not be included in the logic which accumulates scoring~~ for ~~objects improving with veterancy~~. Setting ~~this~~ to 'yes' on a ~~player-owned unit~~ has ~~been known~~ to ~~cause issues~~ if ~~that unit also has a~~ BuildLimit~~= set~~, ~~where that limit can be exceeded~~.		\|name={{PAGENAME}}
			\|values={{values\|bool}}
			\|default=false
			\|types={{Categ\|InfantryTypes}}, {{Categ\|VehicleTypes}}, {{Categ\|AircraftTypes}}, {{Categ\|BuildingTypes}}
			\|ts=yes
			\|fs=yes
			\|ets=yes
			\|ra2=yes
			\|yr=yes
			\|rp=yes
			}}

			Setting this tag makes the object ignored for scoring and killing purposes, also disabling EVA 'unit lost' announcements for it. Although still owned by the player, the object isn't treated as such for the purpose of winning condition. Furthermore, enemy attackers will ignore this object when scanning for targets.

			== Notes ==
			Setting it to 'yes' for a building will make some Super Weapons unable to fire or fire incorrectly from it. If the building has a [[NumberOfDocks\|dock]], units won't be able to automatically dock on it, even if the structure is listed in their [[Dock\|docking]] list.

			All objects with this tag ignore their {{f\|BuildLimit\|link}}, if they have any.

en>DCoder at 15:52, 5 May 2006

2006-05-05T15:52:50Z

New page

{{DeeZireInclusion}}<br />
Can be set to 'yes' or 'no'. This defaults to 'no' for all objects as setting it to 'yes' means that the object is not counted for scoring and kills purposes when destroyed and therefore will not be included in the logic which accumulates scoring for objects improving with veterancy. Setting this to 'yes' on a player-owned unit has been known to cause issues if that unit also has a BuildLimit= set, where that limit can be exceeded.