empire/empserver
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

designate: Drop support for designate costing money

Browse source 
Chainsaw 3 added the designate cost along with extra build cost and
materials, and used both to make fortresses expensive.  Unlike build
cost and materials, the cost to designate didn't pass the test of
time: it was set to zero in Empire 2.  Get rid of it.

sect-chr selector cost and struct dchrstr member d_cost have to stay,
because they're still used to configure whether a sector may be
designated by players (see commit 8d792e1).

Signed-off-by: Markus Armbruster <armbru@pond.sub.org>
This commit is contained in:
Markus Armbruster 2016-06-05 19:08:19 +02:00
parent 9d6b3b3520
commit ba2795fbf7
6 changed files with 23 additions and 37 deletions
Download patch file Download diff file Expand all files Collapse all files

3
src/lib/global/sect.config
View file

@ -52,7 +52,8 @@
# column cost, and only to something with the same terrain. All
# sectors with the same terrain and non-negative cost should have the
# same population limit (column maxpop), or else players can abuse
# redesignation to mass-murder people.
# redesignation to mass-murder people. Other than that, cost has no
# purpose anymore.
# A sector with urban packing (urba in column pkg) is a big city.
# Column maxpop applies at 0% efficiency. The limit at 100% is ten