Legacy RockPatch Wishlist - Revision history

MarkJFox: 146 revisions imported

2025-03-31T19:56:15Z

146 revisions imported

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

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

2009-09-08T03:57:11Z

Protected "Legacy RockPatch Wishlist": Outdated [edit=sysop:move=sysop:read=sysop] [cascading]

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

en>DCoder: splitting off content

2008-07-12T10:01:17Z

splitting off content

Show changes

en>DCoder: RockPatch:Wishlist moved to Legacy RockPatch Wishlist: removing obsolete namespace

2008-07-12T09:45:48Z

RockPatch:Wishlist moved to Legacy RockPatch Wishlist: removing obsolete namespace

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

en>Renegade at 21:17, 21 October 2007

2007-10-21T21:17:09Z

← Older revision		Revision as of 23:17, 21 October 2007
Line 1:		Line 1:
	__NOTOC__[[Category:RockPatch]]{{RockPatch}}		__NOTOC__[[Category:RockPatch]]{{RockPatch}}

	~~{\| align~~=~~"center" width="98%" class="table_parted"~~		=Attention!=
	!~~colspan~~=~~"2"\|Introduction~~		This page is '''obsolete'''. Feature requests are now managed through the [http://bugs.renegadeprojects.com/set_project.php?ref=view_all_set.php%3Ftype=3%26source_query_id=10&project_id=6 Issue Tracker].
	\|-
	~~\|width="50%"\|<div align="center">~~'''~~What this List is'~~''~~</div>You~~'~~re looking at~~ the ~~community-editable wishlist for~~ [~~[RockPatch~~:~~Main\|RockPatch]~~].

	~~If you would like~~ to ~~see~~ a ~~specific feature added~~ to ~~RockPatch~~, ~~add~~ it ~~at an appropriate place on this list~~. '~~'Do~~ not ~~contact CnCVK~~ in ~~any other way~~.~~'' It just doesn~~'t ~~work that way~~. ~~If the entire community started IM sessions~~ and ~~bugged about features the moment he signed on, he'd soon quit making the patch at all~~.<br>		===How to request a Feature===
	~~As such, all wishes~~ ''~~not~~'' ~~made through~~ the ~~wishlist will be ignored~~. ~~(And~~, ~~most likely~~, pd ~~will remember~~ you in a ~~way not helping other wishes~~ you ~~have~~.)		Go to [http://bugs.renegadeprojects.com/set_project.php?ref=view_all_set.php%3Ftype=3%26source_query_id=10&project_id=6 bugs.renegadeprojects.com]. Click on <code>Login</code>. If you have an account, log into it. If you want to be informed about your request's outcome, plan to request several features, or want to report bugs later, click <code>Signup for a new account</code> and register; if not, click <code>Login Anonymously</code>. Once you are logged in, either normally or anonymously, click on <code>Report Issue</code>. If you didn't do so already, the system will ask you to select a project. Choose <code>RockPatch2</code> and click <code>Select Project</code>. Now set:<br>
			*'''Category:''' Feature Request
			*'''Reproducibility:''' N/A
			*'''Severity:''' feature
			*'''Product Version:''' ''empty''
			*'''Summary:''' A one-sentence description of your request - this is what will appear in the issue list, so if you want pd to actually read it, summaries like "ADD THIS PLEASE!!!1!!" are not a good idea.
			*'''Description:''' A detailed description of your request - don't write novels, but the more details you have, the easier pd can assess the wish.
			*'''Additional Information:''' What the title says - possibly a summarized list of the suggested ini flags or something like that. Anything you have in your head about your wish that doesn't quite fit into the request as such.
			*'''Upload file:''' This is mainly used for bug reports, but if you did something like a photoshop mockup of your request, you could attach it here.
			*'''View Status:''' Public
			*'''Report Stay:''' If you wish to return to the report form to add more requests or bug reports, check this.

	~~Also note [[RockPatch:Votelist\|the Votelist]].~~		Afterwards, click <code>Submit Report</code>. Congratulations, you just requested a feature.
	~~\|width="50%"\|~~<~~div align="center"~~>~~'''What this List is not'''~~</~~div~~>
	*This is '''not''' a list of ''demands''.
	*These are '''not''' features that ''are'' already implemented.
	*This list does '''not''' guarantee the feature ''will'' be implemented.
	\|-
	~~\|width="100%" colspan="2"\|<div align="center">'''Where to put your Wish'''</div>~~
	*There are several topical lists, ~~choose the one that fits best.~~
	*Newer wishes are added to the bottom.
	*The list was spread over several pages for a ~~reason. ''Keep it that way.'' (Look at the history to see why~~.)

	'''~~Example:~~''' ~~You wish to~~ request a ~~warhead-feature~~. ~~That would~~, ~~of course~~, be ~~a Totally New Feature~~. ~~However,~~ ''~~Weapons related~~'' ~~fits even better for something about warheads~~. ~~Weapons related~~ is ~~on Page 5~~. ~~So your wish belongs to Page 5, Weapons related~~, at the bottom of the ~~list~~.		===The Reason for this Change===
	\|}		On first glance, this new procedure may look a lot more complicated than the previous one, but check out what you get in return:
			*'''Status reports''' - each request is a single item in the database with its own status information like priority, eta, status, etc., etc.; you won't just know whether pd generally works on your request, but you can see in detail how long he things it'll take, how far he is, and in which version it will be available.
			*'''Comments''' - in the past, there were often opinions or improvement suggestions on wishes by other users. For reasons of order, commenting directly on the page was prohibited; on the tracker, this is not the case. As each issue has its own page, everyone can leave a note at the bottom specifically for that wish, giving his opinion or suggesting improvements for it.
			*'''[http://bugs.renegadeprojects.com/set_project.php?ref=roadmap_page.php&project_id=6 Roadmap] & [http://bugs.renegadeprojects.com/set_project.php?ref=changelog_page.php&project_id=6 Changelog]''' - with both feature requests and bugs tracked by the same system, said system can directly and immediately calculate how close to completion the currently worked on version is. No need to wait for updated wiki pages or forum posts - just check the percentage on the roadmap!

	~~{{quote\|~~pd~~\|I just want~~ to ~~underline that this is not~~ a ~~demand list but only a collection of ideas because I~~'~~m the only person who has the possibility to change anything at the moment~~.~~.. teaching others how to do this would be~~ a ~~solution but~~ it ~~would mean much learning to them (I think)~~.~~<br>~~		And that's just what ''you'' get out of it. For pd, it means a lot less management effort, and an easy way to quickly assess, prioritize and plan feature additions. When he dismisses a wish, it's marked as dismissed. When he chooses a wish, it's automatically on the roadmap. A cleaner environment for both sides, and less time spent updating ModEnc for pd.
	~~I will choose the easiest~~ for me and ~~the most useful~~ for ~~the community things first.<br>~~
	~~So don't be angry if you're wish doesn't get "fulfilled"~~.}}

	~~{{quote\|CnCVK\|~~
	~~The wishlist~~ '''~~only~~''' ~~help me to find good ideas.<br>~~		'''Everything below this line exists purely for archiving purposes.'''
	~~It's not list of demands and this list does not guarantee the feature will be implemented.~~		----
	}}

	=General Bugfixes/Corrections=		=General Bugfixes/Corrections=

en>Renegade: Removed end-notice, now included in Template:RockPatch

2007-06-09T13:14:20Z

Removed end-notice, now included in Template:RockPatch

← Older revision		Revision as of 15:14, 9 June 2007
Line 1:		Line 1:
	__NOTOC__[[Category:RockPatch]]{{RockPatch}}		__NOTOC__[[Category:RockPatch]]{{RockPatch}}

	~~{{HorizontalBar\|Attention: This project was recently ended.}}~~

	{\| align="center" width="98%" class="table_parted"		{\| align="center" width="98%" class="table_parted"

en>Striker: Addet the Hint - Attention: This project was recently ended.

2007-06-09T10:48:32Z

Addet the Hint - Attention: This project was recently ended.

← Older revision		Revision as of 12:48, 9 June 2007
Line 1:		Line 1:
	__NOTOC__[[Category:RockPatch]]{{RockPatch}}		__NOTOC__[[Category:RockPatch]]{{RockPatch}}

			{{HorizontalBar\|Attention: This project was recently ended.}}

	{\| align="center" width="98%" class="table_parted"		{\| align="center" width="98%" class="table_parted"

en>VK at 13:52, 2 June 2007

2007-06-02T13:52:08Z

← Older revision		Revision as of 15:52, 2 June 2007
Line 34:		Line 34:
	=General Bugfixes/Corrections=		=General Bugfixes/Corrections=
	{{Wishlist/TOC}}		{{Wishlist/TOC}}
	*Fixing the 74-unit-bug, aka whiteboy bug
	*Fixing of the "Tank Bunker only allows ground locomotor units" issue (it should allow hover locomotor too).		*Fixing of the "Tank Bunker only allows ground locomotor units" issue (it should allow hover locomotor too).
	*Fixing of the "TIBMINExx is hardcoded to spawn xx entry from {{tt\|[Tiberiums]}}" issue, preferably changing xx to an INI-controlled value		*Fixing of the "TIBMINExx is hardcoded to spawn xx entry from {{tt\|[Tiberiums]}}" issue, preferably changing xx to an INI-controlled value
Line 95:		Line 94:
	*Fix the bug where if the crew of a jumpjet unit lands on a structure, it will be invulunerable to any attacks except for mind control.		*Fix the bug where if the crew of a jumpjet unit lands on a structure, it will be invulunerable to any attacks except for mind control.
	*Make a unit wait in frames before it fires, so the SHP vehicle can load up and charge		*Make a unit wait in frames before it fires, so the SHP vehicle can load up and charge
	*Custom Spy Plane / Airstrike superweapons currently can only have 1 AircraftType listed in the SpyPlane tag, multiple types would be preferable.
	*Fixing of EMP and large animations causing a reconnect error in online games		*Fixing of EMP and large animations causing a reconnect error in online games
	*Showing of tech slider and multi engineer options on online game lobbies		*Showing of tech slider and multi engineer options on online game lobbies
	*[[EMEffect\|EMEffect=yes]] does not work on Animation warheads, neither does CellSpread from what I can tell, would it be possible to make those work on animations?		*[[EMEffect\|EMEffect=yes]] does not work on Animation warheads, neither does CellSpread from what I can tell, would it be possible to make those work on animations?
	*Allow buildings to detect cloakable/subterrean units, like in normal RA2		*Allow buildings to detect cloakable/subterrean units, like in normal RA2
	*Allow modify width,color,sound of laser weapon
	*Allow modify width,color,sound of sonic weapon		*Allow modify width,color,sound of sonic weapon
	*Allow anti-air weapon Warhead to use Temporal=yes on air targets. Note that this used to work in RA2.		*Allow anti-air weapon Warhead to use Temporal=yes on air targets. Note that this used to work in RA2.
Line 117:		Line 115:
	*Make the Spawn logic work on buildings, too. Currently the aircrafts are unable to land.		*Make the Spawn logic work on buildings, too. Currently the aircrafts are unable to land.
	*Copy the TechLevel slider and MultiEngineer options to Network and Internet Play, since thex are useless if only availiable in skirmish.		*Copy the TechLevel slider and MultiEngineer options to Network and Internet Play, since thex are useless if only availiable in skirmish.
	*Check for any new codes that have no corespondig save & loadgame code and fix it.

	==Not clear for my brain==		==Not clear for my brain==
Line 124:		Line 121:
	*Fix Debris Logic/Improve it		*Fix Debris Logic/Improve it
	*In game, when you press esc, there should be a OPTIONS button there		*In game, when you press esc, there should be a OPTIONS button there
			*Check for any new codes that have no corespondig save & loadgame code and fix it.

	==Done==		==Done==
			*Allow modify width,color,sound of laser weapon
			*Fixing the 74-unit-bug, aka whiteboy bug
	*Breaking of the 100-unit-limit		*Breaking of the 100-unit-limit
	*Fix the issues with the 'Dropship load screen' and alter its logic so it is possible to specify the units to use as the 'DropShip', preferably any type of unit, not just aircraft.		*Fix the issues with the 'Dropship load screen' and alter its logic so it is possible to specify the units to use as the 'DropShip', preferably any type of unit, not just aircraft.
	*Give Aircraft the ability to fire at other aircraft. And if they already can, how?		*Give Aircraft the ability to fire at other aircraft. And if they already can, how?
	*Repair bugs with DropShip load out screen and change cameo highlight to size of RA2 icons.		*Repair bugs with DropShip load out screen and change cameo highlight to size of RA2 icons.
			*Custom Spy Plane / Airstrike superweapons currently can only have 1 AircraftType listed in the SpyPlane tag, multiple types would be preferable.

en>Bachsau: /* General Bugfixes/Corrections */

2007-05-24T20:01:43Z

General Bugfixes/Corrections

← Older revision		Revision as of 22:01, 24 May 2007
Line 115:		Line 115:
	*Fix the shadow appearing on top of vehicletype with flying locomotor, this would be practical for a flying fortress without infantries parachuting out.		*Fix the shadow appearing on top of vehicletype with flying locomotor, this would be practical for a flying fortress without infantries parachuting out.
	*Fix the AnimToInfantry logic so that animations added to the list after GENDEATH can spawn player-owned infantry, rather than neutral infantry. Since some mods probably use this logic to spawn neutral infantry, this should be optional.		*Fix the AnimToInfantry logic so that animations added to the list after GENDEATH can spawn player-owned infantry, rather than neutral infantry. Since some mods probably use this logic to spawn neutral infantry, this should be optional.
			*Make the Spawn logic work on buildings, too. Currently the aircrafts are unable to land.
			*Copy the TechLevel slider and MultiEngineer options to Network and Internet Play, since thex are useless if only availiable in skirmish.
			*Check for any new codes that have no corespondig save & loadgame code and fix it.

	==Not clear for my brain==		==Not clear for my brain==

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

2007-05-23T10:38:30Z

Reverted edits by 125.26.141.211 (Talk); changed back to last version by Nighthawk200

← Older revision		Revision as of 12:38, 23 May 2007
Line 34:		Line 34:
	=General Bugfixes/Corrections=		=General Bugfixes/Corrections=
	{{Wishlist/TOC}}		{{Wishlist/TOC}}
	*Fix Balloon Hover Unit rotate when it fire range weapon and not fire weapon out when it stand wrong direction with turget.
	*Fixing the 74-unit-bug, aka whiteboy bug		*Fixing the 74-unit-bug, aka whiteboy bug
	*Fixing of the "Tank Bunker only allows ground locomotor units" issue (it should allow hover locomotor too).		*Fixing of the "Tank Bunker only allows ground locomotor units" issue (it should allow hover locomotor too).