MakeInfantry - Revision history

Rain-Islet: [bot] Batch update {{Bugs}} templates.

2025-07-02T15:36:25Z

[bot] Batch update {{Bugs}} templates.

← Older revision		Revision as of 17:36, 2 July 2025
Line 54:		Line 54:
	But that really is it though, the other [[InfDeath\|InfDeaths]] won't work for this.		But that really is it though, the other [[InfDeath\|InfDeaths]] won't work for this.

	{{Bugs}}		=={{Bugs}}==
	*Do not use an area-effect mutation weapon if [[paradrops\|paratroopers]] are not immune to it - an [[Internal Error]] will occur if a falling paratrooper is killed by an area-effect mutation weapon (point based mutation deaths seem to be okay and just result in the paratrooper exploding, and the Genetic Mutator super weapon appears to have been designed to prevent it killing such infantry).		*Do not use an area-effect mutation weapon if [[paradrops\|paratroopers]] are not immune to it - an [[Internal Error]] will occur if a falling paratrooper is killed by an area-effect mutation weapon (point based mutation deaths seem to be okay and just result in the paratrooper exploding, and the Genetic Mutator super weapon appears to have been designed to prevent it killing such infantry).
	*The animation associated with {{f\|InfDeath\|link}} 9 '''must''' have a {{f\|MakeInfantry\|link}} flag and it must be set to a valid {{f\|AnimToInfantry\|link}} list index. If it doesn't, then the animation will not play at all. <small>[Actually, it doesn't have to have the {{f\|MakeInfantry\|link}} flag ''if'' it has instead a {{f\|Next\|link}} flag so that the last animation of a sequence of animations invoked by InfDeath 9 ''does'' have a {{f\|MakeInfantry\|link}} flag.]</small>		*The animation associated with {{f\|InfDeath\|link}} 9 '''must''' have a {{f\|MakeInfantry\|link}} flag and it must be set to a valid {{f\|AnimToInfantry\|link}} list index. If it doesn't, then the animation will not play at all. <small>[Actually, it doesn't have to have the {{f\|MakeInfantry\|link}} flag ''if'' it has instead a {{f\|Next\|link}} flag so that the last animation of a sequence of animations invoked by InfDeath 9 ''does'' have a {{f\|MakeInfantry\|link}} flag.]</small>

MarkJFox: 13 revisions imported

2025-03-31T19:56:55Z

13 revisions imported

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

en>Testid123 at 03:05, 1 February 2025

2025-02-01T03:05:48Z

← Older revision		Revision as of 05:05, 1 February 2025
Line 62:		Line 62:
	<div><ul>		<div><ul>
	<li style="display: inline-block;">[[File:IE=404E0000(YR).gif\|frame\|IE=404E0000(YR)]]</li>		<li style="display: inline-block;">[[File:IE=404E0000(YR).gif\|frame\|IE=404E0000(YR)]]</li>
			<li style="display: inline-block;">[[File:IE=404E0000(YR)--Problem solved!--.gif\|frame\|IE=404E0000(YR)--Problem solved!--]]</li>
	</ul></div><br>		</ul></div><br>

en>Testid123 at 02:55, 1 February 2025

2025-02-01T02:55:24Z

