public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Hans Ronne <hronne@comhem.se>
To: Jim Kingdon <kingdon@panix.com>
Cc: xconq7@sources.redhat.com
Subject: Re: Cannot do anything in water
Date: Mon, 08 Dec 2003 23:25:00 -0000	[thread overview]
Message-ID: <l03130301bbfa8241234b@[212.181.162.155]> (raw)
In-Reply-To: <200312081908.hB8J8sm01018@panix5.panix.com>

>> I was trying to work on my new game module, and now I've found that, if
>> I try to make a unit move into a water cell (and it can enter water
>> cells), it expends 1 ACP but does not go anywhere!
>
>Probably the same bug as
>http://sources.redhat.com/ml/xconq7/2003/msg00960.html
>
>> Could it be a bug in the new pathfinding algorithm?

Maybe. But not the construction problem since it does not involve
path-finding. If both are manifestations of the same bug, I would rather
suspect the terrain occupancy code.

OTOH, The construction bug sounds more like an undefined action being
allowed following an illegal click. The program should just beep instead
and refuse to do anything if you click in the wrong cell.

Hans


  reply	other threads:[~2003-12-08 19:39 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 [this message]
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
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='l03130301bbfa8241234b@[212.181.162.155]' \
    --to=hronne@comhem.se \
    --cc=kingdon@panix.com \
    --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).