From: Lincoln Peters <sampln@sbcglobal.net>
To: Hans Ronne <hronne@comhem.se>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Cannot do anything in water
Date: Tue, 09 Dec 2003 12:50:00 -0000 [thread overview]
Message-ID: <1070947554.1444.1157.camel@odysseus> (raw)
In-Reply-To: <l03130302bbfab84dd9e0@[212.181.162.155]>
On Mon, 2003-12-08 at 15:24, Hans Ronne wrote:
> >That's not what I've observed. I've often found that if the cell I tell
> >it to build in is illegal (e.g. try to build a city in the water), but
> >it can build in a nearby legal cell without moving (the cell is within
> >its create-range), it will build in that alternate location instead.
> >And it never asks if that is what I want to do.
>
> That's what I meant. The computer should never do that. If you try to do
> something which is not permitted, it should just beep at you. So this is
> definitely a bug.
True, but at the time, my game was set up so that one *could* build
stuff on water cells (and those units would not instantly vanish or
wreck). This was so that, although most units cannot cross bodies of
water on their own, many could build simple boats to carry them across.
I think that this means that there are, in fact, two or more bugs at
work here.
Lincoln Peters <sampln@sbcglobal.net>
next prev parent reply other threads:[~2003-12-09 5:23 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 [this message]
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=1070947554.1444.1157.camel@odysseus \
--to=sampln@sbcglobal.net \
--cc=hronne@comhem.se \
--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).