Legacy RockPatch Wishlist: Difference between revisions
m improved table code |
|||
Line 1: | Line 1: | ||
__NOTOC__[[Category:RockPatch]]{{RockPatch}} | __NOTOC__[[Category:RockPatch]]{{RockPatch}} | ||
{| align="center" width="98%" style=" | {| align="center" width="98%" style="border: 1px solid #aaaaaa; background:#e5e5e5; border-spacing: 5px;" | ||
!colspan="2"|Introduction | ! colspan="2"|Introduction | ||
|- | |- | ||
| | |width="50%" style="border: 1px solid #aaaaaa; background:#F0F0F0; padding: 5px; vertical-align: top;"|<div align="center">'''What this List is'''</div>You're looking at the community-editable wishlist for [[User:pd|pd]]'s [[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 pd in any other way.'' It just doesn't work that way. If the entire community started IM sessions and bugged pd about features the moment he signed on, he'd soon quit making the patch at all.<br> | If you would like to see a specific feature added to RockPatch, add it at an appropriate place on this list. ''Do not contact pd in any other way.'' It just doesn't work that way. If the entire community started IM sessions and bugged pd about features the moment he signed on, he'd soon quit making the patch at all.<br> | ||
Line 14: | Line 10: | ||
Also note [[RockPatch:Votelist|the Votelist]]. | Also note [[RockPatch:Votelist|the Votelist]]. | ||
| | |width="50%" style="border: 1px solid #aaaaaa; background:#F0F0F0; padding: 5px; vertical-align: top;"|<div align="center">'''What this List is not'''</div> | ||
*This is '''not''' a list of ''demands''. | *This is '''not''' a list of ''demands''. | ||
*These are '''not''' features that ''are'' already implemented. | *These are '''not''' features that ''are'' already implemented. | ||
*This list does '''not''' guarantee the feature ''will'' be implemented. | *This list does '''not''' guarantee the feature ''will'' be implemented. | ||
|- | |- | ||
| | |width="100%" style="border: 1px solid #aaaaaa; background:#F0F0F0; padding: 5px; vertical-align: top;" colspan="2"|<div align="center">'''Where to put your Wish'''</div> | ||
*There are several topical lists, choose the one that fits best. | *There are several topical lists, choose the one that fits best. | ||
*Newer wishes are added to the bottom. | *Newer wishes are added to the bottom. | ||
Line 35: | Line 21: | ||
'''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. | '''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. | ||
|} | |} | ||
Revision as of 04:51, 22 June 2006
Introduction | |
---|---|
What this List is You're looking at the community-editable wishlist for pd's 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 pd in any other way. It just doesn't work that way. If the entire community started IM sessions and bugged pd about features the moment he signed on, he'd soon quit making the patch at all. Also note the Votelist. |
What this List is not
|
Where to put your Wish
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. |
I will choose the easiest for me and the most useful for the community things first.
General Bugfixes/Corrections
Table of Contents |
---|
Note: the following wishlist is now OBSOLETE, stored for archiving purposes only. |
- Breaking of the 100-unit-limit
- 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 "TIBMINExx is hardcoded to spawn xx entry from [Tiberiums]" issue, preferably changing xx to an INI-controlled value
- Fixing of the "AttachedParticleSystem= nullifies Burst=" issue
- Fix various hardcoded YR bugs. See [1] for list.
- Fix Carryall Logic for Hind.
- Fix Debris Logic/Improve it
- Rumor has it that NonVehicle=yes does not actually block Vehicle Hijackers, it just gives a no entry cursor and still lets them hijack...this needs fixing.
- NonVehicle=yes also needs to prevent the Tote action (carryall logic) from grabbing the unit too.
- UseOwnName=true cannot be used on a VehicleType (only InfantryTypes). Any vehicle placed inside an IFV will cause the IFV to have a name of "Rocket IFV" (or Repair/Machine Gun if IFV mode 1/2/3).
- Any way to optimize cloaking code or speed it up
- Fix VehicleThief and Thief logic (currently, you need both to get hijackers to work but the infantry can then enter refineries to no effect)
- Fix the PrismSupportModifier bug (if a [General] section is declared on a map and a value is not defined there, the value is set to infinite or something)
- The use of HoverPad=yes causes an Internal Error if the AI uses a Nuke or Weather Storm. This is a pain because the HoverPad=yes can be used to make hover units land on service depots and, better yet, allows an airpad to come with a free aircraft - but we can't use it because of the damned IE!
Not so much of a problem, see discussion. - having 2 PKT files makes some maps get listed ingame twice. can you fix this?
- Fix adding new [BuildingTypes] breaking single player campains. See this link for a better description: [2]}}
- Fix code so you can build all units of a BuildLimit >1 in a row
(right now, if you have BuildLimit=10, for example, you can only build 9, something else, and then the last one) - The 'sell unit' function can be resurrected using a super weapon. However, you can sell any docked unit, including Tank-Bunkered units. Selling a Tank-Bunkered unit leaves the Tank Bunker walls up, rendering it useless. Selling the Tank Bunker then causes an Internal Error. Now, we don't want 'sell unit' forcibly resurrected, however it would be nice if either A) Tank-Bunkered units couldn't be sold (preferred choice), or B) Tank-Bunkers' walls retracted and the Bunker continued to work normally (second choice), or C) selling a 'broken' Tank Bunker did not cause an Internal Error.
- HarvestersPerRefinery - Make this usable
- A rules option so that units will consider in their threat scan neutral player-owned units that have a weapon or non-zero threat rating. It's so annoying if your mod has something that generates neutral infantry opponents that your units and, more importantly, the AI completely ignores.
- fix the "AI doesn't deploy MCVs with new locomotors set on them" bug(IE hover, jumpjet, subter...)
- Fix the Droppod Locomoter
- Force refresh when returning from game-mode menu to apply changes to the menu made by a game mode, such as money range, or starting units range.
- Tote action (carryall logic) and Heal action (negative damage weapon given to an infantry) need to point to sequences in mouse.sha rather than to the same single frame.
- If an AnimToInfantry call occurs for an animation that is positioned in a place where no infantry can land then the call will be suspended (potentially for the remainder of the game). This is believed by some to cause a general game slow down. Either way, it doesn't look nice. Perhaps the call could be cancelled if there is no space...
- WeaponXTurretLocked=true "bug" when unit turns 180 the turret may spin in the opposed direction instead of following with voxle nit’s direction.
- AccelerationFactor=0.01; This has a problem with voxel scales.
- IsTrain=yes, MovementRestrictedTo=Railroad one of these has the control for the train movement and the turn is 135 or 90 but the train should only turn 45 to prevent jumping tracks.
- in RA2 you can place a PKT with a map/maps in a mix, and rename it to an MMX and the map will work, like a map pack, however, the YR equevalant YRO(as documented by deezire) files don't actually work. my idea is to try and make them work!
- Improve the havester logic so it (the harvester) cannot go to an enemy base (and then get killed) when there is an Ore on it (enemy base)
- Factory Plant Settings reduce Solyent values to prevent income generation explotation. (If implemented, this should definitely be optional - I myself reduce soylents manually so I don't want them reduced further by owning an Industrial Plant.) By default vehicle refund should be 50%. Basically if you make a vehicle 25% cheaper, you should only get 50% of its value back
- Code the Hospital=yes and Machine Shop tag so that owning multiple buildings does generate an undocumented cumulative effect.
- The game reads langmd.mix > missionsmd.pkt and uses it to determine which gamemodes the stock maps are available in. Editing this file and dropping it in the directory causes random bugs and duplicate entries in the map list. If possible, add a rules tag pointing to a filename to read instead of missionsmd.pkt (de-hardcode the reference, like the IsIFV= and similar new tags do). Like [General]-->PKTFile= .
- A fix for the ridiculous slowdown caused by having an extra CD drive or too-good hardware. In my case, my P4 3.0GHz and GeForce 5900 are (my the sound of it) the two pieces of hardware that stop me running YR...
- Fix the currently unworking CloakStop= tag
- Fix it so that your computer doesn't have to be in 16-bit colour for the windowed mode (from adding -WIN to a shortcut) to work, i.e. it supports 32-bit colour too.
- Make Fighters/Aircraft Cloakable with their own cloaking unit and can dogfight, ATA without Jumpjet= or altering the height-fongsaunder
- Allow aircrafts/copters to transport vehicles correctly, not by setting a ridiculous ammount of transportable units. (ex: you'd have to set the Hind and the NightHawk to have alot of pips, about ten, just so one tank could fit in it)
- Allow rotors to work with Aircraft units (not just copters) correctly without any bug.
- Fix the error when having a gate that slides down (TS style) instead of opening sideways which made the gate appear OVER a unit passing on the downed gate.
- Fix it so that when you add a superweapon upgrade to a building that has a superweapon, it overwrites the previous superweapon, instead of just adding it as a new superweapon (perhaps make it an optional tag)
- Make PrismType= support more than one
- Bring back mine layer codes
- Fix voxel size units that is bigger than a tank. Eg.: Like if you have a mech or walker unit that is bigger than a 1x1 square.Wish voxel size can be user define like VoxelSize=2x2,like what you can do for buildings.
- Enable the Robotic Centre to accept more than 1 robotic units and if it is destroyed and rebuilt,the robotic units that are more than the first one can be shaken out from their shut down mode. This should also fix a problem with mods that have Vehicle Hijackers and more than 1 type of Robot Tank.