Summary: Building obsolescense requirement vector
Submitted by: cazfi
Submitted on: Sat 15 Jun 2013 08:20:27 AM EEST
Priority: 5 - Normal
Status: Ready For Test
Assigned to: None
Discussion Lock: Any
Planned Release: 2.6.0
Make building "obsolete_by" vector of requirements. If any of these
requirements is fulfilled, building is obsolete.
The original use-case I made this for could be achieved with much less
flexible solution, but I see no reason not to go all the way to full
requirement vector. Old code with single tech requirement had "range" behavior
hardcoded so that for Great Wonders anybody having the tech obsoleted the
wonder (range "World"), and for Small Wonders and normal buildings it was
owner having the tech (range "Player"). I wanted to have specific wonder as
Small Wonder so that all players could have their own, but it getting
obsoleted globally when first player gets relevant tech.
All supplied rulesets should give identical behavior to old. This includes the
fact that wonders in multiplayer ruleset, where they all are Small Wonders, do
not get globally obsoleted. I leave it to future tickets if that should be
changed or not.
Date: Sat 15 Jun 2013 08:20:27 AM EEST Name: ObsoleteReqVec.patch.bz2 Size:
11kB By: cazfi
Reply to this item at:
Message sent via/by Gna!
Freeciv-dev mailing list