ModEnc² - User contributions [en]

Legacy RockPatch Wishlist

2006-11-16T05:48:10Z

61.163.231.230: /* General Bugfixes/Corrections */

__NOTOC__[[Category:RockPatch]]{{RockPatch}}

{| align="center" width="98%" class="table_parted"
!colspan="2"|Introduction
|-
|width="50%"|<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>
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.)

Also note [[RockPatch:Votelist|the Votelist]].
|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.
|}

{{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>
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".}}

=General Bugfixes/Corrections=
{{Wishlist/TOC}}
*allow anti-air weapon Warhead can use Temporal=yes to anti air
*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 {{tt|[Tiberiums]}}" issue, preferably changing xx to an INI-controlled value
*Fixing of the "{{tt|AttachedParticleSystem=}} nullifies {{tt|Burst=}}" issue
*Fix various hardcoded YR bugs. See {{tt|[http://marshall.cannis.net/ump/index.htm#bugs]}} for list.
*Fix Carryall Logic for Hind.
*Fix Debris Logic/Improve it
*Rumor has it that {{tt|NonVehicle=yes}} does not actually block Vehicle Hijackers, it just gives a no entry cursor and still lets them hijack...this needs fixing.
*{{tt|NonVehicle=yes}} also needs to prevent the Tote action (carryall logic) from grabbing the unit too.
*{{tt|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 {{tt|[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 {{tt|HoverPad=yes}} causes an Internal Error if the AI uses a Nuke or Weather Storm. This is a pain because the {{tt|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!<br>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 {{tt|[BuildingTypes]}} breaking single player campains. See this link for a better description: [http://www.cannis.net/tutorials/ra2yr_nobreak_yrmissions1/]}}
*Fix code so you can build all units of a BuildLimit >1 in a row<br>(right now, if you have {{tt|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...
*{{tt|WeaponXTurretLocked=true}} "bug" when unit turns 180 the turret may spin in the opposed direction instead of following with voxle nit’s direction.
*{{tt|AccelerationFactor=0.01}}; This has a problem with voxel scales.
*{{tt|IsTrain=yes}}, {{tt|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 {{tt|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 {{tt|IsIFV=}} and similar new tags do). Like {{tt|[General]}}-->{{tt|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 {{tt|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 {{tt|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 {{tt|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 {{tt|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.
*Enable a Psi-Warning animation for the intended target of any superweapon, not just the nuke and its clones.
*Make a unit ELITE with the armory should coast money, like EliteInfantryCoast=3000, armory is to cheaty right now
*Make so a [vehicletype] can spawn an othe [vehicletype]

*<s>Make so a unit only can built by a specefic warfactory, like BuildOnly=HTNK(on the new warfactory) This is good so big tanks can spawn on a big factory</s> (see the [[RockPatch_talk:Wishlist#Re:_BuildOnly|talk page]])
*Make weapon that, when you fire a unit, you get extra hp, like ih Damage is 100, thats mean you take 100hp from them and add 100hp to you
*BUG: Flipping other tanks... If a tank is to heavy and cant be flipped, the heavy tank get permanetly emp and the tank with flipper weapon cant flipp other unit the heavy tank is dead(not rp bug)
*Fix so AI dont build more unit than the buildlimit
*make the tunnel system works(like generals that GLA uses)
*In game,when you press esc, there should be a OPTIONS button there
*Make a magnetic push weapon yhat pushes other vehicles away
*Subterrainean units that have occupants that can fire out of the unit like the Battle Fortress can fire at targets even when traveling underground.

*Fix the dam hardcoded stolentech
*Make so Cyborg=yes can get EMP and is allowed to iron curtian protection and also make the make so iron curtians warhead is in rules.ini
*Enable the Auto-Deploy logic to work with human players. Currently it only works with the AI, human-controlled units are unable to use Auto-Deploy. This was apparantly either unfinished or desupported according to the ini files.
*Fix the harcdoed CourseLockDuration= and Level= in projectiles, so the unit can fire a bullet that goes in a strange line
*Fix the Mirage Tank logic so it can work with the turret logic
*allow modify width,color,sound of sonic weapon
*Fix the tankbunker bug in which if it will not be sold if it's a deployed unit (like a MCV), if you choose to sale it it'll just undeploy.
*Is it possible for a unit to switch weapon when the targeted unit gets in range? So it wouldn't be sort of strange for units with a weapon with CellSpread=.5 or more kill themselves or has to back off with the MinimumRange= logic.
*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
*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
*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?
*Allow buildings to detect cloakable/subterrean units, like in normal RA2
*allow modify width,color,sound of laser weapon
==Done==
*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.
*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.

Legacy RockPatch Wishlist

2006-09-13T11:32:43Z

61.163.231.230: /* General Bugfixes/Corrections */

__NOTOC__[[Category:RockPatch]]{{RockPatch}}

{| align="center" width="98%" class="table_parted"
!colspan="2"|Introduction
|-
|width="50%"|<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>
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.)

Also note [[RockPatch:Votelist|the Votelist]].
|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.
|}

{{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>
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".}}

=General Bugfixes/Corrections=
{{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 "TIBMINExx is hardcoded to spawn xx entry from {{tt|[Tiberiums]}}" issue, preferably changing xx to an INI-controlled value
*Fixing of the "{{tt|AttachedParticleSystem=}} nullifies {{tt|Burst=}}" issue
*Fix various hardcoded YR bugs. See {{tt|[http://marshall.cannis.net/ump/index.htm#bugs]}} for list.
*Fix Carryall Logic for Hind.
*Fix Debris Logic/Improve it
*Rumor has it that {{tt|NonVehicle=yes}} does not actually block Vehicle Hijackers, it just gives a no entry cursor and still lets them hijack...this needs fixing.
*{{tt|NonVehicle=yes}} also needs to prevent the Tote action (carryall logic) from grabbing the unit too.
*{{tt|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 {{tt|[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 {{tt|HoverPad=yes}} causes an Internal Error if the AI uses a Nuke or Weather Storm. This is a pain because the {{tt|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!<br>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 {{tt|[BuildingTypes]}} breaking single player campains. See this link for a better description: [http://www.cannis.net/tutorials/ra2yr_nobreak_yrmissions1/]}}
*Fix code so you can build all units of a BuildLimit >1 in a row<br>(right now, if you have {{tt|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...
*{{tt|WeaponXTurretLocked=true}} "bug" when unit turns 180 the turret may spin in the opposed direction instead of following with voxle nit’s direction.
*{{tt|AccelerationFactor=0.01}}; This has a problem with voxel scales.
*{{tt|IsTrain=yes}}, {{tt|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 {{tt|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 {{tt|IsIFV=}} and similar new tags do). Like {{tt|[General]}}-->{{tt|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 {{tt|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 {{tt|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 {{tt|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 {{tt|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.
*Enable a Psi-Warning animation for the intended target of any superweapon, not just the nuke and its clones.
*Make a unit ELITE with the armory should coast money, like EliteInfantryCoast=3000, armory is to cheaty right now
*Make so a [vehicletype] can spawn an othe [vehicletype]
*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.
*<s>Make so a unit only can built by a specefic warfactory, like BuildOnly=HTNK(on the new warfactory) This is good so big tanks can spawn on a big factory</s> (see the [[RockPatch_talk:Wishlist#Re:_BuildOnly|talk page]])
*Make weapon that, when you fire a unit, you get extra hp, like ih Damage is 100, thats mean you take 100hp from them and add 100hp to you
*BUG: Flipping other tanks... If a tank is to heavy and cant be flipped, the heavy tank get permanetly emp and the tank with flipper weapon cant flipp other unit the heavy tank is dead(not rp bug)
*Fix so AI dont build more unit than the buildlimit
*make the tunnel system works(like generals that GLA uses)
*In game,when you press esc, there should be a OPTIONS button there
*Make a magnetic push weapon yhat pushes other vehicles away
*Subterrainean units that have occupants that can fire out of the unit like the Battle Fortress can fire at targets even when traveling underground.
*Repair bugs with DropShip load out screen and change cameo highlight to size of RA2 icons.
*Fix the dam hardcoded stolentech
*Make so Cyborg=yes can get EMP and is allowed to iron curtian protection and also make the make so iron curtians warhead is in rules.ini
*Give Aircraft the ability to fire at other aircraft. And if they already can, how?
*Enable the Auto-Deploy logic to work with human players. Currently it only works with the AI, human-controlled units are unable to use Auto-Deploy. This was apparantly either unfinished or desupported according to the ini files.
*Fix the harcdoed CourseLockDuration= and Level= in projectiles, so the unit can fire a bullet that goes in a strange line
*Fix the Mirage Tank logic so it can work with the turret logic
*allow modify width,color,sound of laser weapon
*allow modify width,color,sound of sonic weapon
==Done==
*Breaking of the 100-unit-limit

Legacy RockPatch Wishlist

2006-09-13T11:30:27Z

61.163.231.230: /* Done */

__NOTOC__[[Category:RockPatch]]{{RockPatch}}

{| align="center" width="98%" class="table_parted"
!colspan="2"|Introduction
|-
|width="50%"|<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>
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.)

Also note [[RockPatch:Votelist|the Votelist]].
|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.
|}

{{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>
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".}}

=General Bugfixes/Corrections=
{{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 "TIBMINExx is hardcoded to spawn xx entry from {{tt|[Tiberiums]}}" issue, preferably changing xx to an INI-controlled value
*Fixing of the "{{tt|AttachedParticleSystem=}} nullifies {{tt|Burst=}}" issue
*Fix various hardcoded YR bugs. See {{tt|[http://marshall.cannis.net/ump/index.htm#bugs]}} for list.
*Fix Carryall Logic for Hind.
*Fix Debris Logic/Improve it
*Rumor has it that {{tt|NonVehicle=yes}} does not actually block Vehicle Hijackers, it just gives a no entry cursor and still lets them hijack...this needs fixing.
*{{tt|NonVehicle=yes}} also needs to prevent the Tote action (carryall logic) from grabbing the unit too.
*{{tt|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 {{tt|[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 {{tt|HoverPad=yes}} causes an Internal Error if the AI uses a Nuke or Weather Storm. This is a pain because the {{tt|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!<br>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 {{tt|[BuildingTypes]}} breaking single player campains. See this link for a better description: [http://www.cannis.net/tutorials/ra2yr_nobreak_yrmissions1/]}}
*Fix code so you can build all units of a BuildLimit >1 in a row<br>(right now, if you have {{tt|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...
*{{tt|WeaponXTurretLocked=true}} "bug" when unit turns 180 the turret may spin in the opposed direction instead of following with voxle nit’s direction.
*{{tt|AccelerationFactor=0.01}}; This has a problem with voxel scales.
*{{tt|IsTrain=yes}}, {{tt|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 {{tt|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 {{tt|IsIFV=}} and similar new tags do). Like {{tt|[General]}}-->{{tt|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 {{tt|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 {{tt|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 {{tt|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 {{tt|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.
*Enable a Psi-Warning animation for the intended target of any superweapon, not just the nuke and its clones.
*Make a unit ELITE with the armory should coast money, like EliteInfantryCoast=3000, armory is to cheaty right now
*Make so a [vehicletype] can spawn an othe [vehicletype]
*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.
*<s>Make so a unit only can built by a specefic warfactory, like BuildOnly=HTNK(on the new warfactory) This is good so big tanks can spawn on a big factory</s> (see the [[RockPatch_talk:Wishlist#Re:_BuildOnly|talk page]])
*Make weapon that, when you fire a unit, you get extra hp, like ih Damage is 100, thats mean you take 100hp from them and add 100hp to you
*BUG: Flipping other tanks... If a tank is to heavy and cant be flipped, the heavy tank get permanetly emp and the tank with flipper weapon cant flipp other unit the heavy tank is dead(not rp bug)
*Fix so AI dont build more unit than the buildlimit
*make the tunnel system works(like generals that GLA uses)
*In game,when you press esc, there should be a OPTIONS button there
*Make a magnetic push weapon yhat pushes other vehicles away
*Subterrainean units that have occupants that can fire out of the unit like the Battle Fortress can fire at targets even when traveling underground.
*Repair bugs with DropShip load out screen and change cameo highlight to size of RA2 icons.
*Fix the dam hardcoded stolentech
*Make so Cyborg=yes can get EMP and is allowed to iron curtian protection and also make the make so iron curtians warhead is in rules.ini
*Give Aircraft the ability to fire at other aircraft. And if they already can, how?
*Enable the Auto-Deploy logic to work with human players. Currently it only works with the AI, human-controlled units are unable to use Auto-Deploy. This was apparantly either unfinished or desupported according to the ini files.
*Fix the harcdoed CourseLockDuration= and Level= in projectiles, so the unit can fire a bullet that goes in a strange line
*Fix the Mirage Tank logic so it can work with the turret logic

==Done==
*Breaking of the 100-unit-limit
allow modify width,color,sound of laser weapon
allow modify width,color,sound of sonic weapon

Legacy RockPatch Wishlist/Page 5

2006-05-20T12:43:17Z

61.163.231.230:

::::''Please use [[Talk:RockPatch/Wishlist|the main Wishlist Talkpage]] for comments, not this page's.

{{Wishlist/TOC}}

=Weapons Related=
*More Armor types
*Moving stuff like "OpenToppedRange/Damage/UrbanCombatRange/" and similar from [General] to each unit, and using the [General] entry only as defaults (Like [Jumpjet controls] is now)
*More V3 style missiles
*Drainlogic (DrainWeapon=yes) to work with ranged weapons.
*Temporal weapons to work with cellspread.
*If possible a tag to have permanent mindcontrol like with Psychic Dominator.
*Engineers can't have working conventional weapons. Would be nice if they could. Vehicle Thieves have to force-move on their hijack target if they are an Engineer as well.
*Allow unit to fire two weapons at the same time.
*Warheads other than Fire3 being able to be applied to animations properly
*More flexible Gatling logic
*Third Weapon if possable
*2-5 weapons in one click or in the Primary= or Secondary=
*New warhead immunities.(Just like ImmuneToPoison=yes/Poison=yes). For example: ImmuneToNewImmunity1=yes/NewImmunity1=yes
*Ability to player control which weapon to attack with (Like in Generals)
*Allow the use of less or more steps for the gattling logic. More or less weapons ...
*Have an AltInfDeath= entry on warheads that specifies the death anim to play when the infantry has NotHuman=yes. Currently such an infantry (mainly the animals) always dies with InfDeath=1 regardless of weapon that killed them.
*NextWeapon= tag that fires a weapon when the attack mission of the caller is finished
*New armor types to be declared as DefaultValues=<armor1 default verses>,<armor2 default verses> that would be called with ArmorxxVersus= and would use the default value if this is omitted to allow old rulesmd compatibility
*Weapontypes for immunities etc., declared with perhaps bonus stuff and called by WeaponType=xyz
*Tag to make the unit/building immune to everything except the listed WeaponTypes
*ApplyTag= on warhead to create ultimate possibilities for weapons to work like IsLocomotor=, could be used to slow units down, to make them crushable and basically change everything in their coding
*Completely new superweapon system to use the reusable SuperType= to contain both the earlier Action and Type settings, for instance the Nuke SuperType could make the weapon behave like a nuke, with appropriate coding like modifyable payload weapon, original sidebar and chargetime settings etc.
*Weapons to allow "stacking" on their 'damage=nn' tag, so that they could do variable (or random) damage. The game chooses one at random from the list each time the situation calls it to. For example, 'Damage=0,0,0,30,100' on a weapon would mean a 60% chance of a miss, 20% of a glancing hit, and 20% of a penetrating hit every time the weapon strikes a target. This would allow for many mods to add an element of random chance to combat, giving players the opportunity to take a risk, and also meaning that equal matchups don't have to be annihilation of both sides every time.
*Implement new actions (including new mouse cursors)
*Copy OmniFire logic to be definable for individual weapons instead of units.
*MultiFire to allow multiple targets for weapons other than Mind Control.
*PenetratesBuilding=yes/no, same as penetrates bunker but deals damage out between occupants of civilian buildings (Tratos)
*An area effect superweapon that allows you to promote units within the radius by one stage (like the crate effect) (Tratos)
*Is it possible to create a superweapon action that can be reused, allowing multiple buildings to be built to give multiple copies of the same superweapon (i.e. more radar facilities=more spyplane superweapons available).
*SW that have range from the firing building (like the EMP had range restrictions in TS)
*I saw no area for this, but get some more mpmodesmd.ini editing. Like, new map filters like FILT001 and allow the new filters to be controlled in the rules and by making qualifications like Players= and Terrain=, you know, stuff like that.
*Re-enable the Charges= tag, it says it was disabled in favour of an animation controlled tag. This is annoying for those that can't do art coding very well, I think this would let the weapon charge w/o an anim, you could even add a ChargeReport= tag or something like that to control the charging sound. [Nighthawk200]
*Some Superweapon things:
*Enable a customisable Chronosphere, e.g. you can specify in rulesmd what you want it to chrono (e.g. infantry, vehicles, aircraft, naval units)
*Enable a customisable Iron Curtain, e.g. same as above only Iron Curtain
*Let any superweapon have an iron curtain effect (invulnerability)
*Enable the customisable Chronosphere (if made) to be able to let the modder specify whether it can chrono iron curtained units.
*Enable sort of a 'Chrono Curtain' superweapon, e.g. chronoshifts then iron curtains when chronoshift complete (may be quite hard) [all suggested by Nighthawk200]
*Or (might be easier) let the modder specify another superweapon to fire on the target spot after one has fired, e.g. FireNext=IronCurtainSpecial [Nighthawk200]
*Allow Nuke, Genetic Mutating and Wheater Control SW clones. (Alex05)
*New Laser Weapon(allow define color,degree,width),New sonic Weapon,and "PrismType" can support more building [zhaihs]
* MAKE FIRING SW SUPPORT TURRETS AND RANGE
*Psychic Dominator can effect and control building,use 2 warhead,now DominatorWH only killed unit[zhaihs]
*Different coloured Magna Beams [Nighthawk200]
{{RockPatch}}

Legacy RockPatch Wishlist/Page 5

2006-05-15T06:58:57Z

61.163.231.230:

Legacy RockPatch Wishlist/Page 5

2006-05-15T06:58:11Z

61.163.231.230:

::::''Please use [[Talk:RockPatch/Wishlist|the main Wishlist Talkpage]] for comments, not this page's.

{{Wishlist/TOC}}

=Weapons Related=
*More Armor types
*Moving stuff like "OpenToppedRange/Damage/UrbanCombatRange/" and similar from [General] to each unit, and using the [General] entry only as defaults (Like [Jumpjet controls] is now)
*More V3 style missiles
*Drainlogic (DrainWeapon=yes) to work with ranged weapons.
*Temporal weapons to work with cellspread.
*If possible a tag to have permanent mindcontrol like with Psychic Dominator.
*Engineers can't have working conventional weapons. Would be nice if they could. Vehicle Thieves have to force-move on their hijack target if they are an Engineer as well.
*Allow unit to fire two weapons at the same time.
*Warheads other than Fire3 being able to be applied to animations properly
*More flexible Gatling logic
*Third Weapon if possable
*2-5 weapons in one click or in the Primary= or Secondary=
*New warhead immunities.(Just like ImmuneToPoison=yes/Poison=yes). For example: ImmuneToNewImmunity1=yes/NewImmunity1=yes
*Ability to player control which weapon to attack with (Like in Generals)
*Allow the use of less or more steps for the gattling logic. More or less weapons ...
*Have an AltInfDeath= entry on warheads that specifies the death anim to play when the infantry has NotHuman=yes. Currently such an infantry (mainly the animals) always dies with InfDeath=1 regardless of weapon that killed them.
*NextWeapon= tag that fires a weapon when the attack mission of the caller is finished
*New armor types to be declared as DefaultValues=<armor1 default verses>,<armor2 default verses> that would be called with ArmorxxVersus= and would use the default value if this is omitted to allow old rulesmd compatibility
*Weapontypes for immunities etc., declared with perhaps bonus stuff and called by WeaponType=xyz
*Tag to make the unit/building immune to everything except the listed WeaponTypes
*ApplyTag= on warhead to create ultimate possibilities for weapons to work like IsLocomotor=, could be used to slow units down, to make them crushable and basically change everything in their coding
*Completely new superweapon system to use the reusable SuperType= to contain both the earlier Action and Type settings, for instance the Nuke SuperType could make the weapon behave like a nuke, with appropriate coding like modifyable payload weapon, original sidebar and chargetime settings etc.
*Weapons to allow "stacking" on their 'damage=nn' tag, so that they could do variable (or random) damage. The game chooses one at random from the list each time the situation calls it to. For example, 'Damage=0,0,0,30,100' on a weapon would mean a 60% chance of a miss, 20% of a glancing hit, and 20% of a penetrating hit every time the weapon strikes a target. This would allow for many mods to add an element of random chance to combat, giving players the opportunity to take a risk, and also meaning that equal matchups don't have to be annihilation of both sides every time.
*Implement new actions (including new mouse cursors)
*Copy OmniFire logic to be definable for individual weapons instead of units.
*MultiFire to allow multiple targets for weapons other than Mind Control.
*PenetratesBuilding=yes/no, same as penetrates bunker but deals damage out between occupants of civilian buildings (Tratos)
*An area effect superweapon that allows you to promote units within the radius by one stage (like the crate effect) (Tratos)
*Is it possible to create a superweapon action that can be reused, allowing multiple buildings to be built to give multiple copies of the same superweapon (i.e. more radar facilities=more spyplane superweapons available).
*SW that have range from the firing building (like the EMP had range restrictions in TS)
*I saw no area for this, but get some more mpmodesmd.ini editing. Like, new map filters like FILT001 and allow the new filters to be controlled in the rules and by making qualifications like Players= and Terrain=, you know, stuff like that.
*Re-enable the Charges= tag, it says it was disabled in favour of an animation controlled tag. This is annoying for those that can't do art coding very well, I think this would let the weapon charge w/o an anim, you could even add a ChargeReport= tag or something like that to control the charging sound. [Nighthawk200]
*Some Superweapon things:
*Enable a customisable Chronosphere, e.g. you can specify in rulesmd what you want it to chrono (e.g. infantry, vehicles, aircraft, naval units)
*Enable a customisable Iron Curtain, e.g. same as above only Iron Curtain
*Let any superweapon have an iron curtain effect (invulnerability)
*Enable the customisable Chronosphere (if made) to be able to let the modder specify whether it can chrono iron curtained units.
*Enable sort of a 'Chrono Curtain' superweapon, e.g. chronoshifts then iron curtains when chronoshift complete (may be quite hard) [all suggested by Nighthawk200]
*Or (might be easier) let the modder specify another superweapon to fire on the target spot after one has fired, e.g. FireNext=IronCurtainSpecial [Nighthawk200]
*Allow Nuke, Genetic Mutating and Wheater Control SW clones. (Alex05)
*New Laser Weapon(allow define color,degree,width),New sonic Weapon,and "PrismType" can support more building [zhaihs]
* MAKE FIRING SW SUPPORT TURRETS AND RANGE
{{RockPatch}}
*Psychic Dominator can effect building [zhaihs]

Legacy RockPatch Wishlist/Page 5

2006-04-17T06:42:52Z

61.163.231.230:

Legacy RockPatch Wishlist/Page 5

2006-04-17T06:30:48Z

61.163.231.230:

::::''Please use [[Talk:RockPatch/Wishlist|the main Wishlist Talkpage]] for comments, not this page's.

{{Wishlist/TOC}}

=Weapons Related=
*More Armor types
*Moving stuff like "OpenToppedRange/Damage/UrbanCombatRange/" and similar from [General] to each unit, and using the [General] entry only as defaults (Like [Jumpjet controls] is now)
*More V3 style missiles
*Drainlogic (DrainWeapon=yes) to work with ranged weapons.
*Temporal weapons to work with cellspread.
*If possible a tag to have permanent mindcontrol like with Psychic Dominator.
*Engineers can't have working conventional weapons. Would be nice if they could. Vehicle Thieves have to force-move on their hijack target if they are an Engineer as well.
*Allow unit to fire two weapons at the same time.
*Warheads other than Fire3 being able to be applied to animations properly
*More flexible Gatling logic
*Third Weapon if possable
*2-5 weapons in one click or in the Primary= or Secondary=
*New warhead immunities.(Just like ImmuneToPoison=yes/Poison=yes). For example: ImmuneToNewImmunity1=yes/NewImmunity1=yes
*Ability to player control which weapon to attack with (Like in Generals)
*Allow the use of less or more steps for the gattling logic. More or less weapons ...
*Have an AltInfDeath= entry on warheads that specifies the death anim to play when the infantry has NotHuman=yes. Currently such an infantry (mainly the animals) always dies with InfDeath=1 regardless of weapon that killed them.
*NextWeapon= tag that fires a weapon when the attack mission of the caller is finished
*New armor types to be declared as DefaultValues=<armor1 default verses>,<armor2 default verses> that would be called with ArmorxxVersus= and would use the default value if this is omitted to allow old rulesmd compatibility
*Weapontypes for immunities etc., declared with perhaps bonus stuff and called by WeaponType=xyz
*Tag to make the unit/building immune to everything except the listed WeaponTypes
*ApplyTag= on warhead to create ultimate possibilities for weapons to work like IsLocomotor=, could be used to slow units down, to make them crushable and basically change everything in their coding
*Completely new superweapon system to use the reusable SuperType= to contain both the earlier Action and Type settings, for instance the Nuke SuperType could make the weapon behave like a nuke, with appropriate coding like modifyable payload weapon, original sidebar and chargetime settings etc.
*Weapons to allow "stacking" on their 'damage=nn' tag, so that they could do variable (or random) damage. The game chooses one at random from the list each time the situation calls it to. For example, 'Damage=0,0,0,30,100' on a weapon would mean a 60% chance of a miss, 20% of a glancing hit, and 20% of a penetrating hit every time the weapon strikes a target. This would allow for many mods to add an element of random chance to combat, giving players the opportunity to take a risk, and also meaning that equal matchups don't have to be annihilation of both sides every time.
*Implement new actions (including new mouse cursors)
*Copy OmniFire logic to be definable for individual weapons instead of units.
*MultiFire to allow multiple targets for weapons other than Mind Control.
*PenetratesBuilding=yes/no, same as penetrates bunker but deals damage out between occupants of civilian buildings (Tratos)
*An area effect superweapon that allows you to promote units within the radius by one stage (like the crate effect) (Tratos)
*Is it possible to create a superweapon action that can be reused, allowing multiple buildings to be built to give multiple copies of the same superweapon (i.e. more radar facilities=more spyplane superweapons available).
*SW that have range from the firing building (like the EMP had range restrictions in TS)
*I saw no area for this, but get some more mpmodesmd.ini editing. Like, new map filters like FILT001 and allow the new filters to be controlled in the rules and by making qualifications like Players= and Terrain=, you know, stuff like that.
*Re-enable the Charges= tag, it says it was disabled in favour of an animation controlled tag. This is annoying for those that can't do art coding very well, I think this would let the weapon charge w/o an anim, you could even add a ChargeReport= tag or something like that to control the charging sound. [Nighthawk200]
*Some Superweapon things:
*Enable a customisable Chronosphere, e.g. you can specify in rulesmd what you want it to chrono (e.g. infantry, vehicles, aircraft, naval units)
*Enable a customisable Iron Curtain, e.g. same as above only Iron Curtain
*Let any superweapon have an iron curtain effect (invulnerability)
*Enable the customisable Chronosphere (if made) to be able to let the modder specify whether it can chrono iron curtained units.
*Enable sort of a 'Chrono Curtain' superweapon, e.g. chronoshifts then iron curtains when chronoshift complete (may be quite hard) [all suggested by Nighthawk200]
*Or (might be easier) let the modder specify another superweapon to fire on the target spot after one has fired, e.g. FireNext=IronCurtainSpecial [Nighthawk200]
*Allow Nuke, Genetic Mutating and Wheater Control SW clones. (Alex05)
*New Laser Weapon,New sonic Weapon,and "PrismType" can support more building [zhaihs]
{{RockPatch}}