From: Elijah Meeks <elijahmeeks@yahoo.com>
To: Hans Ronne <hronne@comhem.se>
Cc: xconq7@sources.redhat.com
Subject: Re: Reduced Visibility Table?
Date: Tue, 02 Dec 2003 01:09:00 -0000 [thread overview]
Message-ID: <20031202005832.45465.qmail@web13123.mail.yahoo.com> (raw)
In-Reply-To: <l03130300bbf16fdb70a7@[212.181.162.155]>
Thanks for those tables, that's exactly what I'm
looking for. As to ACP, I guess I wasn't clear, I'm
wondering if there's a way so that a newly created
unit has -1 ACP (Like a unit you've placed using the
designer), rather than starting with full ACP.
--- Hans Ronne <hronne@comhem.se> 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)?
>
> DEF_UU_TABLE("see-chance", uu_see,
> "chance for a type of unit to see another type at a
> distance",
> uusee, constuusee, 0, 100, TABHI, TABINT)
>
> DEF_UU_TABLE("see-chance-adjacent", uu_see_adj,
> "chance for a type of unit to see another type in
> the same cell",
> uuseeadj, constuuseeadj, 0, 100, TABHI, TABINT)
>
> DEF_UU_TABLE("see-chance-at", uu_see_at,
> "chance for a type of unit to see another type in
> an adjacent cell",
> uuseeat, constuuseeat, 0, 100, TABHI, TABINT)
>
> >Also, does anyone know a way to set unit ACP to 0
> on
> >creation?
>
> Depends on what you want to achieve. If you want
> your unit to be unable to
> do anything just set acp-per-turn to 0. If you want
> your unit to be unbound
> by acp (e.g. in building) set acp-independent to
> true.
>
> Hans
>
>
__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
next prev parent reply other threads:[~2003-12-02 0:58 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 [this message]
2003-12-02 4:02 ` Hans Ronne
2003-12-01 23:23 ` Bruno Boettcher
2003-12-01 23:27 ` Lincoln Peters
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=20031202005832.45465.qmail@web13123.mail.yahoo.com \
--to=elijahmeeks@yahoo.com \
--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).