[Freeciv-Dev] (PR#10359) Saving changes game state
[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: |
undisclosed-recipients: ; |
Subject: |
[Freeciv-Dev] (PR#10359) Saving changes game state |
From: |
"Marko Lindqvist" <marko.lindqvist@xxxxxxxxxxx> |
Date: |
Mon, 27 Sep 2004 11:59:35 -0700 |
Reply-to: |
rt@xxxxxxxxxxx |
<URL: http://rt.freeciv.org/Ticket/Display.html?id=10359 >
It seems that simply (auto)saving a game changes its state. Usually
this is difficult to notice - when you are not saving there is no save
games to compare.
Attached two autogames (modified versions of #10208 autogame) differ
only in saveturns setting. Running ally_assert.rc, which autosaves every
turn, assert fails in year -600. When running allytest.rc, which never
saves, assert does not fail (it would fail in year 220)
Another possible reason for this is that saveturns setting itself is
used for something it shouldn't be used for.
- Caz
set timeout -1
create Tester
set aifill 17
set saveturns 1
set endyear 0100
set gameseed 1096243383
set mapseed 1561754589
set borders 0
set startunits cc
rulesetdir civ2
start
set timeout -1
create Tester
set aifill 17
set saveturns 0
set endyear 0100
set gameseed 1096243383
set mapseed 1561754589
set borders 0
set startunits cc
rulesetdir civ2
start
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Freeciv-Dev] (PR#10359) Saving changes game state,
Marko Lindqvist <=
|