Tags - Revision history

MarkJFox: 10 revisions imported

2025-03-31T20:06:09Z

10 revisions imported

← Older revision	Revision as of 22:06, 31 March 2025
(No difference)

en>Crimsonum: Info about multiple tags

2024-01-31T09:03:15Z

Info about multiple tags

← Older revision		Revision as of 11:03, 31 January 2024
Line 4:		Line 4:

	Tags are responsible for telling the game about the [[Maps/Triggers\|triggers]] present on the map. ''Each trigger needs to be referred to by at least one tag to be considered "existant" by the game'', even if the tag isn't attached to anything and thus never used itself. Linked triggers use its parent trigger's Tag. Tags can be simply placed in this section, and objects pre-placed on the map as well as [[AI/TeamTypes/Tag\|teams]] can refer to the tags for additional functionality - if they do, those specific tags and their respective triggers will be notified when the objects referring to them are somehow interacted with (detected, attacked, damaged, destroyed, etc.).		Tags are responsible for telling the game about the [[Maps/Triggers\|triggers]] present on the map. ''Each trigger needs to be referred to by at least one tag to be considered "existant" by the game'', even if the tag isn't attached to anything and thus never used itself. Linked triggers use its parent trigger's Tag. Tags can be simply placed in this section, and objects pre-placed on the map as well as [[AI/TeamTypes/Tag\|teams]] can refer to the tags for additional functionality - if they do, those specific tags and their respective triggers will be notified when the objects referring to them are somehow interacted with (detected, attacked, damaged, destroyed, etc.).

			A single trigger can be referred to by multiple tags. For example, a trigger attached to another can have its own tag in addition to its parent trigger's tag. A trigger may also have tags with different [[#ts_PERSISTENCE\|persistence states]].

	__TOC__		__TOC__

en>Crimsonum: Important note

2022-11-23T15:45:31Z

Important note

← Older revision		Revision as of 17:45, 23 November 2022
Line 67:		Line 67:
	\| Reference to the trigger related to this tag. Again, each trigger needs to be refered to by at least one tag or it will not work. [[FinalSun]] and [[FinalAlert 2]] create tags for you automatically when creating triggers in the Trigger Editor.		\| Reference to the trigger related to this tag. Again, each trigger needs to be refered to by at least one tag or it will not work. [[FinalSun]] and [[FinalAlert 2]] create tags for you automatically when creating triggers in the Trigger Editor.
	\|}		\|}

			== Important Note ==
			{{W}} The hexadecimal prefix of a tag's ID (e.g. {{tt\|02A2DA40}}) is used in pointer remapping during saving and loading. It should not be lower than {{tt\|0x01000000}} to avoid conflicts with real pointers. In addition, it should not be shared by any [[TaskForces\|TaskForce]] (local or global), else they will remap to the same pointer.

	[[Category:Map Information]]		[[Category:Map Information]]

en>E1 Elite at 04:02, 21 September 2022

2022-09-21T04:02:42Z

← Older revision		Revision as of 06:02, 21 September 2022
Line 3:		Line 3:
	{{MappingBar}}		{{MappingBar}}

	Tags are responsible for telling the game about the [[Maps/Triggers\|triggers]] present on the map. ''Each trigger needs to be referred to by at least one tag to be considered "existant" by the game'', even if the tag isn't attached to anything and thus never used itself. Tags can be simply placed in this section, and objects pre-placed on the map as well as [[AI/TeamTypes/Tag\|teams]] can refer to the tags for additional functionality - if they do, those specific tags and their respective triggers will be notified when the objects referring to them are somehow interacted with (detected, attacked, damaged, destroyed, etc.).		Tags are responsible for telling the game about the [[Maps/Triggers\|triggers]] present on the map. ''Each trigger needs to be referred to by at least one tag to be considered "existant" by the game'', even if the tag isn't attached to anything and thus never used itself. Linked triggers use its parent trigger's Tag. Tags can be simply placed in this section, and objects pre-placed on the map as well as [[AI/TeamTypes/Tag\|teams]] can refer to the tags for additional functionality - if they do, those specific tags and their respective triggers will be notified when the objects referring to them are somehow interacted with (detected, attacked, damaged, destroyed, etc.).

	__TOC__		__TOC__
