From: Lincoln Peters <sampln@sbcglobal.net>
To: Xconq list <xconq7@sources.redhat.com>
Subject: Re: More clues about that evasive pathfinding bug
Date: Thu, 18 Dec 2003 06:25:00 -0000 [thread overview]
Message-ID: <1071725112.25715.296.camel@odysseus> (raw)
In-Reply-To: <1071554390.10671.134.camel@odysseus>
Perhaps I should have waited before clicking "Send", in case the bug
manifested itself in another way.
This happened later in that same bellum.g game. The game appears to be
set up so that paratroopers cannot fight while occupying a cargo plane.
Previously, if paratroopers were in a cargo plane, and I instructed them
to attack, Xconq would just beep at me and say "(unit name) in unable to
act, don't know why". This time, it burned an ACP, did nothing, and
gave no indication of an error.
The same thing (burn an ACP without doing anything) seems to happen if I
try to make a unit attack another unit that it cannot attack
(acp-to-attack = 0).
There seem to be additional random events that trigger the bug, and I'm
still trying to find a pattern.
--
Lincoln Peters <sampln@sbcglobal.net>
next prev parent reply other threads:[~2003-12-18 5:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 7:16 Cannot do anything in water 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
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 [this message]
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=1071725112.25715.296.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).