public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Jim Kingdon <kingdon@panix.com>
Cc: xconq7@sources.redhat.com
Subject: Re: time.g weirdness
Date: Thu, 12 Aug 2004 17:08:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0408121255310.29406-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <200408121542.i7CFg9b11038@panix5.panix.com>

On Thu, 12 Aug 2004, Jim Kingdon wrote:

> > 1. By volume restrictions (terrain capacity and unit-size-in-terrain).
> > 2. By move restrictions (mp-to-enter-terrain and mp-to-leave-terrain).
> > 3. By survival restrictions (vanishes-on and wrecks-on).
> 
> This has always seemed confusing to me.
> 
> The game designer, to get things to work consistently, seemingly has
> to set a bunch of these properties.

Hans and I had a thread about this before (I don't remember if it 
was public or not), but, generally speaking, the move restrictions 
should be used to limit whether or not an unit can enter a given 
terrain. Using survival restrictions is not reliable, especially 
since deliberate movement in wreck/vanish situations should not 
necessarily be prohibited (even though the AI should try to avoid 
them).

Eric

  parent reply	other threads:[~2004-08-12 16:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10 17:51 Robert Goulding
2004-08-10 18:11 ` Hans Ronne
2004-08-11  1:23 ` Hans Ronne
2004-08-11 16:34   ` Jim Kingdon
2004-08-11 16:34     ` Hans Ronne
2004-08-11 16:47       ` Eric McDonald
2004-08-11 17:09         ` Hans Ronne
2004-08-12  4:03           ` Eric McDonald
2004-08-12 11:16             ` Hans Ronne
2004-08-11 16:41     ` Eric McDonald
2004-08-12  8:42       ` Jim Kingdon
2004-08-12  8:56         ` Hans Ronne
2004-08-12 15:42           ` Jim Kingdon
2004-08-12 16:58             ` Eric McDonald
2004-08-12 17:35               ` Hans Ronne
2004-08-12 16:55         ` Eric McDonald
2004-08-12 15:39 ` Hans Ronne
2004-08-12 16:53   ` Jim Kingdon
2004-08-12 16:59     ` Hans Ronne
2004-08-12 17:08     ` Eric McDonald [this message]
2004-08-12 17:19       ` Hans Ronne
2004-08-12 17:24         ` Eric McDonald
2004-08-12 18:15           ` Hans Ronne
2004-08-13 23:46             ` Eric McDonald
2004-08-14  3:50             ` Wrecked-Type Doesn't Apply to Detonating Units Elijah Meeks
2004-08-14  9:19               ` Eric McDonald
2004-08-14 15:36                 ` Hans Ronne
2004-08-14 16:00                   ` Eric McDonald
2004-08-14 17:42                     ` Eric McDonald
2004-08-16  0:27                 ` Elijah Meeks
2004-08-16 18:24                   ` Eric McDonald
2004-08-16 21:34                     ` Elijah Meeks
2004-08-17  0:50                       ` 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=Pine.LNX.4.44.0408121255310.29406-100000@leon.phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --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).