How Object Arrays Work - Revision history

MarkJFox: 7 revisions imported

2025-03-31T18:57:13Z

7 revisions imported

← Older revision	Revision as of 20:57, 31 March 2025
(No difference)

en>DCoder: "indecies" is not a word, but DCoder is a monkey

2006-09-11T17:56:23Z

"indecies" is not a word, but DCoder is a monkey

en>DCoder: Added explicit note about duplicate entries

2006-07-11T03:54:08Z

Added explicit note about duplicate entries

← Older revision		Revision as of 05:54, 11 July 2006
Line 64:		Line 64:
	A: Make sure you capitalize the objects identically everywhere you reference them. If you say		A: Make sure you capitalize the objects identically everywhere you reference them. If you say
	[VehicleTypes] 75=AtNk, please be so nice and use [AtNk] as the rules section name. If you say [AtNk] Image=ATnK, use [ATnK] in the art file. Get the pattern?		[VehicleTypes] 75=AtNk, please be so nice and use [AtNk] as the rules section name. If you say [AtNk] Image=ATnK, use [ATnK] in the art file. Get the pattern?

			=== Q: What about duplicate entries, like 15=FOO and 75=FOO ? ===

			A: The first one is loaded, the second one is discarded as if it was commented out. Removing it will have no effect on the numbering, but replacing it with something else will.

	[[Category:General Editing Information]]		[[Category:General Editing Information]]

en>DCoder: Q: What about capitalization of the section names?

2006-02-26T09:25:46Z

Q: What about capitalization of the section names?

← Older revision		Revision as of 11:25, 26 February 2006
Line 59:		Line 59:

	A: Not quite. They have made a lot of little mistakes, which add up and look sloppy. I have fixed some of them (the ugliest ones) and posted them on their corresponding pages, [[BuildingTypes]] and [[Animations]]. More corrected versions will follow soon.		A: Not quite. They have made a lot of little mistakes, which add up and look sloppy. I have fixed some of them (the ugliest ones) and posted them on their corresponding pages, [[BuildingTypes]] and [[Animations]]. More corrected versions will follow soon.

			=== Q: What about capitalization of the section names? ===

			A: Make sure you capitalize the objects identically everywhere you reference them. If you say
			[VehicleTypes] 75=AtNk, please be so nice and use [AtNk] as the rules section name. If you say [AtNk] Image=ATnK, use [ATnK] in the art file. Get the pattern?

	[[Category:General Editing Information]]		[[Category:General Editing Information]]

en>DCoder: A quirk in the system?

2006-01-17T07:21:58Z

A quirk in the system?

