From: Lincoln Peters <sampln@sbcglobal.net>
To: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Cannot do anything in water
Date: Mon, 15 Dec 2003 04:38:00 -0000 [thread overview]
Message-ID: <1071462057.11561.24.camel@odysseus> (raw)
In-Reply-To: <l03130301bbfa8241234b@[212.181.162.155]>
I have found that this mysterious water bug affects bolodd2.g, as well
as the new game I'm working on. If you try to move a naval unit into
the water (I haven't tried air units yet), the unit expends an ACP
without going anywhere.
I also noticed that, in roman.g, an infantry sometimes expends an ACP
while trying to cross a river, but doesn't actually cross the river.
Even stranger, if I tell it to move to a non-adjacent cell, it seems
that the ACP readout shows "ACP 1", when it should say "ACP 1/2"! This
usually seems to happen when the unit could have avoided crossing the
river and spent as many or fewer ACP's by going around it (no problems
if there is no way around the river). Perhaps the same bug? Or at
least a related bug?
Perhaps someone who understands the recent changes to the pathfinding
code could look at bolodd2.g and roman.g and make some sense out of this
mysterious problem.
Meanwhile, I'll keep looking for more clues...
--
Lincoln Peters <sampln@sbcglobal.net>
next prev parent reply other threads:[~2003-12-15 4:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 7:16 Lincoln Peters
2003-12-08 22:48 ` Jim Kingdon
2003-12-08 23:25 ` Hans Ronne
2003-12-09 0:40 ` Lincoln Peters
2003-12-09 0:57 ` Hans Ronne
2003-12-09 12:50 ` Lincoln Peters
2003-12-15 4:38 ` Lincoln Peters [this message]
2003-12-15 20:00 ` Jim Kingdon
2003-12-16 1:42 ` Lincoln Peters
2003-12-16 9:31 ` More clues about that evasive pathfinding bug Lincoln Peters
2003-12-18 6:25 ` Lincoln Peters
2003-12-18 18:00 ` Eric McDonald
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=1071462057.11561.24.camel@odysseus \
--to=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).