Hardcoded - Revision history

MarkJFox: 19 revisions imported

2025-03-31T18:57:13Z

19 revisions imported

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

en>AlexB: /* Why do I need to know this stuff? */

2015-01-22T14:43:58Z

Why do I need to know this stuff?

← Older revision		Revision as of 16:43, 22 January 2015
Line 8:		Line 8:
	=== Why do I need to know this stuff? ===		=== Why do I need to know this stuff? ===

	There are two benefits from knowing the hardcoded ~~suff~~:		There are two benefits from knowing the hardcoded stuff:

	#Saves time and energy in your mind.		#Saves time and energy in your mind.

128.12.176.34 at 07:21, 22 January 2015

2015-01-22T07:21:35Z

← Older revision		Revision as of 09:21, 22 January 2015
Line 4:		Line 4:
	=== What is hardcoding? ===		=== What is hardcoding? ===

	Hard code is code held in the binary executable. Basically it's the things that are out of your hands when it comes to C&C modding. Reasons why some stuff has its behaviour handled purely by the binary code are likely varied and are probably due to time constraints or a lack of ~~nessesity~~ for [[Westwood]] to actually ever vary some behaviour.		Hard code is code held in the binary executable. Basically it's the things that are out of your hands when it comes to C&C modding. Reasons why some stuff has its behaviour handled purely by the binary code are likely varied and are probably due to time constraints or a lack of necessity for [[Westwood]] to actually ever vary some behaviour.

	=== Why do I need to know this stuff? ===		=== Why do I need to know this stuff? ===

	~~well there~~ are 2 benefits from knowing the hardcoded suff:		There are two benefits from knowing the hardcoded suff:

	#Saves time and energy in your mind.		#Saves time and energy in your mind.

en>EvilRenegade: Replacing Template:TTL with Template:F.

2009-11-27T08:06:09Z

Replacing Template:TTL with Template:F.

← Older revision		Revision as of 10:06, 27 November 2009
Line 15:		Line 15:
	== Features that are hard coded ==		== Features that are hard coded ==

	# [[Superweapons]]: basically, superweapons can ONLY be replaced by altering the art assets and warheads that they use and the scope for modifying their behaviour (how they do their damage) is generally limited. All though it is possible to add more superweapons to the list, the {{~~TTL~~\|Type}} value controls what behaviour that super weapon will use. This would allow you to make multiple versions of the same superweapon so you could charge and fire more than one at a time were it not for the fact that every superweapon needs a unique {{~~TTL~~\|Action}} to give it a cursor and targeting. Via some clever ini editing, some members of the editing community have succeeded in creating superweapon like behaviour for some new weapons, but their targeting is handled differently from true superweapons.		# [[Superweapons]]: basically, superweapons can ONLY be replaced by altering the art assets and warheads that they use and the scope for modifying their behaviour (how they do their damage) is generally limited. All though it is possible to add more superweapons to the list, the {{f\|Type\|link}} value controls what behaviour that super weapon will use. This would allow you to make multiple versions of the same superweapon so you could charge and fire more than one at a time were it not for the fact that every superweapon needs a unique {{f\|Action\|link}} to give it a cursor and targeting. Via some clever ini editing, some members of the editing community have succeeded in creating superweapon like behaviour for some new weapons, but their targeting is handled differently from true superweapons.
	# [[Sides]]: Depending on the C&C title, there are either two or three playable sides with two additional sides for neutral units and structures. For the playable sides they represent the main factions in the game and are often sub divided into countries (though internally they are called houses for the most part). In RA2/YR, the number of countries is also limited by code in the [[executable]] that identifies what art assets are assigned for loading screens. The playable sides are always 'GDI', 'Nod' and where applicable 'ThirdSide'.		# [[Sides]]: Depending on the C&C title, there are either two or three playable sides with two additional sides for neutral units and structures. For the playable sides they represent the main factions in the game and are often sub divided into countries (though internally they are called houses for the most part). In RA2/YR, the number of countries is also limited by code in the [[executable]] that identifies what art assets are assigned for loading screens. The playable sides are always 'GDI', 'Nod' and where applicable 'ThirdSide'.
	# Multiplayer [[Colors\|Color]] Selection Menu: The colours that are displayed are fixed, even though you can change what they result in in [[rules.ini]].		# Multiplayer [[Colors\|Color]] Selection Menu: The colours that are displayed are fixed, even though you can change what they result in in [[rules.ini]].
