Infantry Linking - Revision history

MarkJFox: 11 revisions imported

2025-03-31T19:22:37Z

11 revisions imported

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

en>DeathFish: Point the original link to the correct page

2022-05-21T14:05:02Z

Point the original link to the correct page

← Older revision		Revision as of 16:05, 21 May 2022
Line 96:		Line 96:
	#Make a clone of {{tt\|[E1]}} and give it an ID that is 99% likely to be unique. Some sort of alphanumeric serial number that is truly random would be good. (Ideally, you want all of your custom units to have an ID that nobody else could possibly use in a map.)<br>All elements of a linked-infantry group should have totally unique IDs.		#Make a clone of {{tt\|[E1]}} and give it an ID that is 99% likely to be unique. Some sort of alphanumeric serial number that is truly random would be good. (Ideally, you want all of your custom units to have an ID that nobody else could possibly use in a map.)<br>All elements of a linked-infantry group should have totally unique IDs.
	#The original GI ({{tt\|[E1]}}) should be made unbuildable by human players. The only way I know of doing this is to give it a Prerequisite of a building that could never possibly exist on a custom map. This dummy building should be properly defined in your code and have a unique ID.<br>AI players ignore prerequisites and so will still be able to build the original GI.		#The original GI ({{tt\|[E1]}}) should be made unbuildable by human players. The only way I know of doing this is to give it a Prerequisite of a building that could never possibly exist on a custom map. This dummy building should be properly defined in your code and have a unique ID.<br>AI players ignore prerequisites and so will still be able to build the original GI.
	#Set {{f\|AlliedCrew\|\|link}} to your GI clone.<br>I don't think the flags {{f\|Pilot\|\|link}} and {{f\|~~PParatrooper~~\|\|link}} are even parsed, but if they are then they might need to be changed.		#Set {{f\|AlliedCrew\|\|link}} to your GI clone.<br>I don't think the flags {{f\|Pilot\|\|link}} and {{f\|Paratrooper\|\|link}} are even parsed, but if they are then they might need to be changed.
	#Set {{f\|AllowedToStartInMultiplayer\|no\|link}} on the original GI (and 'yes' on your GI clone).		#Set {{f\|AllowedToStartInMultiplayer\|no\|link}} on the original GI (and 'yes' on your GI clone).

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

2009-11-27T08:09:30Z

Replacing Template:TTL with Template:F.

← Older revision		Revision as of 10:09, 27 November 2009
Line 6:		Line 6:

	==Background==		==Background==
	The secret lies in the deploy/undeploy modifications done for the [[Unit:Slave Miner\|Slave Miner]] in {{yr}}: Even before YR, one could have a [[VehicleType]] deploy into a [[BuildingType]] by putting {{~~TTL~~\|DeploysInto}} on it, and a BuildingType into a VehicleType by using {{~~TTL~~\|UndeploysInto}}. This was mainly used on the [[Building:Construction Yard\|Construction Yard]], and on the [[Unit:Artillery\|Nod Artillery]] in {{ts}}.		The secret lies in the deploy/undeploy modifications done for the [[Unit:Slave Miner\|Slave Miner]] in {{yr}}: Even before YR, one could have a [[VehicleType]] deploy into a [[BuildingType]] by putting {{f\|DeploysInto\|link}} on it, and a BuildingType into a VehicleType by using {{f\|UndeploysInto\|link}}. This was mainly used on the [[Building:Construction Yard\|Construction Yard]], and on the [[Unit:Artillery\|Nod Artillery]] in {{ts}}.

	Now, for some reason only known to Electronic Arts (possibly related to [[Building:Refinery\|Refinery]] code, since they are buildings), the coders of YR decided to use the same construct for the Slave Miner. The problem with this is obvious: Code-wise, the vehicle Slave Miner now turns into a building Slave Miner on deploy - but story-wise, that doesn't happen. It's just a vehicle.		Now, for some reason only known to Electronic Arts (possibly related to [[Building:Refinery\|Refinery]] code, since they are buildings), the coders of YR decided to use the same construct for the Slave Miner. The problem with this is obvious: Code-wise, the vehicle Slave Miner now turns into a building Slave Miner on deploy - but story-wise, that doesn't happen. It's just a vehicle.
