Complete.Org: Mailing Lists: Archives: freeciv-dev: August 2001:
[Freeciv-Dev] Re: 3 patches for use on public gameservers (fwd <- rp@xxx
Home

[Freeciv-Dev] Re: 3 patches for use on public gameservers (fwd <- rp@xxx

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: rf13@xxxxxxxxxxxxxxxxxxxxxx
Cc: Freeciv developers <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: 3 patches for use on public gameservers (fwd <- rp@xxxxxxxxxx)
From: Paul Zastoupil <paulz@xxxxxxxxxxxx>
Date: Fri, 31 Aug 2001 16:55:38 -0700

On Fri, Aug 31, 2001 at 11:27:54PM +0200, Raimar Falke wrote:
> On Fri, Aug 31, 2001 at 01:49:34PM -0700, Paul Zastoupil wrote:
> > On Fri, Aug 31, 2001 at 10:52:15PM +0200, Raimar Falke wrote:
> > > On Fri, Aug 31, 2001 at 11:35:24AM -0700, Paul Zastoupil wrote:
> > > > 
> > > > Ok, here it is, although a but ugly.
> > > > 
> > > > mintimeout can only be set from the server console.
> > > 
> > > A cleaner solution for the -1 case may be a new server variable
> > > "autogame" which has to appropriate cmdlevel. No ugly hack and the
> > > IMHO good separation of timeout and autogame.
> > 
> > But this doesn't help the case of someone setting the timeout to 1 on
> > a public server.
> 
> Yes. This is the reason I used "for the -1 case". I still think
> PUBLIC_SERVER is an option.

I could see when PUBLIC_SERVER would be a nice option, but don't we
still need to have the code in there that gets activated by that flag?

I know my solution to this is a bit ugly, its still a step in the right
direction.

-- 
Paul Zastoupil


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