Follow-up Comment #5, patch #6882 (project freeciv):
Those particular bits sound like ones you can implement without touching
anything else - having them not-set by default is the right thing to happen.
1) Tileset (client) topology is different thing from map topology, and we
sometimes need to convert latter to former (to make sure tileset is compatible
with the map). For that conversion your new bits are not relevant (relevant
ones are "hex" & "isometric" bits)
2) Savegames with format from older freeciv versions list the bits (by name)
that are set in the 'topology' setting. I don't think you need to enable those
new bits in any situation when converting such old savegames to new format, so
no need to touch that part either.
--
As for this ticket & S2_6 d3f: It's just the supported setting values that are
of d3f relevance here. If a datafile (savegame/scenario/game.ruleset) tries to
set server setting 'generator' to value 'fracture', it should not cause
failure on any freeciv revision after the freeze.
_______________________________________________________
Reply to this item at:
<http://gna.org/patch/?6882>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Freeciv-dev mailing list
[email protected]
https://mail.gna.org/listinfo/freeciv-dev