Line 31:		Line 31:
	\| The tag's ID. This is used to attach this tag to other objects on the map.<br>		\| The tag's ID. This is used to attach this tag to other objects on the map.<br>
	;What can be achieved by attaching tags? : see <ul><li>[[Events]] and</li><li>[[Actions]]</li></ul>		;What can be achieved by attaching tags? : see <ul><li>[[Events]] and</li><li>[[Actions]]</li></ul>
	;How should tags be attached? : see <ul><li>[[Structures_(maps)#ts_ATTACHED_TAG\|Structures]],</li><li>[[Units_(maps)#ts_ATTACHED_TAG\|Units]],</li><li>[[Infantry_(maps)#ts_ATTACHED_TAG\|Infantry]],</li><li>[[Aircraft_(maps)#ts_ATTACHED_TAG\|Aircraft]], and</li><li>[[TeamTypes]] {{arr\|r}} [[Tag]]</li></ul>		;How should tags be attached? : see <ul><li>[[CellTags]],</li><li>[[Structures_(maps)#ts_ATTACHED_TAG\|Structures]],</li><li>[[Units_(maps)#ts_ATTACHED_TAG\|Units]],</li><li>[[Infantry_(maps)#ts_ATTACHED_TAG\|Infantry]],</li><li>[[Aircraft_(maps)#ts_ATTACHED_TAG\|Aircraft]], and</li><li>[[TeamTypes]] {{arr\|r}} [[Tag]]</li></ul>
	\|-		\|-
	! {{Anchor\|PERSISTENCE\|ts}}		! {{Anchor\|PERSISTENCE\|ts}}
Line 54:		Line 54:
	\|The tag is never removed, and will continue to "spring" every time the trigger's conditions ([[events]]) are met.		\|The tag is never removed, and will continue to "spring" every time the trigger's conditions ([[events]]) are met.
	\|}		\|}
			Map editors refer these as: 0 - OR one time, 1 - AND one time and 2 - OR repeating.

	'''Example:''' a trigger will spring when attached buildings are destroyed:		'''Example:''' a trigger will spring when attached buildings are destroyed:
	* {{tt\|0}} fires the trigger once when ''any'' of the tagged buildings is destroyed, and never again.		* {{tt\|0}} fires the trigger once when ''any'' of the tagged buildings is destroyed, and never again.

en>Crimsonum: Tabulated, and some fixes.

2022-09-14T15:15:47Z

Tabulated, and some fixes.

← Older revision		Revision as of 17:15, 14 September 2022
Line 3:		Line 3:
	{{MappingBar}}		{{MappingBar}}

	~~Map~~ Tags are responsible for telling the game about the [[Maps/Triggers\|~~Triggers~~]] present on the map. ''Each trigger needs to be referred to by at least one tag to be considered "existant" by the game'', even if the tag isn't attached to anything and thus never used itself. Tags can be simply placed in this section, and objects pre-placed on the map as well as [[AI/TeamTypes/Tag\|~~TeamTypes~~]] can refer to the tags for additional functionality - if they do, those specific tags and their respective ~~Triggers~~ will be notified when the objects referring to them are somehow interacted with (detected, attacked, damaged, destroyed, etc.).		Tags are responsible for telling the game about the [[Maps/Triggers\|triggers]] present on the map. ''Each trigger needs to be referred to by at least one tag to be considered "existant" by the game'', even if the tag isn't attached to anything and thus never used itself. Tags can be simply placed in this section, and objects pre-placed on the map as well as [[AI/TeamTypes/Tag\|teams]] can refer to the tags for additional functionality - if they do, those specific tags and their respective triggers will be notified when the objects referring to them are somehow interacted with (detected, attacked, damaged, destroyed, etc.).

	__TOC__		__TOC__
