From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: annoying new bug in movement
Date: Tue, 23 Dec 2003 04:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0312222310220.13523-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <1072152692.31574.1730.camel@odysseus>
Hi Lincoln,
On Mon, 22 Dec 2003, Lincoln Peters wrote:
> I just tested the new patch with bolodd2.g, and found that, although an
> ACP is no longer burned when a move action fails, I still get an error
> when I try to make a naval unit move into water:
>
> Your 1st boat was unable to perform requested move to 30,13
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.
> Your 1st boat can never do this!
I think my error message is more descriptive. :-)
> It would seem that a bug still exists somewhere in the pathfinding
> code...
Yes. Or more generally, the movement code.
Eric
next prev parent reply other threads:[~2003-12-23 4:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 1:33 Jim Kingdon
2003-12-06 1:34 ` Hans Ronne
2003-12-21 13:16 ` Eric McDonald
2003-12-23 4:40 ` Lincoln Peters
2003-12-23 4:54 ` Eric McDonald [this message]
2003-12-24 23:05 ` Lincoln Peters
2003-12-26 0:48 ` Eric McDonald
2003-12-26 2:06 ` Lincoln Peters
2003-12-31 19:10 ` Jim Kingdon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0312222310220.13523-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=sampln@sbcglobal.net \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).