Line 26:		Line 26:
	#:See Also:		#:See Also:
	#:*[[How Object Arrays Work]]		#:*[[How Object Arrays Work]]
	# Infantry CANNOT repair vehicles: Any true infantry as listed in the [{{~~TTL~~\|InfantryTypes}}] list cannot repair a unit from the [{{~~TTL~~\|VehicleTypes}}] list. That is it cannot use a weapon that does negative damage against them, though it can do against infantry. Similarly a vehicle cannot heal infantry. You can generate a similar effect using a [[particle]] or by using negative {{~~TTL~~\|Verses}} values on a [[Warhead]] but the targeting behaviour is different to a true repair unit; please see [[Infantry Mechanic]] for further information.		# Infantry CANNOT repair vehicles: Any true infantry as listed in the [{{f\|InfantryTypes\|link}}] list cannot repair a unit from the [{{f\|VehicleTypes\|link}}] list. That is it cannot use a weapon that does negative damage against them, though it can do against infantry. Similarly a vehicle cannot heal infantry. You can generate a similar effect using a [[particle]] or by using negative {{f\|Verses\|link}} values on a [[Warhead]] but the targeting behaviour is different to a true repair unit; please see [[Infantry Mechanic]] for further information.
	# Number of [[Campaign\|Campaigns]] in RA2/YR: In RA2 there are the Allied, Soviet and Tutorial campaign, a total of 3, in YR there are the Allied and Soviet campaign, a total of 2. You can re-enable the tutorial campiagn in YR, so that you can add a third campaign however, but it involves modifying the executable using a resource hacker and creating some alternate art assets. This means that you cannot add any extra campaigns beyond three in these games. Strangely however TS/FS do not suffer from the same problem. They have a list box that lists all campaigns from [[battle.ini]].		# Number of [[Campaign\|Campaigns]] in RA2/YR: In RA2 there are the Allied, Soviet and Tutorial campaign, a total of 3, in YR there are the Allied and Soviet campaign, a total of 2. You can re-enable the tutorial campiagn in YR, so that you can add a third campaign however, but it involves modifying the executable using a resource hacker and creating some alternate art assets. This means that you cannot add any extra campaigns beyond three in these games. Strangely however TS/FS do not suffer from the same problem. They have a list box that lists all campaigns from [[battle.ini]].
	# [[Cursors]]: Cursor animations are held in the file [[mouse.shp]] (mouse.sha in YR) and certain frames are hardcoded to each action. Some actions however (particularly in RA2/YR where they are left over from TS) all share the same frame so even altering the [[shp]] file will not give unique cursors for these actions.		# [[Cursors]]: Cursor animations are held in the file [[mouse.shp]] (mouse.sha in YR) and certain frames are hardcoded to each action. Some actions however (particularly in RA2/YR where they are left over from TS) all share the same frame so even altering the [[shp]] file will not give unique cursors for these actions.

en>DCoder: per Wanted pages, WestWood => Westwood

2006-07-14T15:02:17Z

per Wanted pages, WestWood => Westwood

← Older revision		Revision as of 17:02, 14 July 2006
Line 4:		Line 4:
	=== What is hardcoding? ===		=== What is hardcoding? ===

	Hard code is code held in the binary executable. Basically it's the things that are out of your hands when it comes to C&C modding. Reasons why some stuff has its behaviour handled purely by the binary code are likely varied and are probably due to time constraints or a lack of nessesity for [[~~WestWood~~]] to actually ever vary some behaviour.		Hard code is code held in the binary executable. Basically it's the things that are out of your hands when it comes to C&C modding. Reasons why some stuff has its behaviour handled purely by the binary code are likely varied and are probably due to time constraints or a lack of nessesity for [[Westwood]] to actually ever vary some behaviour.

	=== Why do I need to know this stuff? ===		=== Why do I need to know this stuff? ===

en>DCoder: Restyled to correct missing links (and created a few new ones...)

2006-06-21T04:26:24Z

Restyled to correct missing links (and created a few new ones...)

