Complete.Org: Mailing Lists: Archives: freeciv-dev: June 2001:
[Freeciv-Dev] Re: freeciv bug with WRITE command in civserver.exe (PR#7
Home

[Freeciv-Dev] Re: freeciv bug with WRITE command in civserver.exe (PR#7

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Thue <thue@xxxxxxx>
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: freeciv bug with WRITE command in civserver.exe (PR#795)
From: Derek Ray <lorimer@xxxxxxxxxxxx>
Date: Sun, 03 Jun 2001 19:23:59 -0400

At 10:42 PM 06/03/2001 +0200, Thue wrote:
On Sunday 03 June 2001 22:07, lorimer@xxxxxxxxxxxx wrote:
> When using the WRITE command in the server to write out a ruleset, it
> writes the following two variables to the file that it shouldn't:
>
> seed
> randseed
>
> This is bad since when you later start the server with the --read
> (filename) command line option, it then reads IN those variables - which
> result in a completely identical map and starting position for the game.
>
> I managed a workaround by deleting the two lines from the (filename) that I
> wrote out; simple enough for now.

Though you would sometimes want to have those saved, most of the time you
don't. So if nobody disagrees I will remove them from the output.

OK, I can see where it's possible that you sometimes DO want them saved - so you can "repeat" a game with the same setup, for whatever reason. How about this:

WRITE command *will* save both variables.
READ command and --read argument won't read the variables back in, though.

This way, the variables get saved somewhere, and you can always manually adjust them. Which reminds me, after using my workaround, I noticed that the --read argument set both seed and randseed to 0 when it didn't encounter them in the file. Oops? =)



[Prev in Thread] Current Thread [Next in Thread]