Complete.Org: Mailing Lists: Archives: freeciv-dev: February 2003:
[Freeciv-Dev] Re: (PR#3467) AI idles fortifying units that do not move
Home

[Freeciv-Dev] Re: (PR#3467) AI idles fortifying units that do not move

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: per@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#3467) AI idles fortifying units that do not move
From: "Gregory Berkolaiko" <Gregory.Berkolaiko@xxxxxxxxxxxx>
Date: Wed, 19 Feb 2003 05:26:48 -0800
Reply-to: rt@xxxxxxxxxxxxxx

On Wed, 19 Feb 2003, Per I. Mathisen wrote:

> On Wed, 19 Feb 2003, Gregory Berkolaiko wrote:
> > Now let's deal with you, Per ;)You are a sinner too but you might be
> > unaware of it.When you "finally fixed this age old problem", you broke
> > the explorer code.Not fatally, but wounded it severely.  The problem was
> > that it couldn't call ai_unit_goto or whatever it was and had to go one
> > step at a time, recomputing warmap at each step (and you know how fast
> > that is).This is why idling reappeared.
> 
> And why can't you use ai_unit_goto()? And why didn't you tell my earlier
> so I could fix it?

Sorry.  I looked up my earlier email, it's a different thing we can't use:
======
Problem 2: verrrry slow.  The problem is two-fold.  First, you don't set
activity to IDLE, so handle_unit_move_request fails and you have to
generate warmap for _every_ move.
======
And I guess we can/should use ai_unit_goto instead of 
handle_unit_move_request.

I would prefer to fix this as a part of a bigger patch, changing EXPLORE 
from activity to auto-mode.  If you have no objections, I will talk to 
Cameron about it.

G.




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