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: Mon, 22 Dec 2003 20:43:26 -0800
- Subject: Re: annoying new bug in movement
- References: <Pine.LNX.4.44.0312222310220.13523-100000@leon.phy.cmich.edu>
On Mon, 2003-12-22 at 20:25, Eric McDonald wrote:
> That is the error notification that I added to the code.
> As I mentioned, but perhaps was not clear, I made no serious
> attempt to isolate the underlying problem. My "fix" was just to
> deaden the pain somewhat.
>
> I don't really feel responsible for this bug (aside from checking
> in the patch (from someone else) that likely introduced it), and
> thus am not feeling highly motivated to fix it at this point.
It is certainly less painful, now that it doesn't burn an ACP. And I'm
still trying to find a pattern that would indicate the exact location of
the bug.
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.
--
Lincoln Peters <sampln@sbcglobal.net>