Line 96:		Line 96:
	#Make a clone of {{tt\|[E1]}} and give it an ID that is 99% likely to be unique. Some sort of alphanumeric serial number that is truly random would be good. (Ideally, you want all of your custom units to have an ID that nobody else could possibly use in a map.)<br>All elements of a linked-infantry group should have totally unique IDs.		#Make a clone of {{tt\|[E1]}} and give it an ID that is 99% likely to be unique. Some sort of alphanumeric serial number that is truly random would be good. (Ideally, you want all of your custom units to have an ID that nobody else could possibly use in a map.)<br>All elements of a linked-infantry group should have totally unique IDs.
	#The original GI ({{tt\|[E1]}}) should be made unbuildable by human players. The only way I know of doing this is to give it a Prerequisite of a building that could never possibly exist on a custom map. This dummy building should be properly defined in your code and have a unique ID.<br>AI players ignore prerequisites and so will still be able to build the original GI.		#The original GI ({{tt\|[E1]}}) should be made unbuildable by human players. The only way I know of doing this is to give it a Prerequisite of a building that could never possibly exist on a custom map. This dummy building should be properly defined in your code and have a unique ID.<br>AI players ignore prerequisites and so will still be able to build the original GI.
	#Set {{~~TTL~~\|AlliedCrew\|}} to your GI clone.<br>I don't think the flags {{~~TTL~~\|Pilot\|}} and {{~~TTL~~\|PParatrooper\|}} are even parsed, but if they are then they might need to be changed.		#Set {{f\|AlliedCrew\|\|link}} to your GI clone.<br>I don't think the flags {{f\|Pilot\|\|link}} and {{f\|PParatrooper\|\|link}} are even parsed, but if they are then they might need to be changed.
	#Set {{~~TTL~~\|AllowedToStartInMultiplayer\|no}} on the original GI (and 'yes' on your GI clone).		#Set {{f\|AllowedToStartInMultiplayer\|no\|link}} on the original GI (and 'yes' on your GI clone).

	Obviously the AI scripts can be left alone as the AI is unaffected.		Obviously the AI scripts can be left alone as the AI is unaffected.

en>Marshall: fixed link to redirect

2008-05-13T18:21:23Z

fixed link to redirect

