Ares

Implement BuildLimit.RemovesCameo =

Bug #895098 reported by DCoder DCoder
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
Incomplete
Medium
Unassigned
Ares outdated-1.0 "Gold"

Bug Description

BuildLimit.RemovesCameo = y/n
When set, the cameo will be _removed_ from the sidebar when limit is reached, and _restored_ when it can be built again, as opposed to simply _graying_ it out. Applications include technology upgrades and other one-at-a-time devices that are mostly clutter.

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

Postponing for the future.

Revision history for this message
Black Temple Gaurdian (black-temple-gaurdian) wrote :

Not for nothing but can't this be done with just a negative build limit (the only problem there being you can't queue all of them, say it was build limit -5 you could queue 4 and only then build the final one)?

Revision history for this message
Professor_Tesla (professor-tesla) wrote :

It can be done that way, but then you can never get the cameo back once the build limit is reached. On the other hand, if it were implemented as described in the original post, it might become a new cause of the NCO bug.

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

I remember a NegativePrerequisite= flag. was is just available in rockpatch?

this should do, i think

Revision history for this message
WoRmINaToR (worminator) wrote :

Actually I agree with anon, Prerequisite.Negative= set to itself should do just fine for this usage case, would it not?

Revision history for this message
Mustafa Alperen SEKİ (mustafaoyunda37) wrote :

In fact Prerequisite.Negative=BUILDINGITSELF is same as something like BuildLimit.RemovesCameo=1. But more can't be achived with that.

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

Other bug subscribers

Remote bug watches

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