Complete.Org: Mailing Lists: Archives: freeciv-dev: August 2001:
[Freeciv-Dev] Re: Timeout bug (PR#876)
Home

[Freeciv-Dev] Re: Timeout bug (PR#876)

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Thue <thue@xxxxxxx>, schnetter@xxxxxxx, freeciv-dev@xxxxxxxxxxx
Cc: bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Freeciv-Dev] Re: Timeout bug (PR#876)
From: Reinier Post <rp@xxxxxxxxxx>
Date: Tue, 7 Aug 2001 10:15:03 +0200

On Mon, Aug 06, 2001 at 09:50:59PM +0200, Thue wrote:
> On Monday 06 August 2001 17:54, schnetter@xxxxxxx wrote:
> > Full_Name: Stefan Schnetter
> > Version: every?
> > Distribution: -----------------
> > Client: Both (or N/A)
> > OS:
> > Submission from: (NULL) (217.224.166.238)
> >
> >
> > A Timeout less than 10 seconds should not be possible.
> > If someone "/set timeout 1" (and there exist ai players) the game
> > will be messed up.
> 
> Actually setting a timeout of 1 can be very usefull for AI testgames, 
> so we don't want to limit it.
> 
> There is a patch that used to be applied to the civservers running at 
> civserver.freeciv.org that allowed one to set a minimum timeout. I 
> guess it has not been applied to the various versions running now.

Correct.  The player who would do this either started to behave or
left.  But I've done it by accident.  On a fast server, in an all_AI
game, what you will see is that the game finishes almost instantly,
while the screen updates continue for 15 minutes or more.  So the game
appears to continue normally, except that none of the interaction has
any effect.  This is very unexpected, as far as I'm concerned.
Either we have to introduce a 'make server wait for client updates' option
or we have to introduce a higher minimum timeout just for this reason.

> Perhaps a patch that allows a lower limit for timeout will be applied 
> to CVS once 1.12.0 is out.

-- 
Reinier


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