From: Lincoln Peters <sampln@sbcglobal.net>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: annoying new bug in movement
Date: Fri, 26 Dec 2003 02:06:00 -0000 [thread overview]
Message-ID: <1072307355.3305.13995.camel@odysseus> (raw)
In-Reply-To: <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>
next prev parent reply other threads:[~2003-12-24 23:05 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
2003-12-24 23:05 ` Lincoln Peters
2003-12-26 0:48 ` Eric McDonald
2003-12-26 2:06 ` Lincoln Peters [this message]
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=1072307355.3305.13995.camel@odysseus \
--to=sampln@sbcglobal.net \
--cc=mcdonald@phy.cmich.edu \
--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).