Referencing (maps) - Revision history

MarkJFox: 5 revisions imported

2025-03-31T20:03:20Z

5 revisions imported

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

en>Nighthawk200: Maps/Referencing moved to Referencing (maps): Moving.

2008-06-18T09:26:27Z

Maps/Referencing moved to Referencing (maps): Moving.

← Older revision	Revision as of 11:26, 18 June 2008
(No difference)

en>Nighthawk200 at 17:15, 29 April 2007

2007-04-29T17:15:25Z

← Older revision		Revision as of 19:15, 29 April 2007
Line 6:		Line 6:
	::Also note: '''All''' entries in column P7 are expected to be literal, so you have to convert all the numbers into letters like this:		::Also note: '''All''' entries in column P7 are expected to be literal, so you have to convert all the numbers into letters like this:
	:: 0 is "A", 1 is "B", 25 is "Z", 26 is "AA", just like the columnm numbering in your favourite spreadsheet program.		:: 0 is "A", 1 is "B", 25 is "Z", 26 is "AA", just like the columnm numbering in your favourite spreadsheet program.
			[[Category:Map_Information]]

en>DCoder: P7 note

2006-09-14T12:02:11Z

P7 note

← Older revision		Revision as of 14:02, 14 September 2006
Line 4:		Line 4:
	:Some parameters take their values to be indexes of objects, others assume they are the identifiers of those objects.<br />		:Some parameters take their values to be indexes of objects, others assume they are the identifiers of those objects.<br />
	:For convenience, if the parameter's description in the table ends with a "#" symbol, you should use the object's index in its appropriate list, otherwise you should use its ID.		:For convenience, if the parameter's description in the table ends with a "#" symbol, you should use the object's index in its appropriate list, otherwise you should use its ID.
			::Also note: '''All''' entries in column P7 are expected to be literal, so you have to convert all the numbers into letters like this:
			:: 0 is "A", 1 is "B", 25 is "Z", 26 is "AA", just like the columnm numbering in your favourite spreadsheet program.

en>DCoder: Reworded to make sense

2006-09-14T11:52:02Z

Reworded to make sense

← Older revision		Revision as of 13:52, 14 September 2006
Line 2:		Line 2:

	:As you probably noticed, some of the Parameter descriptions in this table end with "#". The reason for that is:<br />		:As you probably noticed, some of the Parameter descriptions in this table end with "#". The reason for that is:<br />
	~~The~~ parameters ~~referring~~ to objects ~~that~~ are ~~restricted to having only hexadecimal~~ identifiers ~~(Tags, Triggers, Events, TeamTypes) refer to them by their ID, but the parameters referring to other~~ objects (those which can have non-numeric IDs), refer to them by their index in the corresponding ObjectList. For example, a parameter requiring "TeamType ID" should get the TeamType's ID (eg, {{Tt\|12AC14FF}}), but a parameter asking for an "Infantry#" should get that particular infantry's index in the InfantryTypes list, not its ID. <br />		:Some parameters take their values to be indexes of objects, others assume they are the identifiers of those objects.<br />
	For convenience, if the parameter's description in the table ends with a "#" symbol, you should use the object's index, otherwise you should use its ID.		:For convenience, if the parameter's description in the table ends with a "#" symbol, you should use the object's index in its appropriate list, otherwise you should use its ID.

	~~{{NeedTesting}}~~
	~~This poses the question, what happens if you create a TeamType that has a non-hexadecimal identifier and invoke it through such an Event or Action?~~

en>DCoder: Created (as a blob for inclusion on TS-YR Ev/Ac pages)

2006-09-14T10:27:51Z

Created (as a blob for inclusion on TS-YR Ev/Ac pages)

New page

;Referencing items

:As you probably noticed, some of the Parameter descriptions in this table end with "#". The reason for that is:<br />
The parameters referring to objects that are restricted to having only hexadecimal identifiers (Tags, Triggers, Events, TeamTypes) refer to them by their ID, but the parameters referring to other objects (those which can have non-numeric IDs), refer to them by their index in the corresponding ObjectList. For example, a parameter requiring "TeamType ID" should get the TeamType's ID (eg, {{Tt|12AC14FF}}), but a parameter asking for an "Infantry#" should get that particular infantry's index in the InfantryTypes list, not its ID. <br />
For convenience, if the parameter's description in the table ends with a "#" symbol, you should use the object's index, otherwise you should use its ID.

{{NeedTesting}}
This poses the question, what happens if you create a TeamType that has a non-hexadecimal identifier and invoke it through such an Event or Action?