Upgrade SW with more possibilities

Bug #895126 reported by Bug Importer
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ares
Invalid
Wishlist
Unassigned

Bug Description

First, I wish a copy of NPatchs upgrade SW.

[UpgradeSpecial]
UpgradeType=ARMOR,CLOAK,SPEED,FIREPOWER ; Upgrade type: can be one or more constants
UpgradeRadius=3 ; Upgrade radius in cells
UpgradeValue=2.0 ; Value, which depends from upgrade type

And now something else to:
Add new tags to the unit, any tag that the TechnoType accpect.
Exempel:
[UpgradeSpecial]
Type=Upgrade
ImmuneToRadiation=yes

UpgradeOnVehicles=yes
UpgradeOnInfantry=no
UpgradeOnBuildings=no
UpgradeOnAircrafts=no

This means:
-You can only upgrade on VehicleTypes
-When you upgrade the unit(lets say HTNK), the HTNK will become immune to radiation.
-Replace tags should also work.
-It should take a list of tags, not just one.

Comment idea please.

Revision history for this message
Electro (owlberteinstein-b) wrote :

Severity -> feature. RTFM.

Revision history for this message
Marshall (m-edward) wrote :

I believe making it accept any TechnoType tag would be a lot of work. A better solution might be to have a list of replacement TechnoTypes. Eg:
Upgrade.Suffix=UP1
Then HTNK upgrades to HTNKUP1
TELE upgrades to TELEUP1
Upgrade.ForbiddenUnits=
Upgrade.RequiredUnits=

However even that is a lot of work and I don't see it getting a lot of use.

Revision history for this message
DCoder DCoder (dcoder1337) wrote :

It would involve work, but not an extraordinary amount of it. Marshall's way is not that much easier from my point of view, though the question of usefulness still stands.

And why can't you people file ONE request per issue so it can be tracked properly?

Revision history for this message
Bug Importer (bug-importer) wrote :

Speaking of Upgrade SW, it would be a good idea to add a duration=x tag, so the Upgrade SW could have a temporary effect.
So for example:
Duration=60 ;Effects last 60 seconds
and
Duration=-1 :Effects are permanent

Revision history for this message
Renegade (renegade) wrote :

Closing as suspended since feedback has been requested and there was no activity on the issue for more than four weeks.

Issue will be of lower priority if re-opened.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.