Help has moved to the Planio platform. All logins and passwords remained the same. All users will be able to login and use Redmine just as before. Read more...

Feature #692373

Provenance (defaultness) of game-start setting values not tracked

Added by Jacob Nevins almost 5 years ago. Updated 10 months ago.

Start date:
Due date:
% Done:


Estimated time:


2.6 added the notion of defaultness for server settings, so that if a default changes, a loaded savegame can be updated with the new default.

If a setting was at internal or ruleset default at game start, and then you set a setting after game start, save/load a game, and then '/reset game', and then the default subsequently changes, then the game's default won't follow that, because the provenance of the game-start value isn't tracked in the savefile.

To fix this, 'struct setting' would have to gain a 'game_setdef' member, and that would have to be saved in a new column in [settings] in savefiles (=> d3f).

This is probably not a very important corner case. I raise it mainly to record that I've thought about it. (Other '/reset' commands do the right thing wrt defaultness, I think.)

Related issues

Blocks Freeciv - Task #673656: S3_1 datafile format freeze (d3f)Closed

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>


#1 Updated by Marko Lindqvist over 1 year ago

  • Blocks Task #673656: S3_1 datafile format freeze (d3f) added

#2 Updated by Marko Lindqvist 11 months ago

  • Sprint/Milestone set to 3.1.0

#5 Updated by Marko Lindqvist 10 months ago

  • Status changed from Resolved to Closed
  • Assignee set to Marko Lindqvist

Also available in: Atom PDF