← Older revision		Revision as of 04:55, 1 February 2025
Line 58:		Line 58:
	*The animation associated with {{f\|InfDeath\|link}} 9 '''must''' have a {{f\|MakeInfantry\|link}} flag and it must be set to a valid {{f\|AnimToInfantry\|link}} list index. If it doesn't, then the animation will not play at all. <small>[Actually, it doesn't have to have the {{f\|MakeInfantry\|link}} flag ''if'' it has instead a {{f\|Next\|link}} flag so that the last animation of a sequence of animations invoked by InfDeath 9 ''does'' have a {{f\|MakeInfantry\|link}} flag.]</small>		*The animation associated with {{f\|InfDeath\|link}} 9 '''must''' have a {{f\|MakeInfantry\|link}} flag and it must be set to a valid {{f\|AnimToInfantry\|link}} list index. If it doesn't, then the animation will not play at all. <small>[Actually, it doesn't have to have the {{f\|MakeInfantry\|link}} flag ''if'' it has instead a {{f\|Next\|link}} flag so that the last animation of a sequence of animations invoked by InfDeath 9 ''does'' have a {{f\|MakeInfantry\|link}} flag.]</small>
	*When an animation that has this flag set is playing and the cell is obstructed so the infantry cannot be spawned (e.g., a vehicle is parked in that cell), the game will stubbornly keep trying to place it, and cause increasing lag, as well as an ever-growing memory leak, for the remainder of the game session. The only way to prevent accumulating lag is to make sure the cell in question is clear. Note that this also happens when the cell is occupied by invincible objects such as impassable terrain tiles (cliffs, water) or [[TerrainTypes]] such as ore mines. In this case, there is no fix for the ever growing lag and memory leakage, short of aborting the current game session. <!-- It's 5 AM, do you know where your garbage collector is? blargh. --><br>		*When an animation that has this flag set is playing and the cell is obstructed so the infantry cannot be spawned (e.g., a vehicle is parked in that cell), the game will stubbornly keep trying to place it, and cause increasing lag, as well as an ever-growing memory leak, for the remainder of the game session. The only way to prevent accumulating lag is to make sure the cell in question is clear. Note that this also happens when the cell is occupied by invincible objects such as impassable terrain tiles (cliffs, water) or [[TerrainTypes]] such as ore mines. In this case, there is no fix for the ever growing lag and memory leakage, short of aborting the current game session. <!-- It's 5 AM, do you know where your garbage collector is? blargh. --><br>
	*In special cases, the game will give {{f\|IE\|404E0000\|link}}		*In special cases, the game will give {{f\|IE\|404E0000\|link}}(Now I can fix this problem [[Testid123]])
	which was caused by [[InfantryTypes]] spawning under the destroyed building. (The building has some kind of trigger or action.)<br>		which was caused by [[InfantryTypes]] spawning under the destroyed building. (The building has some kind of trigger or action.)<br>
	<div><ul>		<div><ul>

en>Testid123 at 02:40, 1 February 2025

2025-02-01T02:40:46Z

← Older revision		Revision as of 04:40, 1 February 2025
Line 9:		Line 9:
	\|rp=yes		\|rp=yes
	}}		}}

	Specifies the list index of {{tt\|rulesmd.ini}}{{arr\|r}}[{{f\|General\|link}}]{{arr\|r}}{{f\|AnimToInfantry\|link}} to refer to to determine which [[InfantryType]] should be created when this [[animation]] finishes.		Specifies the list index of {{tt\|rulesmd.ini}}{{arr\|r}}[{{f\|General\|link}}]{{arr\|r}}{{f\|AnimToInfantry\|link}} to refer to to determine which [[InfantryType]] should be created when this [[animation]] finishes.

