Legacy RockPatch Wishlist/Page 2 - Revision history

MarkJFox: 72 revisions imported

2025-03-31T19:56:18Z

72 revisions imported

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

en>DCoder: Protected "Legacy RockPatch Wishlist/Page 2": Outdated [edit=sysop:move=sysop:read=sysop]

2009-09-08T03:58:20Z

Protected "Legacy RockPatch Wishlist/Page 2": Outdated [edit=sysop:move=sysop:read=sysop]

← Older revision	Revision as of 05:58, 8 September 2009
(No difference)

en>DCoder: RockPatch:Wishlist/Page 2 moved to Legacy RockPatch Wishlist/Page 2: obsolete namespace

2008-07-12T09:48:37Z

RockPatch:Wishlist/Page 2 moved to Legacy RockPatch Wishlist/Page 2: obsolete namespace

← Older revision	Revision as of 11:48, 12 July 2008
(No difference)

en>VK at 13:54, 2 June 2007

2007-06-02T13:54:57Z

← Older revision		Revision as of 15:54, 2 June 2007
Line 2:		Line 2:
	=Enhancements=		=Enhancements=
	{{Wishlist/TOC}}		{{Wishlist/TOC}}
	*Make GDIPowerTurbine=GAPOWRUP work for every side
	*True Air-to-Air combat		*True Air-to-Air combat

Line 64:		Line 64:
	*Different parachute animations on the New Paradrop Superweapons, could let the modder have both a paradrop and simulated drop pods superweapon at once, possible tag would be 'ParachuteAnim=xxxxx'		*Different parachute animations on the New Paradrop Superweapons, could let the modder have both a paradrop and simulated drop pods superweapon at once, possible tag would be 'ParachuteAnim=xxxxx'
	*Additional SpeedTypes		*Additional SpeedTypes
	*Aircraft takeoff/landing pitch, as opposed to VTOL.
	*Automated building of units outside of clicking sidebar (E.g; a "recruiting center" might build a free infantry each minute)		*Automated building of units outside of clicking sidebar (E.g; a "recruiting center" might build a free infantry each minute)
	*'AlliedEngineer', 'SovietEngineer', 'ThirdEngineer', and possibly 'FourthEngineer' tags instead of the regular 'Engineer=' in [General] which makes all Conyards spawn an Allied Engineer instead of the side specific. Also, on that note:		*'AlliedEngineer', 'SovietEngineer', 'ThirdEngineer', and possibly 'FourthEngineer' tags instead of the regular 'Engineer=' in [General] which makes all Conyards spawn an Allied Engineer instead of the side specific. Also, on that note:
Line 86:		Line 86:
	*enable tibtrees to have a SpawnsOreType=(number for the [Tiberiums] list) to allow trees to spawn gems, and other new ores, also, i played with the values and gems refuse to grow and spread, even with Growth=1 GrowthPercentage=1 Spread=1 SpreadPercentage=1 Ore with the same values grows so fast it covers most of the map within a few seconds, this would need fixing, the default values state not to grow, so i don't see why it would need to be hardcoded to not grow.		*enable tibtrees to have a SpawnsOreType=(number for the [Tiberiums] list) to allow trees to spawn gems, and other new ores, also, i played with the values and gems refuse to grow and spread, even with Growth=1 GrowthPercentage=1 Spread=1 SpreadPercentage=1 Ore with the same values grows so fast it covers most of the map within a few seconds, this would need fixing, the default values state not to grow, so i don't see why it would need to be hardcoded to not grow.

	==Not clear==		==Not clear for VKs brain==
	*Remove the HardCoding in the Clone Vat Logic ;Dunno, perhaps they meant make it able to grind infanty again like it could in RA2? [[User:Blade\|Blade]] 00:51, 20 February 2007 (CET)		*Remove the HardCoding in the Clone Vat Logic ;Dunno, perhaps they meant make it able to grind infanty again like it could in RA2? [[User:Blade\|Blade]] 00:51, 20 February 2007 (CET)
	*Find hardcoded items (e.g. animations, units, buildings, infantry and such) and make them un-hardcoded		*Find hardcoded items (e.g. animations, units, buildings, infantry and such) and make them un-hardcoded
			*Make GDIPowerTurbine=GAPOWRUP work for every side

	==Done==		==Done==
			*Aircraft takeoff/landing pitch, as opposed to VTOL.
	*mouse.shp frames to use, like [Weapon]AttackCursor=start_frame,end_frame; [Unit]Move/Deploy/EnterCursor= )		*mouse.shp frames to use, like [Weapon]AttackCursor=start_frame,end_frame; [Unit]Move/Deploy/EnterCursor= )
	*More "special" mouse-cursors, like C4 or the SW-cursors (if possible, this should be implemented via tags, pointing to exact		*More "special" mouse-cursors, like C4 or the SW-cursors (if possible, this should be implemented via tags, pointing to exact

en>Nighthawk200: Wish already exists further up ;). It's been there since before the feature was put into ETS.

2007-05-25T09:23:13Z

Wish already exists further up ;). It's been there since before the feature was put into ETS.