← Older revision		Revision as of 06:26, 21 June 2006
Line 1:		Line 1:
	The term "hardcoded" describes functions that are coded directly into the [[Engine]] and cannot be changed/expanded by [[INI-editing]]. Examples for this are the number of unique [[MCV]]s in the game, the number of [[Houses]] and the multiplayer side colours menu.		The term "hardcoded" describes functions that are coded directly into the [[Engine]] and cannot be changed/expanded by [[INI-editing]]. Examples for this are the number of unique [[MCV]]s in the game, the number of [[Houses]] and the multiplayer side colours menu.

	== ~~Hard Coding~~ ==		== Hardcoding ==
	=== What is hardcoding? ===		=== What is hardcoding? ===

	Hard code is code held in the binary executable. Basically ~~its~~ the things that are out of your hands when it comes to C&C modding. Reasons why some stuff has its behaviour handled purely by the binary code are likely varied and are probably due to time constraints or a lack of nessesity for [WestWood] to actually ever vary some behaviour.		Hard code is code held in the binary executable. Basically it's the things that are out of your hands when it comes to C&C modding. Reasons why some stuff has its behaviour handled purely by the binary code are likely varied and are probably due to time constraints or a lack of nessesity for [[WestWood]] to actually ever vary some behaviour.

	=== Why do I need to know this stuff? ===		=== Why do I need to know this stuff? ===