Line 58:		Line 57:
	*Do not use an area-effect mutation weapon if [[paradrops\|paratroopers]] are not immune to it - an [[Internal Error]] will occur if a falling paratrooper is killed by an area-effect mutation weapon (point based mutation deaths seem to be okay and just result in the paratrooper exploding, and the Genetic Mutator super weapon appears to have been designed to prevent it killing such infantry).		*Do not use an area-effect mutation weapon if [[paradrops\|paratroopers]] are not immune to it - an [[Internal Error]] will occur if a falling paratrooper is killed by an area-effect mutation weapon (point based mutation deaths seem to be okay and just result in the paratrooper exploding, and the Genetic Mutator super weapon appears to have been designed to prevent it killing such infantry).
	*The animation associated with {{f\|InfDeath\|link}} 9 '''must''' have a {{f\|MakeInfantry\|link}} flag and it must be set to a valid {{f\|AnimToInfantry\|link}} list index. If it doesn't, then the animation will not play at all. <small>[Actually, it doesn't have to have the {{f\|MakeInfantry\|link}} flag ''if'' it has instead a {{f\|Next\|link}} flag so that the last animation of a sequence of animations invoked by InfDeath 9 ''does'' have a {{f\|MakeInfantry\|link}} flag.]</small>		*The animation associated with {{f\|InfDeath\|link}} 9 '''must''' have a {{f\|MakeInfantry\|link}} flag and it must be set to a valid {{f\|AnimToInfantry\|link}} list index. If it doesn't, then the animation will not play at all. <small>[Actually, it doesn't have to have the {{f\|MakeInfantry\|link}} flag ''if'' it has instead a {{f\|Next\|link}} flag so that the last animation of a sequence of animations invoked by InfDeath 9 ''does'' have a {{f\|MakeInfantry\|link}} flag.]</small>
	*When an animation that has this flag set is playing and the cell is obstructed so the infantry cannot be spawned (e.g., a vehicle is parked in that cell), the game will stubbornly keep trying to place it, and cause increasing lag, as well as an ever-growing memory leak, for the remainder of the game session. The only way to prevent accumulating lag is to make sure the cell in question is clear. Note that this also happens when the cell is occupied by invincible objects such as impassable terrain tiles (cliffs, water) or [[TerrainTypes]] such as ore mines. In this case, there is no fix for the ever growing lag and memory leakage, short of aborting the current game session. <!-- It's 5 AM, do you know where your garbage collector is? blargh. -->		*When an animation that has this flag set is playing and the cell is obstructed so the infantry cannot be spawned (e.g., a vehicle is parked in that cell), the game will stubbornly keep trying to place it, and cause increasing lag, as well as an ever-growing memory leak, for the remainder of the game session. The only way to prevent accumulating lag is to make sure the cell in question is clear. Note that this also happens when the cell is occupied by invincible objects such as impassable terrain tiles (cliffs, water) or [[TerrainTypes]] such as ore mines. In this case, there is no fix for the ever growing lag and memory leakage, short of aborting the current game session. <!-- It's 5 AM, do you know where your garbage collector is? blargh. --><br>
			*In special cases, the game will give {{f\|IE\|404E0000\|link}}
			which was caused by [[InfantryTypes]] spawning under the destroyed building. (The building has some kind of trigger or action.)<br>
			<div><ul>
			<li style="display: inline-block;">[[File:IE=404E0000(YR).gif\|frame\|IE=404E0000(YR)]]</li>
			</ul></div><br>

	==See also==		==See also==

en>Testid123 at 09:26, 17 August 2024

2024-08-17T09:26:02Z

← Older revision		Revision as of 11:26, 17 August 2024
Line 64:		Line 64:
	*[[InfDeath]]		*[[InfDeath]]
	*[[DeathAnims]]		*[[DeathAnims]]
			*[[MakeInfantryOwner]]
	[[Category:RA2/YR Tutorials]]		[[Category:RA2/YR Tutorials]]

en>DeathFish: /* See also */

2022-07-09T20:10:39Z

en>Graion Dilach: MakeInfantry=9?! Somebody must've messed those two up. MakeInfantry=0 was intended, I'm 100% sure.

2011-08-05T14:55:34Z

MakeInfantry=9?! Somebody must've messed those two up. MakeInfantry=0 was intended, I'm 100% sure.

← Older revision		Revision as of 16:55, 5 August 2011
Line 42:		Line 42:
	==Applications==		==Applications==
	===Neutral infantry===		===Neutral infantry===
	You can create [[neutral]] infantry oppponents by not using an {{f\|InfDeath\|9\|link}} weapon (this includes using an animation that is not caused by a weapon such as crate pickups or a building anim). For example, setting {{tt\|[[rules\|rulesmd.ini]]}}{{arr\|r}}{{tt\|[E1]}}{{arr\|r}}{{f\|DeathAnims\|NEWANIM\|link}} and {{tt\|[[art\|artmd.ini]]}}{{arr\|r}}{{tt\|[NEWANIM]}}{{arr\|r}}{{f\|MakeInfantry\|9\|link}} would cause the GI to turn into a neutral Brute when the GI dies.		You can create [[neutral]] infantry oppponents by not using an {{f\|InfDeath\|9\|link}} weapon (this includes using an animation that is not caused by a weapon such as crate pickups or a building anim). For example, setting {{tt\|[[rules\|rulesmd.ini]]}}{{arr\|r}}{{tt\|[E1]}}{{arr\|r}}{{f\|DeathAnims\|NEWANIM\|link}} and {{tt\|[[art\|artmd.ini]]}}{{arr\|r}}{{tt\|[NEWANIM]}}{{arr\|r}}{{f\|MakeInfantry\|0\|link}} would cause the GI to turn into a neutral Brute when the GI dies.

	===Player-owned infantry===		===Player-owned infantry===

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

2009-11-27T08:17:41Z

Replacing Template:TTL with Template:F.

