From: Lincoln Peters <sampln@sbcglobal.net>
To: bboett@adlp.org
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Reduced Visibility Table?
Date: Mon, 01 Dec 2003 23:27:00 -0000 [thread overview]
Message-ID: <1070321096.9357.140.camel@odysseus> (raw)
In-Reply-To: <20031201231823.GH1378@adlp.org>
On Mon, 2003-12-01 at 15:18, Bruno Boettcher wrote:
> On Mon, Dec 01, 2003 at 02:14:25PM -0800, Elijah Meeks wrote:
> > Is there a way to make units less visible--submarines
> > and spies, for example, that could only be seen by
> > adjacent units (Even if the other unit has a visual
> > range higher than 1)?
> since reading this.... is there a way to let those units coexist with
> enemy units in the same cell?
You can make any unit exert zero ZOC (Zone of Control). However, the
last time I looked at games that used this (which was before the new
pathfinding algorithm was introduced), units still tried to go around
invisible enemy units with no ZOC, even though they could not
theoretically see those enemy units!
--
Lincoln Peters <sampln@sbcglobal.net>
next prev parent reply other threads:[~2003-12-01 23:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 22:35 Elijah Meeks
2003-12-01 23:18 ` Hans Ronne
2003-12-02 1:09 ` Elijah Meeks
2003-12-02 4:02 ` Hans Ronne
2003-12-01 23:23 ` Bruno Boettcher
2003-12-01 23:27 ` Lincoln Peters [this message]
2003-12-01 23:43 ` Stan Shebs
2003-12-02 0:30 ` Hans Ronne
2003-12-02 0:54 ` Lincoln Peters
2003-12-02 0:58 ` Hans Ronne
2003-12-02 4:46 ` Eric McDonald
2003-12-02 4:04 ` Eric McDonald
2003-12-02 4:16 ` Eric McDonald
2003-12-02 20:56 ` Hans Ronne
2003-12-03 2:41 ` Eric McDonald
2003-12-03 3:04 ` Lincoln Peters
2003-12-03 21:13 ` Eric McDonald
2003-12-01 23:32 ` Hans Ronne
2003-12-02 15:04 ` Bruno Boettcher
2003-12-02 19:57 ` Emmanuel Fritsch
2003-12-03 2:12 ` Hans Ronne
2003-12-03 2:22 ` 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=1070321096.9357.140.camel@odysseus \
--to=sampln@sbcglobal.net \
--cc=bboett@adlp.org \
--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).