From: Lincoln Peters <sampln@sbcglobal.net>
To: mskala@ansuz.sooke.bc.ca
Cc: Xconq developers mailing list
<xconq-developers@lists.sourceforge.net>,
xconq7 <xconq7@sources.redhat.com>
Subject: Re: GIS and navigable rivers
Date: Tue, 04 Jan 2005 21:27:00 -0000 [thread overview]
Message-ID: <1104873945.5594.50.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.53.0501041210140.7308@opal.ansuz.sooke.bc.ca>
On Tue, 2005-01-04 at 12:32 -0500, mskala@ansuz.sooke.bc.ca wrote:
> There's some discussion of the navigable-rivers issue in the designer's
> manual; if you make them borders so that they can impede land movement,
> then it's tricky for ships to travel along them, and if you make them
> connections so that ships can travel along them, they won't impede land
> movement. The documentation suggests making a chain of alternating lake
> hexes and river borders, and using the special "border slide" movement
> mode.
The more I think about this, the more I think that the solution would be
to make mp-to-leave-terrain work for connections, so that one can cause
a unit to spend one or two extra MP's to leave a cell with a certain
type of connection, preferably without penalizing them if they simply
traverse the connection (unless mp-to-traverse is used for that purpose)
or cross it by means of another connection (i.e. a bridge).
I'll add this to the feature request tracker on SourceForge as soon as I
get a chance.
---
Lincoln Peters
<sampln@sbcglobal.net>
BOFH excuse #134:
because of network lag due to too many people playing deathmatch
prev parent reply other threads:[~2005-01-04 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-01 6:59 New Feature: Overwatch Eric McDonald
2005-01-01 7:19 ` Lincoln Peters
2005-01-01 16:31 ` Eric McDonald
2005-01-01 21:09 ` Lincoln Peters
2005-01-01 21:38 ` Eric McDonald
2005-01-02 2:43 ` Bug reports, feature requests, and dilemmas [was: Re: New Feature: Overwatch] Lincoln Peters
2005-01-04 17:24 ` GIS and navigable rivers mskala
2005-01-04 21:27 ` Lincoln Peters [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=1104873945.5594.50.camel@localhost.localdomain \
--to=sampln@sbcglobal.net \
--cc=mskala@ansuz.sooke.bc.ca \
--cc=xconq-developers@lists.sourceforge.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).