en>DCoder: Adding info on spawn failure bug, might need rewording, adjusted heading levels, do we need a categ for lag-inducing phenomenons ?

2008-05-23T05:51:27Z

Adding info on spawn failure bug, might need rewording, adjusted heading levels, do we need a categ for lag-inducing phenomenons ?

← Older revision		Revision as of 07:51, 23 May 2008
Line 20:		Line 20:
	If this [[animation]] was invoked by an [[InfDeath]] other than 9, and the [[animation]] has {{TTL\|AltPalette\|yes}} set, then any remappable colours will be remapped to a seemingly random player colour.		If this [[animation]] was invoked by an [[InfDeath]] other than 9, and the [[animation]] has {{TTL\|AltPalette\|yes}} set, then any remappable colours will be remapped to a seemingly random player colour.

	=Using MakeInfantry Logic (tutorial by Marshall)=		==Using MakeInfantry Logic (tutorial by Marshall)==
	If you've been reading up on MakeInfantry (mutation) logic elsewhere and haven't really understood much then that's okay - this tutorial is probably more easily understood if you haven't read any other MakeInfantry information before.		If you've been reading up on MakeInfantry (mutation) logic elsewhere and haven't really understood much then that's okay - this tutorial is probably more easily understood if you haven't read any other MakeInfantry information before.

Line 58:		Line 58:
	*Do not use an area-effect mutation weapon if [[paradrops\|paratroopers]] are not immune to it - an [[Internal Error]] will occur if a falling paratrooper is killed by an area-effect mutation weapon (point based mutation deaths seem to be okay and just result in the paratrooper exploding, and the Genetic Mutator super weapon appears to have been designed to prevent it killing such infantry).		*Do not use an area-effect mutation weapon if [[paradrops\|paratroopers]] are not immune to it - an [[Internal Error]] will occur if a falling paratrooper is killed by an area-effect mutation weapon (point based mutation deaths seem to be okay and just result in the paratrooper exploding, and the Genetic Mutator super weapon appears to have been designed to prevent it killing such infantry).
	*The animation associated with {{TTL\|InfDeath}} 9 '''must''' have a {{TTL\|MakeInfantry}} flag and it must be set to a valid {{TTL\|AnimToInfantry}} list index. If it doesn't, then the animation will not play at all. <small>[Actually, it doesn't have to have the {{TTL\|MakeInfantry}} flag ''if'' it has instead a {{TTL\|Next}} flag so that the last animation of a sequence of animations invoked by InfDeath 9 ''does'' have a {{TTL\|MakeInfantry}} flag.]</small>		*The animation associated with {{TTL\|InfDeath}} 9 '''must''' have a {{TTL\|MakeInfantry}} flag and it must be set to a valid {{TTL\|AnimToInfantry}} list index. If it doesn't, then the animation will not play at all. <small>[Actually, it doesn't have to have the {{TTL\|MakeInfantry}} flag ''if'' it has instead a {{TTL\|Next}} flag so that the last animation of a sequence of animations invoked by InfDeath 9 ''does'' have a {{TTL\|MakeInfantry}} flag.]</small>
			*When an animation that has this flag set is playing and the cell is obstructed so the infantry cannot be spawned (e.g., a vehicle is parked in that cell), the game will stubbornly keep trying to place it, and cause increasing lag, as well as an ever-growing memory leak, for the remainder of the game session. The only way to prevent accumulating lag is to make sure the cell in question is clear. Note that this also happens when the cell is occupied by invincible objects such as impassable terrain tiles (cliffs, water) or [[TerrainTypes]] such as ore mines. In this case, there is no fix for the ever growing lag and memory leakage, short of aborting the current game session. <!-- It's 5 AM, do you know where your garbage collector is? blargh. -->

	=See also=		==See also==
	*[[Mutation]]		*[[Mutation]]

	[[Category:RA2/YR Tutorials]]		[[Category:RA2/YR Tutorials]]

← Older revision		Revision as of 22:10, 9 July 2022
Line 62:		Line 62:
	==See also==		==See also==
	*[[Mutation]]		*[[Mutation]]
			*[[InfDeath]]
			*[[DeathAnims]]
	[[Category:RA2/YR Tutorials]]		[[Category:RA2/YR Tutorials]]