← Older revision	Revision as of 09:21, 17 January 2006
Line 1:	Line 1:
		== How Object Arrays Work ==

		I've seen the question asked over and over at various forums, so I figured this should be made common knowledge.

		The object arrays ( [InfantryTypes] , [Movies] , [Tiberiums], etc. ) are internally 0-based. That means, the first item listed in such an array will always have index #0 ingame, the second one will be #1, and so on, regardless of what the text on the left of the equals sign says. You can have things like a^2+b^2=CSQUARED and the game would recognize CSQUARED and put it into the array correctly.

		These internal indecies are a way how the game refers to these objects, widely used by AI scripts and map triggers. So, a map trigger action that says "Play Animation #250 at waypoint 45" will play the animation that has the internal index of #250 in the [Animations] list, '''which is not necessarily [Animations]250='''.

		All new entries (from mpmode files and map files) are appended to the end of the appropriate arrays, provided their entries are not in them already.

		For example:

		rules.ini contains
		[AircraftTypes]
		4=ORCA
		1=ORCAB
		0=SCRIN
		11=MIG
		9500=DUMMYOBJECT
		-7=APACHE

		and map75.mpr contains
		[AircraftTypes]
		1=SCRIN
		3=ROFLCOPTER
		49=B52

		So, when you're playing on map75.mpr, the game builds the [AircraftTypes] array as follows:
		[AircraftTypes]
		0=ORCA
		1=ORCAB
		2=SCRIN
		3=MIG
		4=DUMMYOBJECT
		5=APACHE
		6=ROFLCOPTER
		7=B52

		And when you're playing on emptymap.mpr, which doesn't define new [AircraftTypes], the array will be
		[AircraftTypes]
		0=ORCA
		1=ORCAB
		2=SCRIN
		3=MIG
		4=DUMMYOBJECT
		5=APACHE

		== Common Questions & Answers ==

		=== Q. So can I place anything silly to the left of the equals sign, and it won't affect anything? ===

		A: Yes, while you can place almost (except for the = sign itself...) anything to the left of the equals sign, it makes most sense to keep the numbering identical to the one used ingame.

		=== Q: What features break if I break the existing ordering (say, by adding new items to the middle of the list)? ===

		A: No matter whether you added or removed items from the middle of the array, you messed up the internal ordering. The consequences - almost every array of the game has a corresponding map trigger and/or AI script action that calls for an object from that array via index. So, reordering those lists is '''not''' advised under any circumstances. Add your new objects to the end of it.

		=== Q: Are Westwood's unmodded arrays correct? ===

		A: Not quite. They have made a lot of little mistakes, which add up and look sloppy. I have fixed some of them (the ugliest ones) and posted them on their corresponding pages, [[BuildingTypes]] and [[Animations]]. More corrected versions will follow soon.
		[[Category:General Editing Information]]

en>DCoder at 07:20, 17 January 2006

2006-01-17T07:20:08Z

← Older revision		Revision as of 09:20, 17 January 2006
Line 1:		Line 1:
	~~== How Object Arrays Work ==~~

	~~I've seen the question asked over and over at various forums, so I figured this should be made common knowledge.~~

	The object arrays ( [InfantryTypes] , [Movies] , [Tiberiums], etc. ) are internally 0-based. That means, the first item listed in such an array will always have index #0 ingame, the second one will be #1, and so on, regardless of what the text on the left of the equals sign says. You can have things like a^2+b^2=CSQUARED and the game would recognize CSQUARED and put it into the array correctly.

	These internal indecies are a way how the game refers to these objects, widely used by AI scripts and map triggers. So, a map trigger action that says "Play Animation #250 at waypoint 45" will play the animation that has the internal index of #45 in the [Animations] list, '''which is not necessarily [Animations]45='''.

	~~All new entries (from mpmode files and map files) are appended to the end of the appropriate arrays, provided their entries are not in them already.~~

	~~For example:~~

	~~rules.ini contains~~
	~~[AircraftTypes]~~
	~~4=ORCA~~
	~~1=ORCAB~~
	~~0=SCRIN~~
	~~11=MIG~~
	~~9500=DUMMYOBJECT~~
	~~-7=APACHE~~

	~~and map75.mpr contains~~
	~~[AircraftTypes]~~
	~~1=SCRIN~~
	~~3=ROFLCOPTER~~
	~~49=B52~~

	~~So, when you're playing on map75.mpr, the game builds the [AircraftTypes] array as follows:~~
	~~[AircraftTypes]~~
	~~0=ORCA~~
	~~1=ORCAB~~
	~~2=SCRIN~~
	~~3=MIG~~
	~~4=DUMMYOBJECT~~
	~~5=APACHE~~
	~~6=ROFLCOPTER~~
	~~7=B52~~

	~~And when you're playing on emptymap.mpr, which doesn't define new [AircraftTypes], the array will be~~
	~~[AircraftTypes]~~
	~~0=ORCA~~
	~~1=ORCAB~~
	~~2=SCRIN~~
	~~3=MIG~~
	~~4=DUMMYOBJECT~~
	~~5=APACHE~~

	~~== Common Questions & Answers ==~~

	~~=== Q. So can I place anything silly to the left of the equals sign, and it won't affect anything? ===~~

	~~A: Yes, while you can place almost (except for the = sign itself...) anything to the left of the equals sign, it makes most sense to keep the numbering identical to the one used ingame.~~

	~~=== Q: What features break if I break the existing ordering (say, by adding new items to the middle of the list)? ===~~

	A: No matter whether you added or removed items from the middle of the array, you messed up the internal ordering. The consequences - almost every array of the game has a corresponding map trigger and/or AI script action that calls for an object from that array via index. So, reordering those lists is '''not''' advised under any circumstances. Add your new objects to the end of it.

	~~=== Q: Are Westwood's unmodded arrays correct? ===~~

	A: Not quite. They have made a lot of little mistakes, which add up and look sloppy. I have fixed some of them (the ugliest ones) and posted them on their corresponding pages, [[BuildingTypes]] and [[Animations]]. More corrected versions will follow soon.
	~~[[Category:General Editing Information]]~~