← Older revision		Revision as of 11:23, 25 May 2007
Line 85:		Line 85:
	*Allow Color= to work on tiberiums, when using a Palette= tag, to allow different varients of ores.		*Allow Color= to work on tiberiums, when using a Palette= tag, to allow different varients of ores.
	*enable tibtrees to have a SpawnsOreType=(number for the [Tiberiums] list) to allow trees to spawn gems, and other new ores, also, i played with the values and gems refuse to grow and spread, even with Growth=1 GrowthPercentage=1 Spread=1 SpreadPercentage=1 Ore with the same values grows so fast it covers most of the map within a few seconds, this would need fixing, the default values state not to grow, so i don't see why it would need to be hardcoded to not grow.		*enable tibtrees to have a SpawnsOreType=(number for the [Tiberiums] list) to allow trees to spawn gems, and other new ores, also, i played with the values and gems refuse to grow and spread, even with Growth=1 GrowthPercentage=1 Spread=1 SpreadPercentage=1 Ore with the same values grows so fast it covers most of the map within a few seconds, this would need fixing, the default values state not to grow, so i don't see why it would need to be hardcoded to not grow.
	* Copy NeedsTheater= logic from ETS.

	==Not clear==		==Not clear==

en>Bachsau: /* Enhancements */

2007-05-24T19:50:33Z

Enhancements

← Older revision		Revision as of 21:50, 24 May 2007
Line 85:		Line 85:
	*Allow Color= to work on tiberiums, when using a Palette= tag, to allow different varients of ores.		*Allow Color= to work on tiberiums, when using a Palette= tag, to allow different varients of ores.
	*enable tibtrees to have a SpawnsOreType=(number for the [Tiberiums] list) to allow trees to spawn gems, and other new ores, also, i played with the values and gems refuse to grow and spread, even with Growth=1 GrowthPercentage=1 Spread=1 SpreadPercentage=1 Ore with the same values grows so fast it covers most of the map within a few seconds, this would need fixing, the default values state not to grow, so i don't see why it would need to be hardcoded to not grow.		*enable tibtrees to have a SpawnsOreType=(number for the [Tiberiums] list) to allow trees to spawn gems, and other new ores, also, i played with the values and gems refuse to grow and spread, even with Growth=1 GrowthPercentage=1 Spread=1 SpreadPercentage=1 Ore with the same values grows so fast it covers most of the map within a few seconds, this would need fixing, the default values state not to grow, so i don't see why it would need to be hardcoded to not grow.
			* Copy NeedsTheater= logic from ETS.

	==Not clear==		==Not clear==

195.195.244.67: /* Enhancements */

2007-05-16T11:01:50Z

Enhancements

← Older revision		Revision as of 13:01, 16 May 2007
Line 82:		Line 82:
	*Allowing SpyPlane, and it's clones to have custom EVA Activated events.		*Allowing SpyPlane, and it's clones to have custom EVA Activated events.
	*Allow custom warfactory exit paths. Suggest useing the same direction logic that backs the posedir and deploydir tags. Example: The unit would appear at the location pointed to by ExitCoord= then moves in the dirction pointed out by the possable new tag ExitDir=. As it stands right now in Yuri the unit first appears at the ExitCoord= point for a secont then re-appears and moves as if it where the origenal warfactory which looks to be the equivlent to what would be ExitDir=60		*Allow custom warfactory exit paths. Suggest useing the same direction logic that backs the posedir and deploydir tags. Example: The unit would appear at the location pointed to by ExitCoord= then moves in the dirction pointed out by the possable new tag ExitDir=. As it stands right now in Yuri the unit first appears at the ExitCoord= point for a secont then re-appears and moves as if it where the origenal warfactory which looks to be the equivlent to what would be ExitDir=60
			*improve the Tiberiums logic to allow additional types of ore rather than just gold and gems.
			*Allow Color= to work on tiberiums, when using a Palette= tag, to allow different varients of ores.
			*enable tibtrees to have a SpawnsOreType=(number for the [Tiberiums] list) to allow trees to spawn gems, and other new ores, also, i played with the values and gems refuse to grow and spread, even with Growth=1 GrowthPercentage=1 Spread=1 SpreadPercentage=1 Ore with the same values grows so fast it covers most of the map within a few seconds, this would need fixing, the default values state not to grow, so i don't see why it would need to be hardcoded to not grow.

	==Not clear==		==Not clear==