← Older revision		Revision as of 10:17, 27 November 2009
Line 10:		Line 10:
	}}		}}

	Specifies the list index of {{tt\|rulesmd.ini}}{{arr\|r}}[{{~~TTL~~\|General}}]{{arr\|r}}{{~~TTL~~\|AnimToInfantry}} to refer to to determine which [[InfantryType]] should be created when this [[animation]] finishes.		Specifies the list index of {{tt\|rulesmd.ini}}{{arr\|r}}[{{f\|General\|link}}]{{arr\|r}}{{f\|AnimToInfantry\|link}} to refer to to determine which [[InfantryType]] should be created when this [[animation]] finishes.

	If this [[animation]] was invoked by [[InfDeath]] 8 or 9 then the resulting [[InfantryType]] will be given to the owner of the killing unit.		If this [[animation]] was invoked by [[InfDeath]] 8 or 9 then the resulting [[InfantryType]] will be given to the owner of the killing unit.
Line 18:		Line 18:
	If this [[animation]] was invoked by [[InfDeath]] 9 then the [[animation]] will be hard-coded to use the unit palette instead of the animation palette, and any remappable colours will be remapped to the player colour of the owner of the killing unit.		If this [[animation]] was invoked by [[InfDeath]] 9 then the [[animation]] will be hard-coded to use the unit palette instead of the animation palette, and any remappable colours will be remapped to the player colour of the owner of the killing unit.

	If this [[animation]] was invoked by an [[InfDeath]] other than 9, and the [[animation]] has {{~~TTL~~\|AltPalette\|yes}} set, then any remappable colours will be remapped to a seemingly random player colour.		If this [[animation]] was invoked by an [[InfDeath]] other than 9, and the [[animation]] has {{f\|AltPalette\|yes\|link}} set, then any remappable colours will be remapped to a seemingly random player colour.

	==Using MakeInfantry Logic (tutorial by Marshall)==		==Using MakeInfantry Logic (tutorial by Marshall)==
