Complete.Org: Mailing Lists: Archives: freeciv-dev: June 2003:
[Freeciv-Dev] Re: (PR#4326) Pathfinding
Home

[Freeciv-Dev] Re: (PR#4326) Pathfinding

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: ChrisK@xxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#4326) Pathfinding
From: "Raimar Falke" <rf13@xxxxxxxxxxxxxxxxx>
Date: Tue, 10 Jun 2003 09:45:39 -0700
Reply-to: rt@xxxxxxxxxxxxxx

On Mon, Jun 09, 2003 at 04:15:46AM -0700, Gregory Berkolaiko wrote:
> 
> On Sun, 8 Jun 2003, Raimar Falke wrote:
> 
> > On Fri, Jun 06, 2003 at 11:06:29AM -0700, Gregory Berkolaiko wrote:
> > > 
> > > > Greg: you may now see why I prefered a flags field in pf_parameter
> > > > instead of the zoc_used field.
> > > 
> > > I admit I was thinking the same.  But we need to carefully consider what 
> > > we do, because some AI calculations need to ignore ZoC...
> > 
> > They this code has to remove F_IGZOC in parameter->flags.
> 
> This is a bit ugly, but probably the best way.

So you agree on the whole plan?

> > > or use a different notion of ZoC.
> > 
> > If code wants this you have to be more specific.
> 
> I realised that when planning strategic attacks (on enemy cities), AI
> should ignore ZoC imposed by enemy units in the field, but pay attention
> to the ZoC imposed by enemy cities.
> 
> > > Another solution is write another MC-callback marine_move_unit.
> > 
> > You would need another flags to trigger this. So we would have to add
> > a "bool is_marine" to pf_parameter. I'm strongly against this since
> > this duplicates unit_type->flags.
> 
> No flag is needed.  Have a look how we handle trireme case for example.

So you want another callback? I doubt this.

        Raimar

-- 
 email: rf13@xxxxxxxxxxxxxxxxx
 "The BeOS takes the best features from the major operating systems. 
  It's got the power and flexibility of Unix, the interface and ease 
  of use of the MacOS, and Minesweeper from Windows."




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