Line 23:		Line 23:
	ID=PERSISTENCE,NAME,TRIGGER_ID		ID=PERSISTENCE,NAME,TRIGGER_ID

	{\| style="width: 80%" ~~border=1~~ class="~~table_descrowdesccol~~"		{\| style="width: 80%" class="wikitable"
	\|+ Meanings of each string		\|+ Meanings of each string
	! style="width: 13em; " \| String		! style="width: 13em; " \| String
Line 29:		Line 29:
	\|-		\|-
	! {{Anchor\|ID\|ts}}		! {{Anchor\|ID\|ts}}
	\| The ~~Tag~~'s ID. This is used to attach this ~~Tag~~ to other objects on the map.<br>		\| The tag's ID. This is used to attach this tag to other objects on the map.<br>
	;What can be achieved by attaching tags? : see <li>[[Events]] and <li> [[Actions]]		;What can be achieved by attaching tags? : see <ul><li>[[Events]] and</li><li>[[Actions]]</li></ul>
	;How should tags be attached? : see <li>~~[~~[[~~Structures~~#ts_ATTACHED_TAG\|Structures]]], <li> ~~[~~[[~~Units~~#ts_ATTACHED_TAG\|Units]], <li> ~~[~~[[~~Infantry~~#ts_ATTACHED_TAG\|Infantry]]], <li> ~~[~~[[~~Aircraft~~#ts_ATTACHED_TAG\|Aircraft]]] and <li> [TeamTypes] {{arr\|r}} [[Tag]].		;How should tags be attached? : see <ul><li>[[Structures_(maps)#ts_ATTACHED_TAG\|Structures]],</li><li>[[Units_(maps)#ts_ATTACHED_TAG\|Units]],</li><li>[[Infantry_(maps)#ts_ATTACHED_TAG\|Infantry]],</li><li>[[Aircraft_(maps)#ts_ATTACHED_TAG\|Aircraft]], and</li><li>[[TeamTypes]] {{arr\|r}} [[Tag]]</li></ul>
	\|-		\|-
	! {{Anchor\|PERSISTENCE\|ts}}		! {{Anchor\|PERSISTENCE\|ts}}
	\| This flag controls if and when the tag should be removed after being triggered. Once a tag has been removed, it cannot be triggered again. Applicable values ~~are:~~		\| This flag controls if and when the tag should be removed after being triggered. Once a tag has been removed, it cannot be triggered again.
	* 0 ~~= the~~ tag is removed immediately when triggered. If the tag is attached to multiple objects, it's enough to "trip" any one of them to fire the attached trigger.		{\| style="width: 90%" class="wikitable"
	* 1 ~~= the tag is semi~~-persistent~~; it~~ maintains a count of all objects it's attached to, and only actually "springs" after it's been triggered from all the objects; then, it removes itself.		\|+Applicable values
	* 2 ~~= the~~ tag is ~~fully persistent; it just won~~'~~t go away~~.		\|-
			!Value
			!Meaning
			!Description
			\|-
			\|0
			\|Volatile
			\|The tag is removed immediately when triggered. If the tag is attached to multiple objects, it's enough to "trip" any one of them to fire the attached trigger.
			\|-
			\|1
			\|Semi-persistent
			\|The tag maintains a count of all objects it's attached to, and only actually "springs" after it's been triggered from all the objects; then, it removes itself.
			\|-
			\|2
			\|Persistent
			\|The tag is never removed, and will continue to "spring" every time the trigger's conditions ([[events]]) are met.
			\|}
	'''Example:''' a trigger will spring when attached buildings are destroyed:		'''Example:''' a trigger will spring when attached buildings are destroyed:
	* {{tt\|0}} fires the trigger once when ''any'' of the tagged buildings is destroyed, and never again.		* {{tt\|0}} fires the trigger once when ''any'' of the tagged buildings is destroyed, and never again.
Line 45:		Line 60:
	\|-		\|-
	! {{Anchor\|NAME\|ts}}		! {{Anchor\|NAME\|ts}}
	\| A plain text string used as a name of this ~~Tag~~. Not used ingame, only in the map editor. Should not contain commas.		\| A plain text string used as a name of this tag. Not used ingame, only in the map editor. Should not contain commas.
	\|-		\|-
	! {{Anchor\|TRIGGER_ID\|ts}}		! {{Anchor\|TRIGGER_ID\|ts}}
	\| Reference to the ~~Trigger~~ related to this ~~Tag~~. Again, each ~~Trigger~~ needs to be refered to by at least one ~~Tag~~ or it will not work. [[FinalSun]] and [[FinalAlert 2]] create tags for you when ~~you press "Place on map"~~ in the Trigger Editor.		\| Reference to the trigger related to this tag. Again, each trigger needs to be refered to by at least one tag or it will not work. [[FinalSun]] and [[FinalAlert 2]] create tags for you automatically when creating triggers in the Trigger Editor.
	\|}		\|}

	[[Category:Map Information]]		[[Category:Map Information]]

en>Crimsonum: Per RA1 source code and evidence from FinalAlert.

2022-09-14T13:47:53Z

Per RA1 source code and evidence from FinalAlert.

← Older revision		Revision as of 15:47, 14 September 2022
Line 21:		Line 21:
	The [{{Tt\|Tags}}] section in a map takes this format:		The [{{Tt\|Tags}}] section in a map takes this format:

	ID=~~REPEATING~~,NAME,TRIGGER_ID		ID=PERSISTENCE,NAME,TRIGGER_ID

	{\| style="width: 80%" border=1 class="table_descrowdesccol"		{\| style="width: 80%" border=1 class="table_descrowdesccol"
Line 33:		Line 33:
	;How should tags be attached? : see <li>[[[Structures#ts_ATTACHED_TAG\|Structures]]], <li> [[[Units#ts_ATTACHED_TAG\|Units]], <li> [[[Infantry#ts_ATTACHED_TAG\|Infantry]]], <li> [[[Aircraft#ts_ATTACHED_TAG\|Aircraft]]] and <li> [TeamTypes] {{arr\|r}} [[Tag]].		;How should tags be attached? : see <li>[[[Structures#ts_ATTACHED_TAG\|Structures]]], <li> [[[Units#ts_ATTACHED_TAG\|Units]], <li> [[[Infantry#ts_ATTACHED_TAG\|Infantry]]], <li> [[[Aircraft#ts_ATTACHED_TAG\|Aircraft]]] and <li> [TeamTypes] {{arr\|r}} [[Tag]].
	\|-		\|-
	! {{Anchor\|~~REPEATING~~\|ts}}		! {{Anchor\|PERSISTENCE\|ts}}
	\| ~~Can have~~ values ~~0, 1 or 2~~:~~<br>~~		\| This flag controls if and when the tag should be removed after being triggered. Once a tag has been removed, it cannot be triggered again. Applicable values are:
	0 ~~- Any of~~ the ~~associated~~ objects ~~- OR operator -~~ one ~~time<br>~~		* 0 = the tag is removed immediately when triggered. If the tag is attached to multiple objects, it's enough to "trip" any one of them to fire the attached trigger.
	1 - ~~When~~ all of the ~~associated~~ objects ~~- AND operator - one time<br>~~		* 1 = the tag is semi-persistent; it maintains a count of all objects it's attached to, and only actually "springs" after it's been triggered from all the objects; then, it removes itself.
	2 ~~- Any of~~ the ~~associated objects - OR operator - repeat<br>~~		* 2 = the tag is fully persistent; it just won't go away.

	~~Tags could be associated with more than one objects, in such cases~~ 0~~/1 can be used for~~ any ~~or all~~ of ~~them cases to activate this tag for one time~~. ~~For example in case of~~ 1~~, means activate this Tag one time~~ when all ~~the associated~~ buildings ~~having this TagID~~ are ~~destroyed, whereas a 0 would mean activate this Tag one time when any of those associated buildings get~~ destroyed. ~~By using~~ 2~~, this Tag will not stop after one~~ time~~, it will be triggered repeatedly. There~~ is ~~no AND operator for repeat or 3~~.		'''Example:''' a trigger will spring when attached buildings are destroyed:
			* {{tt\|0}} fires the trigger once when ''any'' of the tagged buildings is destroyed, and never again.
			* {{tt\|1}} fires the trigger once when ''all'' tagged buildings are destroyed.
			* {{tt\|2}} fires the trigger ''every time'' a tagged building is destroyed.
	\|-		\|-
	! {{Anchor\|NAME\|ts}}		! {{Anchor\|NAME\|ts}}

en>E1 Elite: Tags repeat case correction

2017-07-09T16:34:29Z

Tags repeat case correction

← Older revision		Revision as of 18:34, 9 July 2017
Line 34:		Line 34:
	\|-		\|-
	! {{Anchor\|REPEATING\|ts}}		! {{Anchor\|REPEATING\|ts}}
	\| Can be ~~set~~ to ~~{{Tt\|2}} ('enabled') or~~ any ~~other value ('disabled')~~. ~~Specifies whether~~ this Tag ~~is repeating - that is~~, ~~can~~ it ~~notify its attached objects more than once~~.		\| Can have values 0, 1 or 2:<br>
			0 - Any of the associated objects - OR operator - one time<br>
			1 - When all of the associated objects - AND operator - one time<br>
			2 - Any of the associated objects - OR operator - repeat<br>

			Tags could be associated with more than one objects, in such cases 0/1 can be used for any or all of them cases to activate this tag for one time. For example in case of 1, means activate this Tag one time when all the associated buildings having this TagID are destroyed, whereas a 0 would mean activate this Tag one time when any of those associated buildings get destroyed. By using 2, this Tag will not stop after one time, it will be triggered repeatedly. There is no AND operator for repeat or 3.
	\|-		\|-
	! {{Anchor\|NAME\|ts}}		! {{Anchor\|NAME\|ts}}

en>DCoder: Updating with new sidebar + anchors

2008-06-23T14:58:10Z

Updating with new sidebar + anchors

← Older revision		Revision as of 16:58, 23 June 2008
Line 1:		Line 1:
	{{WrongTitle\|[Tags]}}		{{WrongTitle\|[Tags]}}

	{{~~SideBar\|Map-specific INI sections\|Template:Mapping~~}}		{{MappingBar}}

	Map Tags are responsible for telling the game about the [[Maps/Triggers\|Triggers]] present on the map. ''Each trigger needs to be ~~refered~~ to by at least one tag to be considered "existant" by the game'', even if the tag isn't attached to anything and thus never used itself. Tags can be simply placed in this section, and objects pre-placed on the map as well as [[AI/TeamTypes/Tag\|TeamTypes]] can refer to the tags for additional functionality - if they do, those specific tags and their respective Triggers will be notified when the objects referring to them are somehow interacted with (detected, attacked, damaged, destroyed, etc.).		Map Tags are responsible for telling the game about the [[Maps/Triggers\|Triggers]] present on the map. ''Each trigger needs to be referred to by at least one tag to be considered "existant" by the game'', even if the tag isn't attached to anything and thus never used itself. Tags can be simply placed in this section, and objects pre-placed on the map as well as [[AI/TeamTypes/Tag\|TeamTypes]] can refer to the tags for additional functionality - if they do, those specific tags and their respective Triggers will be notified when the objects referring to them are somehow interacted with (detected, attacked, damaged, destroyed, etc.).

	__TOC__		__TOC__
	~~{{clr}}~~

	== Section ==		== Section ==

	=== ~~[[TD]]~~/~~[[CO]]~~ ===		=== <span id="td"></span>{{td}} ===

	~~=== [[RA]]/[[CS]]/[[AM]] ===~~		Section does not exist.

	=== ~~[[TS]]~~/~~[[FS]]~~/~~[[RA2]]~~/~~[[YR]]~~ ===		=== <span id="ra"></span>{{ra}}, {{cs}}, {{am}} ===

			Section does not exist.

			=== <span id="ts"></span><span id="ra2"></span><span id="yr"></span>{{ts}}, {{fs}}, {{ra2}}, {{yr}} ===

	The [{{Tt\|Tags}}] section in a map takes this format:		The [{{Tt\|Tags}}] section in a map takes this format:
Line 27:		Line 30:
	! {{Anchor\|ID\|ts}}		! {{Anchor\|ID\|ts}}
	\| The Tag's ID. This is used to attach this Tag to other objects on the map.<br>		\| The Tag's ID. This is used to attach this Tag to other objects on the map.<br>
	;What can be achieved by attaching tags? : see <li>[[~~Maps/Events\|~~Events]] and <li> [[~~Maps/Actions\|~~Actions]]		;What can be achieved by attaching tags? : see <li>[[Events]] and <li> [[Actions]]
	;How should tags be attached? : see <li>[[[~~Maps/~~Structures#ts_ATTACHED_TAG\|Structures]]], <li> [[[~~Maps/~~Units#ts_ATTACHED_TAG\|Units]], <li> [[[~~Maps/~~Infantry#ts_ATTACHED_TAG\|Infantry]]], <li> [[[~~Maps/~~Aircraft#ts_ATTACHED_TAG\|Aircraft]]] and <li> [TeamTypes] {{arr\|r}} [[~~AI/TeamTypes/Tag\|~~Tag]].		;How should tags be attached? : see <li>[[[Structures#ts_ATTACHED_TAG\|Structures]]], <li> [[[Units#ts_ATTACHED_TAG\|Units]], <li> [[[Infantry#ts_ATTACHED_TAG\|Infantry]]], <li> [[[Aircraft#ts_ATTACHED_TAG\|Aircraft]]] and <li> [TeamTypes] {{arr\|r}} [[Tag]].
	\|-		\|-
	! {{Anchor\|REPEATING\|ts}}		! {{Anchor\|REPEATING\|ts}}

en>Nighthawk200: Categorising.

2008-06-20T20:38:43Z

Categorising.

← Older revision		Revision as of 22:38, 20 June 2008
Line 39:		Line 39:
	\| Reference to the Trigger related to this Tag. Again, each Trigger needs to be refered to by at least one Tag or it will not work. [[FinalSun]] and [[FinalAlert 2]] create tags for you when you press "Place on map" in the Trigger Editor.		\| Reference to the Trigger related to this Tag. Again, each Trigger needs to be refered to by at least one Tag or it will not work. [[FinalSun]] and [[FinalAlert 2]] create tags for you when you press "Place on map" in the Trigger Editor.
	\|}		\|}

			[[Category:Map Information]]

en>DCoder: Maps/Tags moved to Tags: Moving the Maps/ sections' pages to main space.

2008-06-17T18:58:51Z

Maps/Tags moved to Tags: Moving the Maps/ sections' pages to main space.

← Older revision	Revision as of 20:58, 17 June 2008
(No difference)