Line 10:		Line 10:
	well there are 2 benefits from knowing the hardcoded suff:		well there are 2 benefits from knowing the hardcoded suff:

	~~1. saves~~ time and energy in your mind. ~~<br>~~		#Saves time and energy in your mind.
	~~2. stops~~ you irritating more experienced modders by asking about features that are impossible.		#Stops you irritating more experienced modders by asking about features that are impossible.

	== Features that are hard coded ==		== Features that are hard coded ==

	1. [[Superweapons]]: basically, superweapons can ONLY be replaced by altering the art assets and warheads that they use and the scope for modifying their behaviour (how they do their damage) is generally limited. All though it is possible to add more superweapons to the list, the [[Type~~=]]~~ value controls what behaviour that super weapon will use. This would allow you to make multiple versions of the same superweapon so you could charge and fire more than one at a time were it not for the fact that every superweapon needs a unique [[Action~~=]]~~ to give it a cursor and targeting. Via some clever ini editing, some members of the editing community have succeeded in creating superweapon like behaviour for some new weapons, but their targeting is handled differently from true superweapons.~~<br><br>~~		# [[Superweapons]]: basically, superweapons can ONLY be replaced by altering the art assets and warheads that they use and the scope for modifying their behaviour (how they do their damage) is generally limited. All though it is possible to add more superweapons to the list, the {{TTL\|Type}} value controls what behaviour that super weapon will use. This would allow you to make multiple versions of the same superweapon so you could charge and fire more than one at a time were it not for the fact that every superweapon needs a unique {{TTL\|Action}} to give it a cursor and targeting. Via some clever ini editing, some members of the editing community have succeeded in creating superweapon like behaviour for some new weapons, but their targeting is handled differently from true superweapons.
			# [[Sides]]: Depending on the C&C title, there are either two or three playable sides with two additional sides for neutral units and structures. For the playable sides they represent the main factions in the game and are often sub divided into countries (though internally they are called houses for the most part). In RA2/YR, the number of countries is also limited by code in the [[executable]] that identifies what art assets are assigned for loading screens. The playable sides are always 'GDI', 'Nod' and where applicable 'ThirdSide'.
	2. [[Sides]]: Depending on the C&C title, there are either two or three playable sides with two additional sides for neutral units and structures. For the playable sides they represent the main factions in the game and are often sub divided into countries (though internally they are called houses for the most part). In RA2/YR, the number of countries is also limited by code in the [[executable]] that identifies what art assets are assigned for loading screens. The playable sides are always 'GDI', 'Nod' and where applicable 'ThirdSide'. ~~<br><br>~~		# Multiplayer [[Colors\|Color]] Selection Menu: The colours that are displayed are fixed, even though you can change what they result in in [[rules.ini]].
			# Adding a new type of unit missile: if you are planning to add a new missile that will act as the '[[Unit:V3\|V3]] Rocket Launcher' or the '[[Unit:Dreadnought\|Dreadnought]]' or the '[[Unit:Boomer\|Boomer]] sub' missiles, you will fail. If you tried to add one, the rocket will launch until it reached a certain altitude and will do one of the 2 actions:
	3. Multiplayer [[Colors\|Color]] Selection Menu: The colours that are displayed are fixed, even though you can change what they result in in [[rules.ini]]~~<br><br>~~		#* will reverse its destinated direction and travel to nowhere.
			#* will reverse its destination and head straight back to the 'Launching vehicle'. Similar behaviour can be created however; please see [[Spawned Missiles]] for further information.
	4. Adding a new type of unit missile: if you are planning to add a new missile that will act as the '[[V3]] Rocket Launcher' or the '[[Dreadnought]]' or the '[[Boomer]] sub' missiles, you will fail. If you tried to add one, the rocket will launch until it reached a certain altitude and will do one of the 2 actions: a) will reverse its destinated direction and travel to nowhere. b) will reverse its destination and head straight back to the 'Launching vehicle'. Similar behaviour can be created however; please see [[Spawned Missiles]] for further information.		#The [[100 Units Bug]]. It is more of a bug than a hardcoded issue and is to do with the xxxtypes section, which lists of all the units in the game. The list looks like this:
	~~<br><br>~~		#: <tt>[InfantryTypes]<br>1=E1<br>2=ENGINEER<br>3=SENGINEER<br>4= ...etc.</tt>
			#:If any player buildable units are numbered to exceed 100 (after considering vacant numbers) then the list causes some kind of overflow error for the AI and it will constantly build the last unit on the list as though it were the only unit available to it.
	~~5. the xxxTypes~~ [[~~bug~~]]~~: xxx here stands for both of the word 'Vehicle' or 'Infantry'~~. It is more of a bug than a hardcoded issue and is to do with the xxxtypes section, which lists of all the units in the game. The list looks like this:		#:See Also:
	<~~blockquote~~>		#:*[[How Object Arrays Work]]
	[InfantryTypes]<br>		# Infantry CANNOT repair vehicles: Any true infantry as listed in the [{{TTL\|InfantryTypes}}] list cannot repair a unit from the [{{TTL\|VehicleTypes}}] list. That is it cannot use a weapon that does negative damage against them, though it can do against infantry. Similarly a vehicle cannot heal infantry. You can generate a similar effect using a [[particle]] or by using negative {{TTL\|Verses}} values on a [[Warhead]] but the targeting behaviour is different to a true repair unit; please see [[Infantry Mechanic]] for further information.
	1=E1 <br>		# Number of [[Campaign\|Campaigns]] in RA2/YR: In RA2 there are the Allied, Soviet and Tutorial campaign, a total of 3, in YR there are the Allied and Soviet campaign, a total of 2. You can re-enable the tutorial campiagn in YR, so that you can add a third campaign however, but it involves modifying the executable using a resource hacker and creating some alternate art assets. This means that you cannot add any extra campaigns beyond three in these games. Strangely however TS/FS do not suffer from the same problem. They have a list box that lists all campaigns from [[battle.ini]].
	2=ENGINEER <br>		# [[Cursors]]: Cursor animations are held in the file [[mouse.shp]] (mouse.sha in YR) and certain frames are hardcoded to each action. Some actions however (particularly in RA2/YR where they are left over from TS) all share the same frame so even altering the [[shp]] file will not give unique cursors for these actions.
	3=SENGINEER		# Disk Name for RA2/YR: The names for the data/install disks are hard coded in both the games and their installers. In RA2, they must either be named RA1 or RA2, yet strangely enough YR accepts RA3 and YR1 as valid disk names.
	4= ...etc. ~~<br>~~
	</~~blockquote~~>
	If any player buildable units are numbered to exceed 100 (after considering vacant numbers) then the list causes some kind of overflow error for the AI and it will constantly build the last unit on the list as though it were the only unit available to it.~~<br>~~
	*See ~~also~~: [[~~100 Units Bug~~]]~~<br><br>~~

	~~6. Infanty~~ CANNOT repair vehicles: Any true infantry as listed in the [[InfantryTypes]] list cannot repair a unit from the [~~[UnitTypes]~~] list. That is it cannot use a weapon that does negative damage against them, though it can do against infantry. Similarly a vehicle cannot heal infantry. You can generate a similar effect using a [[particle]] or by using negative [[Verses~~=]]~~ values on a [[Warhead]] but the targeting behaviour is different to a true repair unit; please see [[Infantry Mechanic]] for further information.~~<br><br>~~

	7. Number of [[Campaign\|Campaigns]] in RA2/YR: In RA2 there are the Allied, Soviet and Tutorial campaign, a total of 3, in YR there are the Allied and Soviet campaign, a total of 2. You can re-enable the tutorial campiagn in YR, so that you can add a third campaign however, but it involves modifying the executable using a resource hacker and creating some alternate art assets. This means that you cannot add any extra campaigns beyond three in these games. Strangely however TS/FS do not suffer from the same problem. They have a list box that lists all campaigns from [battle.ini]. ~~<br><br>~~

	8. [[Cursors]]: Cursor animations are held in the file [[mouse.shp]] (mouse.sha in YR) and certain frames are hardcoded to each action. Some actions however (particularly in RA2/YR where they are left over from TS) all share the same frame so even altering the [[shp]] file will not give unique cursors for these actions.

	9. Disk Name for RA2/YR: The names for the data/install disks are hard coded in both the games and their installers. In RA2, they must either be named RA1 or RA2, yet strangely enough YR accepts RA3 and YR1 as valid disk names.

	== Contributors ==		== Contributors ==