en>Renegade: Reverted edits by 222.93.246.48 (Talk); changed back to last version by 24.145.152.184

2007-05-02T22:26:12Z

Reverted edits by 222.93.246.48 (Talk); changed back to last version by 24.145.152.184

← Older revision		Revision as of 00:26, 3 May 2007
Line 2:		Line 2:
	=Enhancements=		=Enhancements=
	{{Wishlist/TOC}}		{{Wishlist/TOC}}
	~~Allowing "Armory Buildings" use "Gather Point function" like Barracks and WeaponFactory to make the inftrany exit and auto run to the gather point.~~
	*Make GDIPowerTurbine=GAPOWRUP work for every side		*Make GDIPowerTurbine=GAPOWRUP work for every side
	*True Air-to-Air combat		*True Air-to-Air combat

222.93.246.48: /* Enhancements */

2007-05-02T16:49:07Z

Enhancements

← Older revision		Revision as of 18:49, 2 May 2007
Line 2:		Line 2:
	=Enhancements=		=Enhancements=
	{{Wishlist/TOC}}		{{Wishlist/TOC}}
			Allowing "Armory Buildings" use "Gather Point function" like Barracks and WeaponFactory to make the inftrany exit and auto run to the gather point.
	*Make GDIPowerTurbine=GAPOWRUP work for every side		*Make GDIPowerTurbine=GAPOWRUP work for every side
	*True Air-to-Air combat		*True Air-to-Air combat

24.145.152.184 at 04:12, 4 April 2007

2007-04-04T04:12:33Z

← Older revision		Revision as of 06:12, 4 April 2007
Line 81:		Line 81:
	*Currently a warhead appies damage to buildings once per cell. Meaning a 3x3 building is subject to damage 9 times by a warhead with a high CellSpread=. This makes some situations where you cant control exact or absolute damage. Example:You cant have a weapon that damages a 1x1 building with the exact damage a 3x3 building takes in the same Cellspread. I would like to see a warhead tag similar to DamageOnce=yes/no that dictates that the warhead will only deal damage once per object it comes in contact with. This takes affect at the first cell of the cellspread radius that the building occupies and takes in to effect Percentatmax=.		*Currently a warhead appies damage to buildings once per cell. Meaning a 3x3 building is subject to damage 9 times by a warhead with a high CellSpread=. This makes some situations where you cant control exact or absolute damage. Example:You cant have a weapon that damages a 1x1 building with the exact damage a 3x3 building takes in the same Cellspread. I would like to see a warhead tag similar to DamageOnce=yes/no that dictates that the warhead will only deal damage once per object it comes in contact with. This takes affect at the first cell of the cellspread radius that the building occupies and takes in to effect Percentatmax=.
	*Allowing SpyPlane, and it's clones to have custom EVA Activated events.		*Allowing SpyPlane, and it's clones to have custom EVA Activated events.
	*Allow AutoFire=yes to be used on drop pod and paradrop superweapons. If used, the units would be auto-dropped at the player's base.
	*Allow custom warfactory exit paths. Suggest useing the same direction logic that backs the posedir and deploydir tags. Example: The unit would appear at the location pointed to by ExitCoord= then moves in the dirction pointed out by the possable new tag ExitDir=. As it stands right now in Yuri the unit first appears at the ExitCoord= point for a secont then re-appears and moves as if it where the origenal warfactory which looks to be the equivlent to what would be ExitDir=60		*Allow custom warfactory exit paths. Suggest useing the same direction logic that backs the posedir and deploydir tags. Example: The unit would appear at the location pointed to by ExitCoord= then moves in the dirction pointed out by the possable new tag ExitDir=. As it stands right now in Yuri the unit first appears at the ExitCoord= point for a secont then re-appears and moves as if it where the origenal warfactory which looks to be the equivlent to what would be ExitDir=60