From: Jim Kingdon <kingdon@panix.com>
To: mcdonald@phy.cmich.edu
Cc: xconq7@sources.redhat.com
Subject: Re: annoying new bug in movement
Date: Wed, 31 Dec 2003 19:10:00 -0000 [thread overview]
Message-ID: <200312301826.hBUIQXi08764@panix5.panix.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0312210153320.24091-100000@leon.phy.cmich.edu> (message from Eric McDonald on Sun, 21 Dec 2003 02:22:27 -0500 (EST))
> (2) do_move_action . . .
> But at least now a notification is provided to let the player know
> that the movement cannot be performed, and ACP is prevented from
> being deducted in such a circumstance.
I tried this with the test case I've been using, and it does have the
intended effect (now ACP is not deducted, and I get the "%s was unable
to perform requested move to %d,%d." message).
Not a full fix, but better than it was.
prev parent reply other threads:[~2003-12-30 18:26 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
2003-12-31 19:10 ` Jim Kingdon [this message]
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=200312301826.hBUIQXi08764@panix5.panix.com \
--to=kingdon@panix.com \
--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).