This is the mail archive of the
xconq7@sources.redhat.com
mailing list for the Xconq project.
Re: annoying new bug in movement
- From: Lincoln Peters <sampln at sbcglobal dot net>
- To: Eric McDonald <mcdonald at phy dot cmich dot edu>
- Cc: Xconq list <xconq7 at sources dot redhat dot com>
- Date: Wed, 24 Dec 2003 15:09:17 -0800
- Subject: Re: annoying new bug in movement
- References: <Pine.LNX.4.44.0312222345320.13523-100000@leon.phy.cmich.edu>
On Mon, 2003-12-22 at 20:54, Eric McDonald wrote:
> > Meanwhile, I also noticed that I no longer seem to be able to issue move
> > commands to units if the move command would leave them inside another
> > unit (e.g. I tell a battledroid to move into a base). However, I can
> > still have one unit occupy another if they are adjacent to each other.
> > I'm not yet sure if this odd behavior is restricted to bolodd2.g or not.
>
> Didn't you previously report that a unit would not take a path
> that would lead it through a potential transport, such as a city
> or a base? If so, it is probably related to this. dist > 1
> logic has changed rather significantly due to the new
> pathfinding and its attendant details.
Yes, I did. Although I didn't have any difficulty telling a unit to
enter a transport until now (I only had difficulty when a unit tried to
pass through a transport).
Perhaps that is the root of the problem? Unless, of course, there are
multiple bugs at work here...
--
Lincoln Peters <sampln@sbcglobal.net>