Complete.Org: Mailing Lists: Archives: freeciv-dev: August 2001:
[Freeciv-Dev] Re: [Patch] Introduction of turns
Home

[Freeciv-Dev] Re: [Patch] Introduction of turns

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Christian Knoke <ChrisK@xxxxxxxx>
Cc: freeciv development list <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: [Patch] Introduction of turns
From: Raimar Falke <hawk@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 27 Aug 2001 22:21:14 +0200
Reply-to: rf13@xxxxxxxxxxxxxxxxxxxxxx

On Mon, Aug 27, 2001 at 09:09:33PM +0200, Christian Knoke wrote:
> Am Montag, 27. August 2001 19:05 schrieb Raimar Falke:
> > On Mon, Aug 27, 2001 at 12:52:34PM -0400, Ross W. Wetmore wrote:
> > > The client currently displays the Game year to the user, so I am
> > > not sure I understand why an additional mechanism is needed to send
> > > this.
> > >
> > > Is there some point in processing where the year can change in ways
> > > that the client won't pickup (immediately)? Is this what is being
> > > fixed?
> >
> > As pointed out before it is easier for client side ai planing to
> > handle with turns instead of years. It may be possible to calculate
> > the current turn from the current year but a far easier solution is
> > to add a field to struct civ_game and two packets.
> 
> These agents do some clever things, but can't simply count the turns ??

They could. But you have to save this over a client quit/newstart and
the same for server restart. Yes this can be done with a separate turn
counting agent but this overkill.

> It seems to be bad design to have both turns and years. If you really
> need the absolute turn number (from the beginning), you should send the
> turn number and compute the year.

Nice idea but this isn't possible currently. The transformation from
turn to year depends on the global space race which is AFAIK unknown
to the client.

        Raimar

-- 
 email: rf13@xxxxxxxxxxxxxxxxx
  reality.sys corrupt. Reboot Universe? (y,n,q)


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