en>DCoder at 17:18, 14 January 2006

2006-01-14T17:18:49Z

← Older revision		Revision as of 19:18, 14 January 2006
Line 4:		Line 4:

	The object arrays ( [InfantryTypes] , [Movies] , [Tiberiums], etc. ) are internally 0-based. That means, the first item listed in such an array will always have index #0 ingame, the second one will be #1, and so on, regardless of what the text on the left of the equals sign says. You can have things like a^2+b^2=CSQUARED and the game would recognize CSQUARED and put it into the array correctly.		The object arrays ( [InfantryTypes] , [Movies] , [Tiberiums], etc. ) are internally 0-based. That means, the first item listed in such an array will always have index #0 ingame, the second one will be #1, and so on, regardless of what the text on the left of the equals sign says. You can have things like a^2+b^2=CSQUARED and the game would recognize CSQUARED and put it into the array correctly.

			These internal indecies are a way how the game refers to these objects, widely used by AI scripts and map triggers. So, a map trigger action that says "Play Animation #250 at waypoint 45" will play the animation that has the internal index of #45 in the [Animations] list, '''which is not necessarily [Animations]45='''.

	All new entries (from mpmode files and map files) are appended to the end of the appropriate arrays, provided their entries are not in them already.		All new entries (from mpmode files and map files) are appended to the end of the appropriate arrays, provided their entries are not in them already.

en>DCoder: Created the page.

2006-01-14T16:44:21Z

Created the page.

New page

== How Object Arrays Work ==

I've seen the question asked over and over at various forums, so I figured this should be made common knowledge.

The object arrays ( [InfantryTypes] , [Movies] , [Tiberiums], etc. ) are internally 0-based. That means, the first item listed in such an array will always have index #0 ingame, the second one will be #1, and so on, regardless of what the text on the left of the equals sign says. You can have things like a^2+b^2=CSQUARED and the game would recognize CSQUARED and put it into the array correctly.

All new entries (from mpmode files and map files) are appended to the end of the appropriate arrays, provided their entries are not in them already.

For example:

rules.ini contains
[AircraftTypes]
4=ORCA
1=ORCAB
0=SCRIN
11=MIG
9500=DUMMYOBJECT
-7=APACHE

and map75.mpr contains
[AircraftTypes]
1=SCRIN
3=ROFLCOPTER
49=B52

So, when you're playing on map75.mpr, the game builds the [AircraftTypes] array as follows:
[AircraftTypes]
0=ORCA
1=ORCAB
2=SCRIN
3=MIG
4=DUMMYOBJECT
5=APACHE
6=ROFLCOPTER
7=B52

And when you're playing on emptymap.mpr, which doesn't define new [AircraftTypes], the array will be
[AircraftTypes]
0=ORCA
1=ORCAB
2=SCRIN
3=MIG
4=DUMMYOBJECT
5=APACHE

== Common Questions & Answers ==

=== Q. So can I place anything silly to the left of the equals sign, and it won't affect anything? ===

A: Yes, while you can place almost (except for the = sign itself...) anything to the left of the equals sign, it makes most sense to keep the numbering identical to the one used ingame.

=== Q: What features break if I break the existing ordering (say, by adding new items to the middle of the list)? ===