← Older revision		Revision as of 20:21, 13 May 2008
Line 45:		Line 45:
	UndeploysInto=SENGINEER		UndeploysInto=SENGINEER

	The code above is the (already mentioned) most common application of this technique, ~~taken straight from (~~older versions of) [[~~YR 1.002 UMP\|the~~ UMP]]: It links together all three engineer types, and all four dog types. Were any of them selected ingame and you pressed "Select all of Type", all Engineers or all Dogs would be selected, no matter if they're originally Allied, Soviet, or Yuri.		The code above is the (already mentioned) most common application of this technique, as used in [older versions of] the [[UMP]]: It links together all three engineer types, and all four dog types. Were any of them selected ingame and you pressed "Select all of Type", all Engineers or all Dogs would be selected, no matter if they're originally Allied, Soviet, or Yuri.

	This example also demonstrates how to link more than two InfantryTypes: "Circle deploying". Look at the engineers - each of them deploys into one other, and undeploys into the third one. Mind how problems might arise with the dogs - if {{tt\|ADOG}} is selected and "Select all of Type" is pressed - does {{tt\|YDOG}} get selected? [[#Problems and Limitations\|{{arr\|d}}]]		This example also demonstrates how to link more than two InfantryTypes: "Circle deploying". Look at the engineers - each of them deploys into one other, and undeploys into the third one. Mind how problems might arise with the dogs - if {{tt\|ADOG}} is selected and "Select all of Type" is pressed - does {{tt\|YDOG}} get selected? [[#Problems and Limitations\|{{arr\|d}}]]

en>Gordon-creAtive: rw

2008-03-30T12:43:07Z

← Older revision		Revision as of 14:43, 30 March 2008
Line 121:		Line 121:

	[[Category:MP Mode Override Bugs]] <!-- take this out if a page over the specific bug gets created -->		[[Category:MP Mode Override Bugs]] <!-- take this out if a page over the specific bug gets created -->
	[[Category:Tutorials]]		[[Category:TS Tutorials]]
			[[Category:RA2/YR Tutorials]]
	[[Category:General Editing Information]]		[[Category:General Editing Information]]

en>Renegade: Reversion: It's a rhetoric question, made clear by the link to the problems section. And the additional sentence repeats almost exactly what was said two paragraphs higher.

2006-12-27T04:55:47Z

Reversion: It's a rhetoric question, made clear by the link to the problems section. And the additional sentence repeats almost exactly what was said two paragraphs higher.

← Older revision		Revision as of 06:55, 27 December 2006
Line 47:		Line 47:
	The code above is the (already mentioned) most common application of this technique, taken straight from (older versions of) [[YR 1.002 UMP\|the UMP]]: It links together all three engineer types, and all four dog types. Were any of them selected ingame and you pressed "Select all of Type", all Engineers or all Dogs would be selected, no matter if they're originally Allied, Soviet, or Yuri.		The code above is the (already mentioned) most common application of this technique, taken straight from (older versions of) [[YR 1.002 UMP\|the UMP]]: It links together all three engineer types, and all four dog types. Were any of them selected ingame and you pressed "Select all of Type", all Engineers or all Dogs would be selected, no matter if they're originally Allied, Soviet, or Yuri.

	This example also demonstrates how to link more than two InfantryTypes: "Circle deploying". Look at the engineers - each of them deploys into one other, and undeploys into the third one. Mind how problems might arise with the dogs - if {{tt\|ADOG}} is selected and "Select all of Type" is pressed - {{tt\|YDOG}} ~~does ''NOT''~~ get selected. [[#Problems and Limitations\|{{arr\|d}}]]		This example also demonstrates how to link more than two InfantryTypes: "Circle deploying". Look at the engineers - each of them deploys into one other, and undeploys into the third one. Mind how problems might arise with the dogs - if {{tt\|ADOG}} is selected and "Select all of Type" is pressed - does {{tt\|YDOG}} get selected? [[#Problems and Limitations\|{{arr\|d}}]]

	Also note that the hack works one-directional: {{tt\|ENGINEER}} is treated as the same type as {{tt\|SENGINEER}} due to {{tt\|1=DeploysInto=SENGINEER}}; {{tt\|SENGINEER}} is treated as the same type as {{tt\|ENGINEER}} due to {{tt\|1=DeploysInto=ENGINEER}}. Would either side be missing the link, then it would only work from the linking side, not from the not-linking, e.g. if {{tt\|SENGINEER}} was missing the hack, and {{tt\|ENGINEER}} was selected, then you could select both {{tt\|ENGINEER}} and {{tt\|SENGINEER}} through "Select all of Type" - but if SENGINEER was selected, "Select all of Type" would only select other {{tt\|SENGINEER}}s. ''All participating units must be linked to all other participating units for this to work.''		Also note that the hack works one-directional: {{tt\|ENGINEER}} is treated as the same type as {{tt\|SENGINEER}} due to {{tt\|1=DeploysInto=SENGINEER}}; {{tt\|SENGINEER}} is treated as the same type as {{tt\|ENGINEER}} due to {{tt\|1=DeploysInto=ENGINEER}}. Would either side be missing the link, then it would only work from the linking side, not from the not-linking, e.g. if {{tt\|SENGINEER}} was missing the hack, and {{tt\|ENGINEER}} was selected, then you could select both {{tt\|ENGINEER}} and {{tt\|SENGINEER}} through "Select all of Type" - but if SENGINEER was selected, "Select all of Type" would only select other {{tt\|SENGINEER}}s. ''All participating units must be linked to all other participating units for this to work.''
	~~"Circle linking" allows you to link up to three infantry units together.~~

	==Useful Applications==		==Useful Applications==

86.142.44.30: /* Usage */

2006-12-26T23:41:04Z

Usage

← Older revision		Revision as of 01:41, 27 December 2006
Line 47:		Line 47:
	The code above is the (already mentioned) most common application of this technique, taken straight from (older versions of) [[YR 1.002 UMP\|the UMP]]: It links together all three engineer types, and all four dog types. Were any of them selected ingame and you pressed "Select all of Type", all Engineers or all Dogs would be selected, no matter if they're originally Allied, Soviet, or Yuri.		The code above is the (already mentioned) most common application of this technique, taken straight from (older versions of) [[YR 1.002 UMP\|the UMP]]: It links together all three engineer types, and all four dog types. Were any of them selected ingame and you pressed "Select all of Type", all Engineers or all Dogs would be selected, no matter if they're originally Allied, Soviet, or Yuri.

	This example also demonstrates how to link more than two InfantryTypes: "Circle deploying". Look at the engineers - each of them deploys into one other, and undeploys into the third one. Mind how problems might arise with the dogs - if {{tt\|ADOG}} is selected and "Select all of Type" is pressed - ~~does~~ {{tt\|YDOG}} get selected? [[#Problems and Limitations\|{{arr\|d}}]]		This example also demonstrates how to link more than two InfantryTypes: "Circle deploying". Look at the engineers - each of them deploys into one other, and undeploys into the third one. Mind how problems might arise with the dogs - if {{tt\|ADOG}} is selected and "Select all of Type" is pressed - {{tt\|YDOG}} does ''NOT'' get selected. [[#Problems and Limitations\|{{arr\|d}}]]

	Also note that the hack works one-directional: {{tt\|ENGINEER}} is treated as the same type as {{tt\|SENGINEER}} due to {{tt\|1=DeploysInto=SENGINEER}}; {{tt\|SENGINEER}} is treated as the same type as {{tt\|ENGINEER}} due to {{tt\|1=DeploysInto=ENGINEER}}. Would either side be missing the link, then it would only work from the linking side, not from the not-linking, e.g. if {{tt\|SENGINEER}} was missing the hack, and {{tt\|ENGINEER}} was selected, then you could select both {{tt\|ENGINEER}} and {{tt\|SENGINEER}} through "Select all of Type" - but if SENGINEER was selected, "Select all of Type" would only select other {{tt\|SENGINEER}}s. ''All participating units must be linked to all other participating units for this to work.''		Also note that the hack works one-directional: {{tt\|ENGINEER}} is treated as the same type as {{tt\|SENGINEER}} due to {{tt\|1=DeploysInto=SENGINEER}}; {{tt\|SENGINEER}} is treated as the same type as {{tt\|ENGINEER}} due to {{tt\|1=DeploysInto=ENGINEER}}. Would either side be missing the link, then it would only work from the linking side, not from the not-linking, e.g. if {{tt\|SENGINEER}} was missing the hack, and {{tt\|ENGINEER}} was selected, then you could select both {{tt\|ENGINEER}} and {{tt\|SENGINEER}} through "Select all of Type" - but if SENGINEER was selected, "Select all of Type" would only select other {{tt\|SENGINEER}}s. ''All participating units must be linked to all other participating units for this to work.''
			"Circle linking" allows you to link up to three infantry units together.

	==Useful Applications==		==Useful Applications==

en>Renegade: first draft of an (almost) original version..please proofread, backcheck and correct - especially the background part; am very not sure whether this wasn't possible before, working on conclusions here

2006-10-01T20:49:14Z

first draft of an (almost) original version..please proofread, backcheck and correct - especially the background part; am very not sure whether this wasn't possible before, working on conclusions here

Show changes

en>Vinifera7: category

2006-10-01T19:57:19Z

213.122.121.221 at 09:54, 1 October 2006

2006-10-01T09:54:39Z

← Older revision		Revision as of 11:54, 1 October 2006
Line 1:		Line 1:
	This is a copy of the Infantry Linking document by Marshall included with the [http://marshall.cannis.net/ump YR 1.002 Mini-Path (UMP) Developer's Pack]		This is a copy of the Infantry Linking document by Marshall included with the [http://marshall.cannis.net/ump YR 1.002 Mini-Path (UMP) Developer's Pack]

	~~== Infantry Linking using DeploysInto/UndeploysInto (Engineers, Attack Dogs, etc)... and why you shouldn't do it ==~~

	Infantry Linking is generally discouraged because it requires complex work-arounds for the problems it causes and also invites Internal Errors.		Infantry Linking is generally discouraged because it requires complex work-arounds for the problems it causes and also invites Internal Errors.

← Older revision		Revision as of 16:05, 21 May 2022
Line 96:		Line 96:
	#Make a clone of {{tt\|[E1]}} and give it an ID that is 99% likely to be unique. Some sort of alphanumeric serial number that is truly random would be good. (Ideally, you want all of your custom units to have an ID that nobody else could possibly use in a map.)<br>All elements of a linked-infantry group should have totally unique IDs.		#Make a clone of {{tt\|[E1]}} and give it an ID that is 99% likely to be unique. Some sort of alphanumeric serial number that is truly random would be good. (Ideally, you want all of your custom units to have an ID that nobody else could possibly use in a map.)<br>All elements of a linked-infantry group should have totally unique IDs.
	#The original GI ({{tt\|[E1]}}) should be made unbuildable by human players. The only way I know of doing this is to give it a Prerequisite of a building that could never possibly exist on a custom map. This dummy building should be properly defined in your code and have a unique ID.<br>AI players ignore prerequisites and so will still be able to build the original GI.		#The original GI ({{tt\|[E1]}}) should be made unbuildable by human players. The only way I know of doing this is to give it a Prerequisite of a building that could never possibly exist on a custom map. This dummy building should be properly defined in your code and have a unique ID.<br>AI players ignore prerequisites and so will still be able to build the original GI.
	#Set {{f\|AlliedCrew\|\|link}} to your GI clone.<br>I don't think the flags {{f\|Pilot\|\|link}} and {{f\|~~PParatrooper~~\|\|link}} are even parsed, but if they are then they might need to be changed.		#Set {{f\|AlliedCrew\|\|link}} to your GI clone.<br>I don't think the flags {{f\|Pilot\|\|link}} and {{f\|Paratrooper\|\|link}} are even parsed, but if they are then they might need to be changed.
	#Set {{f\|AllowedToStartInMultiplayer\|no\|link}} on the original GI (and 'yes' on your GI clone).		#Set {{f\|AllowedToStartInMultiplayer\|no\|link}} on the original GI (and 'yes' on your GI clone).

← Older revision		Revision as of 10:09, 27 November 2009
Line 6:		Line 6:

	==Background==		==Background==
	The secret lies in the deploy/undeploy modifications done for the [[Unit:Slave Miner\|Slave Miner]] in {{yr}}: Even before YR, one could have a [[VehicleType]] deploy into a [[BuildingType]] by putting {{~~TTL~~\|DeploysInto}} on it, and a BuildingType into a VehicleType by using {{~~TTL~~\|UndeploysInto}}. This was mainly used on the [[Building:Construction Yard\|Construction Yard]], and on the [[Unit:Artillery\|Nod Artillery]] in {{ts}}.		The secret lies in the deploy/undeploy modifications done for the [[Unit:Slave Miner\|Slave Miner]] in {{yr}}: Even before YR, one could have a [[VehicleType]] deploy into a [[BuildingType]] by putting {{f\|DeploysInto\|link}} on it, and a BuildingType into a VehicleType by using {{f\|UndeploysInto\|link}}. This was mainly used on the [[Building:Construction Yard\|Construction Yard]], and on the [[Unit:Artillery\|Nod Artillery]] in {{ts}}.

	Now, for some reason only known to Electronic Arts (possibly related to [[Building:Refinery\|Refinery]] code, since they are buildings), the coders of YR decided to use the same construct for the Slave Miner. The problem with this is obvious: Code-wise, the vehicle Slave Miner now turns into a building Slave Miner on deploy - but story-wise, that doesn't happen. It's just a vehicle.		Now, for some reason only known to Electronic Arts (possibly related to [[Building:Refinery\|Refinery]] code, since they are buildings), the coders of YR decided to use the same construct for the Slave Miner. The problem with this is obvious: Code-wise, the vehicle Slave Miner now turns into a building Slave Miner on deploy - but story-wise, that doesn't happen. It's just a vehicle.
Line 96:		Line 96:
	#Make a clone of {{tt\|[E1]}} and give it an ID that is 99% likely to be unique. Some sort of alphanumeric serial number that is truly random would be good. (Ideally, you want all of your custom units to have an ID that nobody else could possibly use in a map.)<br>All elements of a linked-infantry group should have totally unique IDs.		#Make a clone of {{tt\|[E1]}} and give it an ID that is 99% likely to be unique. Some sort of alphanumeric serial number that is truly random would be good. (Ideally, you want all of your custom units to have an ID that nobody else could possibly use in a map.)<br>All elements of a linked-infantry group should have totally unique IDs.
	#The original GI ({{tt\|[E1]}}) should be made unbuildable by human players. The only way I know of doing this is to give it a Prerequisite of a building that could never possibly exist on a custom map. This dummy building should be properly defined in your code and have a unique ID.<br>AI players ignore prerequisites and so will still be able to build the original GI.		#The original GI ({{tt\|[E1]}}) should be made unbuildable by human players. The only way I know of doing this is to give it a Prerequisite of a building that could never possibly exist on a custom map. This dummy building should be properly defined in your code and have a unique ID.<br>AI players ignore prerequisites and so will still be able to build the original GI.
	#Set {{~~TTL~~\|AlliedCrew\|}} to your GI clone.<br>I don't think the flags {{~~TTL~~\|Pilot\|}} and {{~~TTL~~\|PParatrooper\|}} are even parsed, but if they are then they might need to be changed.		#Set {{f\|AlliedCrew\|\|link}} to your GI clone.<br>I don't think the flags {{f\|Pilot\|\|link}} and {{f\|PParatrooper\|\|link}} are even parsed, but if they are then they might need to be changed.
	#Set {{~~TTL~~\|AllowedToStartInMultiplayer\|no}} on the original GI (and 'yes' on your GI clone).		#Set {{f\|AllowedToStartInMultiplayer\|no\|link}} on the original GI (and 'yes' on your GI clone).

	Obviously the AI scripts can be left alone as the AI is unaffected.		Obviously the AI scripts can be left alone as the AI is unaffected.

← Older revision		Revision as of 21:57, 1 October 2006
Line 103:		Line 103:

	You should not attempt to make use of infantry linking unless you clearly understand every facet of this document.		You should not attempt to make use of infantry linking unless you clearly understand every facet of this document.

			[[Category:General_Editing_Information]]