Complete.Org: Mailing Lists: Archives: freeciv-dev: May 2003:
[Freeciv-Dev] Re: RFC: Layers Patch

[Freeciv-Dev] Re: RFC: Layers Patch

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: RFC: Layers Patch
From: "Per I. Mathisen" <per@xxxxxxxxxxx>
Date: Thu, 29 May 2003 15:23:48 +0000 (GMT)

On Thu, 29 May 2003, Arnstein Lindgard wrote:
> Per described two problems;
> > - attacking a tile that contains a ground unit and an air unit results
> > in behaviour that is not well defined and sometimes highly undesirable
> Allow attcking.

I guess you mean "allow attacking if there is any unit on target tile that
you can attack". This _can_ be solved simply by moving several checks from
can_unit_attack_unit_at_tile() into common code and get_defender().

You still have the problem of 100% civ1/2 compatibility.

> > - X transporting Y units into a tile with a unit by Z, where allied(X,
> > Z) and !allied(Y, Z) results in illegal stacking
> Disallow moving there.

I'm sorry, I was not being clear. There are two separate problems here.
The first is how to deal with multi-owner stacks. The proposal in redux is
the same as Greg's: You cannot attack a stack unless you are at war with
_all_ units on that tile.

I forgot to mention, though, that none of the proposals so far have solved
the transport problem above. The extra complicating factor is that we do
not know for sure what units we will be bringing along as a transport from
tile1 to tile2, since we rehash the transport list _after_ having decided
to move.

Anyway, I'm happy with any solution as long as the core dumps go away and
no options are added.

  - Per

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