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

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

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: lorimer@xxxxxxxxxxxx, Thue <thue@xxxxxxx>
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: freeciv bug with WRITE command in civserver.exe (PR#795)
From: Reinier Post <rp@xxxxxxxxxx>
Date: Mon, 4 Jun 2001 09:46:16 +0200

On Sun, Jun 03, 2001 at 07:23:59PM -0400, Derek Ray wrote:
 
> 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.

I don't think this is a good idea.  'read' is a nice clean command:
it accepts everything you can specify on the command line.  'write'
isn't: it cannot write everything you can specify on the command line.
So if you're going to cripple one of them, cripple the 'write' command
further.

> 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?  =)

I think it would be better to have two write commands for this purpose,
'writesetup' and 'writestate', for example.

If that is true, it's a bug!

-- 
Reinier


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