Line 28:		Line 28:
	<br>		<br>
	1. You need to list all the [[InfantryTypes]] that you would like to spawn using MakeInfantry logic. You do this in a comma separated list on the following flag:<br>		1. You need to list all the [[InfantryTypes]] that you would like to spawn using MakeInfantry logic. You do this in a comma separated list on the following flag:<br>
	{{tt\|[[rules\|rulesmd.ini]]}}{{arr\|r}}[[General\|[General]]]{{arr\|r}}{{~~TTL~~\|AnimToInfantry}}<br>		{{tt\|[[rules\|rulesmd.ini]]}}{{arr\|r}}[[General\|[General]]]{{arr\|r}}{{f\|AnimToInfantry\|link}}<br>
	For example, {{~~TTL~~\|AnimToInfantry\|BRUTE,NEWUNIT,GHOST}}<br>		For example, {{f\|AnimToInfantry\|BRUTE,NEWUNIT,GHOST\|link}}<br>
	Later on we will refer to these [[InfantryTypes]] by their list index. In the above example, {{tt\|BRUTE}} would have an index of zero, {{tt\|NEWUNIT}} would have an index of 1 and {{tt\|GHOST}} would have an index of 2.<br>		Later on we will refer to these [[InfantryTypes]] by their list index. In the above example, {{tt\|BRUTE}} would have an index of zero, {{tt\|NEWUNIT}} would have an index of 1 and {{tt\|GHOST}} would have an index of 2.<br>
	<br>		<br>
	2. In order to spawn an [[InfantryType]] from the {{~~TTL~~\|AnimToInfantry}} list then an animation must be played - the [[InfantryType]] will be spawned once the animation finishes. <br>		2. In order to spawn an [[InfantryType]] from the {{f\|AnimToInfantry\|link}} list then an animation must be played - the [[InfantryType]] will be spawned once the animation finishes. <br>
	To make the spawned [[InfantryType]] player-owned, another infantry unit in-game must be killed by a weapon that was fired by a player-owned unit. Further more, the weapon's {{~~TTL~~\|Warhead}} '''must''' have {{~~TTL~~\|InfDeath\|9}} set.<br>		To make the spawned [[InfantryType]] player-owned, another infantry unit in-game must be killed by a weapon that was fired by a player-owned unit. Further more, the weapon's {{f\|Warhead\|link}} '''must''' have {{f\|InfDeath\|9\|link}} set.<br>
	Note that {{~~TTL~~\|MutateWarhead}} and {{~~TTL~~\|MutateExplosionWarhead}} are only used by the Genetic Mutator super weapon and have '''no bearing''' on this logic.		Note that {{f\|MutateWarhead\|link}} and {{f\|MutateExplosionWarhead\|link}} are only used by the Genetic Mutator super weapon and have '''no bearing''' on this logic.
	You can change the animation referenced by [[InfDeath]] 9 if you want (see [[InfDeath\|InfDeaths]]).<br>		You can change the animation referenced by [[InfDeath]] 9 if you want (see [[InfDeath\|InfDeaths]]).<br>
	<br>		<br>
	3. In {{Tt\|[[art\|artmd.ini]]}}, find or create the [[animation]] section for the animation that you want to spawn an [[InfantryType]] (see {{tt\|[GENDEATH]}} as an example).<br>		3. In {{Tt\|[[art\|artmd.ini]]}}, find or create the [[animation]] section for the animation that you want to spawn an [[InfantryType]] (see {{tt\|[GENDEATH]}} as an example).<br>
	You need to set {{~~TTL~~\|MakeInfantry\|X}} on your animation, where X is the list index number of the [[InfantryType]] you wish to spawn, taken from the {{~~TTL~~\|AnimToInfantry}} flag discussed in the first step.		You need to set {{f\|MakeInfantry\|X\|link}} on your animation, where X is the list index number of the [[InfantryType]] you wish to spawn, taken from the {{f\|AnimToInfantry\|link}} flag discussed in the first step.

	==Applications==		==Applications==
	===Neutral infantry===		===Neutral infantry===
	You can create [[neutral]] infantry oppponents by not using an {{~~TTL~~\|InfDeath\|9}} weapon (this includes using an animation that is not caused by a weapon such as crate pickups or a building anim). For example, setting {{tt\|[[rules\|rulesmd.ini]]}}{{arr\|r}}{{tt\|[E1]}}{{arr\|r}}{{~~TTL~~\|DeathAnims\|NEWANIM}} and {{tt\|[[art\|artmd.ini]]}}{{arr\|r}}{{tt\|[NEWANIM]}}{{arr\|r}}{{~~TTL~~\|MakeInfantry\|9}} would cause the GI to turn into a neutral Brute when the GI dies.		You can create [[neutral]] infantry oppponents by not using an {{f\|InfDeath\|9\|link}} weapon (this includes using an animation that is not caused by a weapon such as crate pickups or a building anim). For example, setting {{tt\|[[rules\|rulesmd.ini]]}}{{arr\|r}}{{tt\|[E1]}}{{arr\|r}}{{f\|DeathAnims\|NEWANIM\|link}} and {{tt\|[[art\|artmd.ini]]}}{{arr\|r}}{{tt\|[NEWANIM]}}{{arr\|r}}{{f\|MakeInfantry\|9\|link}} would cause the GI to turn into a neutral Brute when the GI dies.

	===Player-owned infantry===		===Player-owned infantry===
	You can create multiple weapons that result in a player-owned [[InfantryType]] being created as long as they all have {{~~TTL~~\|InfDeath\|9}} set on their {{tt\|[[Warhead\|warheads]]}}. However the limitation is that they will all spawn the same [[InfantryType]].<br>		You can create multiple weapons that result in a player-owned [[InfantryType]] being created as long as they all have {{f\|InfDeath\|9\|link}} set on their {{tt\|[[Warhead\|warheads]]}}. However the limitation is that they will all spawn the same [[InfantryType]].<br>
	You could, of course, change the [[InfantryType]] that the Genetic Mutator spawns, or you could convert the Genetic Mutator into a non-mutation weapon if you wanted to.		You could, of course, change the [[InfantryType]] that the Genetic Mutator spawns, or you could convert the Genetic Mutator into a non-mutation weapon if you wanted to.

Line 52:		Line 52:

	==Actually, you can have two player-owned mutations==		==Actually, you can have two player-owned mutations==
	I lied above so that you could more easily understand the MakeInfantry logic first. In truth, by using {{~~TTL~~\|InfDeath\|8}}, you can spawn a second [[InfantryType]] that will be player-owned. However, in order to make use of {{~~TTL~~\|InfDeath}} 8 for MakeInfantry purposes you will have to sacrifice the unique Virus [[InfDeath]] animation (or re-order the other [[InfDeath]] animations, but you ''will'' have to sacrifice one of them). There is also a limitation of [[InfDeath]] 8 in that the animation cannot remap the player colours correctly (see the description of the {{~~TTL~~\|MakeInfantry}} flag at the top of this page).<br>		I lied above so that you could more easily understand the MakeInfantry logic first. In truth, by using {{f\|InfDeath\|8\|link}}, you can spawn a second [[InfantryType]] that will be player-owned. However, in order to make use of {{f\|InfDeath\|link}} 8 for MakeInfantry purposes you will have to sacrifice the unique Virus [[InfDeath]] animation (or re-order the other [[InfDeath]] animations, but you ''will'' have to sacrifice one of them). There is also a limitation of [[InfDeath]] 8 in that the animation cannot remap the player colours correctly (see the description of the {{f\|MakeInfantry\|link}} flag at the top of this page).<br>
	But that really is it though, the other [[InfDeath\|InfDeaths]] won't work for this.		But that really is it though, the other [[InfDeath\|InfDeaths]] won't work for this.

	{{Bugs}}		{{Bugs}}
	*Do not use an area-effect mutation weapon if [[paradrops\|paratroopers]] are not immune to it - an [[Internal Error]] will occur if a falling paratrooper is killed by an area-effect mutation weapon (point based mutation deaths seem to be okay and just result in the paratrooper exploding, and the Genetic Mutator super weapon appears to have been designed to prevent it killing such infantry).		*Do not use an area-effect mutation weapon if [[paradrops\|paratroopers]] are not immune to it - an [[Internal Error]] will occur if a falling paratrooper is killed by an area-effect mutation weapon (point based mutation deaths seem to be okay and just result in the paratrooper exploding, and the Genetic Mutator super weapon appears to have been designed to prevent it killing such infantry).
	*The animation associated with {{~~TTL~~\|InfDeath}} 9 '''must''' have a {{~~TTL~~\|MakeInfantry}} flag and it must be set to a valid {{~~TTL~~\|AnimToInfantry}} list index. If it doesn't, then the animation will not play at all. <small>[Actually, it doesn't have to have the {{~~TTL~~\|MakeInfantry}} flag ''if'' it has instead a {{~~TTL~~\|Next}} flag so that the last animation of a sequence of animations invoked by InfDeath 9 ''does'' have a {{~~TTL~~\|MakeInfantry}} flag.]</small>		*The animation associated with {{f\|InfDeath\|link}} 9 '''must''' have a {{f\|MakeInfantry\|link}} flag and it must be set to a valid {{f\|AnimToInfantry\|link}} list index. If it doesn't, then the animation will not play at all. <small>[Actually, it doesn't have to have the {{f\|MakeInfantry\|link}} flag ''if'' it has instead a {{f\|Next\|link}} flag so that the last animation of a sequence of animations invoked by InfDeath 9 ''does'' have a {{f\|MakeInfantry\|link}} flag.]</small>
	*When an animation that has this flag set is playing and the cell is obstructed so the infantry cannot be spawned (e.g., a vehicle is parked in that cell), the game will stubbornly keep trying to place it, and cause increasing lag, as well as an ever-growing memory leak, for the remainder of the game session. The only way to prevent accumulating lag is to make sure the cell in question is clear. Note that this also happens when the cell is occupied by invincible objects such as impassable terrain tiles (cliffs, water) or [[TerrainTypes]] such as ore mines. In this case, there is no fix for the ever growing lag and memory leakage, short of aborting the current game session. <!-- It's 5 AM, do you know where your garbage collector is? blargh. -->		*When an animation that has this flag set is playing and the cell is obstructed so the infantry cannot be spawned (e.g., a vehicle is parked in that cell), the game will stubbornly keep trying to place it, and cause increasing lag, as well as an ever-growing memory leak, for the remainder of the game session. The only way to prevent accumulating lag is to make sure the cell in question is clear. Note that this also happens when the cell is occupied by invincible objects such as impassable terrain tiles (cliffs, water) or [[TerrainTypes]] such as ore mines. In this case, there is no fix for the ever growing lag and memory leakage, short of aborting the current game session. <!-- It's 5 AM, do you know where your garbage collector is? blargh. -->