A: No matter whether you added or removed items from the middle of the array, you messed up the internal ordering. The consequences - almost every array of the game has a corresponding map trigger and/or AI script action that calls for an object from that array via index. So, reordering those lists is '''not''' advised under any circumstances. Add your new objects to the end of it.

=== Q: Are Westwood's unmodded arrays correct? ===

A: Not quite. They have made a lot of little mistakes, which add up and look sloppy. I have fixed some of them (the ugliest ones) and posted them on their corresponding pages, [[BuildingTypes]] and [[Animations]]. More corrected versions will follow soon.
[[Category:General Editing Information]]

← Older revision		Revision as of 19:56, 11 September 2006
Line 5:		Line 5:
	The object arrays ( [InfantryTypes] , [Movies] , [Tiberiums], etc. ) are internally 0-based. That means, the first item listed in such an array will always have index #0 ingame, the second one will be #1, and so on, regardless of what the text on the left of the equals sign says. You can have things like a^2+b^2=CSQUARED and the game would recognize CSQUARED and put it into the array correctly.		The object arrays ( [InfantryTypes] , [Movies] , [Tiberiums], etc. ) are internally 0-based. That means, the first item listed in such an array will always have index #0 ingame, the second one will be #1, and so on, regardless of what the text on the left of the equals sign says. You can have things like a^2+b^2=CSQUARED and the game would recognize CSQUARED and put it into the array correctly.

	These internal ~~indecies~~ are a way how the game refers to these objects, widely used by AI scripts and map triggers. So, a map trigger action that says "Play Animation #250 at waypoint 45" will play the animation that has the internal index of #250 in the [Animations] list, '''which is not necessarily [Animations]250='''.		These internal indices are a way how the game refers to these objects, widely used by AI scripts and map triggers. So, a map trigger action that says "Play Animation #250 at waypoint 45" will play the animation that has the internal index of #250 in the [Animations] list, '''which is not necessarily [Animations]250='''.

	All new entries (from mpmode files and map files) are appended to the end of the appropriate arrays, provided their entries are not in them already.		All new entries (from mpmode files and map files) are appended to the end of the appropriate arrays, provided their entries are not in them already.
Line 48:		Line 48:
	== Common Questions & Answers ==		== Common Questions & Answers ==

	=== Q. So can I place ~~anything~~ silly to the left of the equals sign~~, and it won't affect anything~~? ===		=== Q. So can I place silly words to the left of the equals sign without any problems? ===

	A: Yes, while you can place almost (except for the = sign itself...) anything to the left of the equals sign, it makes most sense to keep the numbering identical to the one used ingame.		A: Yes, while you can place almost (except for the = sign itself...) anything to the left of the equals sign, it makes most sense to keep the numbering identical to the one used ingame.
Line 63:		Line 63:

	A: Make sure you capitalize the objects identically everywhere you reference them. If you say		A: Make sure you capitalize the objects identically everywhere you reference them. If you say
	[VehicleTypes] 75=AtNk, please be so nice and use [AtNk] as the rules section name. If you say [AtNk] Image=ATnK, use [ATnK] in the art file. Get the pattern?		{{Tt\|[VehicleTypes] 75{{equal}}AtNk}}, please be so nice and use {{Tt\|[AtNk]}} as the rules section name. If you say {{Tt\|[AtNk] Image{{equal}}ATnK}}, use {{Tt\|[ATnK]}} in the art file. Get the pattern?

	=== Q: What about duplicate entries, like 15=FOO and 75=FOO ? ===		=== Q: What about duplicate entries, like {{Tt\|15{{equal}}FOO}} and {{Tt\|75{{equal}}FOO}} ? ===

	A: The first one is loaded, the second one is discarded as if it was commented out. Removing it will have no effect on the numbering, but replacing it with something else will.		A: The first one is loaded, the second one is discarded as if it was commented out. Removing it will have no effect on the numbering, but replacing it with something else will.

	[[Category:General Editing Information]]		[[Category:General Editing Information]]