en>DCoder: s/Versus/Verses/

2006-06-21T03:56:27Z

s/Versus/Verses/

← Older revision		Revision as of 05:56, 21 June 2006
Line 35:		Line 35:
	*See also: [[100 Units Bug]]<br><br>		*See also: [[100 Units Bug]]<br><br>

	6. Infanty CANNOT repair vehicles: Any true infantry as listed in the [[InfantryTypes]] list cannot repair a unit from the [[UnitTypes]] list. That is it cannot use a weapon that does negative damage against them, though it can do against infantry. Similarly a vehicle cannot heal infantry. You can generate a similar effect using a [[particle]] or by using negative [[~~Versus~~=]] values on a [[Warhead]] but the targeting behaviour is different to a true repair unit; please see [[Infantry Mechanic]] for further information.<br><br>		6. Infanty CANNOT repair vehicles: Any true infantry as listed in the [[InfantryTypes]] list cannot repair a unit from the [[UnitTypes]] list. That is it cannot use a weapon that does negative damage against them, though it can do against infantry. Similarly a vehicle cannot heal infantry. You can generate a similar effect using a [[particle]] or by using negative [[Verses=]] values on a [[Warhead]] but the targeting behaviour is different to a true repair unit; please see [[Infantry Mechanic]] for further information.<br><br>

	7. Number of [[Campaign\|Campaigns]] in RA2/YR: In RA2 there are the Allied, Soviet and Tutorial campaign, a total of 3, in YR there are the Allied and Soviet campaign, a total of 2. You can re-enable the tutorial campiagn in YR, so that you can add a third campaign however, but it involves modifying the executable using a resource hacker and creating some alternate art assets. This means that you cannot add any extra campaigns beyond three in these games. Strangely however TS/FS do not suffer from the same problem. They have a list box that lists all campaigns from [battle.ini]. <br><br>		7. Number of [[Campaign\|Campaigns]] in RA2/YR: In RA2 there are the Allied, Soviet and Tutorial campaign, a total of 3, in YR there are the Allied and Soviet campaign, a total of 2. You can re-enable the tutorial campiagn in YR, so that you can add a third campaign however, but it involves modifying the executable using a resource hacker and creating some alternate art assets. This means that you cannot add any extra campaigns beyond three in these games. Strangely however TS/FS do not suffer from the same problem. They have a list box that lists all campaigns from [battle.ini]. <br><br>

66.218.35.101: /* Features that are hard coded */

2005-09-14T06:00:54Z

Features that are hard coded

← Older revision		Revision as of 08:00, 14 September 2005
Line 40:		Line 40:

	8. [[Cursors]]: Cursor animations are held in the file [[mouse.shp]] (mouse.sha in YR) and certain frames are hardcoded to each action. Some actions however (particularly in RA2/YR where they are left over from TS) all share the same frame so even altering the [[shp]] file will not give unique cursors for these actions.		8. [[Cursors]]: Cursor animations are held in the file [[mouse.shp]] (mouse.sha in YR) and certain frames are hardcoded to each action. Some actions however (particularly in RA2/YR where they are left over from TS) all share the same frame so even altering the [[shp]] file will not give unique cursors for these actions.

			9. Disk Name for RA2/YR: The names for the data/install disks are hard coded in both the games and their installers. In RA2, they must either be named RA1 or RA2, yet strangely enough YR accepts RA3 and YR1 as valid disk names.

	== Contributors ==		== Contributors ==

66.61.45.80 at 02:31, 14 September 2005

2005-09-14T02:31:58Z

← Older revision		Revision as of 04:31, 14 September 2005
Line 10:		Line 10:
	well there are 2 benefits from knowing the hardcoded suff:		well there are 2 benefits from knowing the hardcoded suff:

	1. saves time an energy in your mind. <br>		1. saves time and energy in your mind. <br>
	2. stops you irritating more experienced modders by asking about features that are impossible.		2. stops you irritating more experienced modders by asking about features that are impossible.

en>Renegade: Added to category

2005-04-17T23:46:26Z

Added to category

← Older revision		Revision as of 01:46, 18 April 2005
Line 46:		Line 46:
	* Tratos for bringing up some ideas		* Tratos for bringing up some ideas
	* Kravvitz for some editing, bringing up and explaining some stuff.		* Kravvitz for some editing, bringing up and explaining some stuff.

			[[Category:General_Editing_Information]]