public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: Hans Ronne <hronne@comhem.se>, <xconq7@sources.redhat.com>
Subject: Re: Major bug and what to do about it (long)
Date: Thu, 19 Aug 2004 16:46:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0408191149050.9287-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <20040818211030.85504.qmail@web13121.mail.yahoo.com>

On Wed, 18 Aug 2004, Elijah Meeks wrote:

> Now, if I have a unit-view that turns out to no longer
> represent a real unit, then this isn't a mirage, but
> faulty intelligence.  

I think that Stan used the term "mirage" in a somewhat figurative 
sense, and didn't literally mean a mirage. The terms "ghost unit" 
and "mirage" apply to any unit view that doesn't correspond to the 
unit it purports to correspond to (excepting mistaken sightings) 
at the position of the unit view.

> that I think to be there and am firing at indirectly
> (Tanks behind smoke, platoons behind hills or in
> cover, newly cloaked starships, all of which I would
> not fire at directly).

Unfortunately, cells are not subdivided into smaller spatial 
regions in any literal sense. Even the scheme that I am proposing 
treats subregions as virtual and not having any distinct 
coordinates within the cell.

What this leads to is that if you see an unit view in a cell, you 
can attempt direct fire == aimed fire == 'fire-at' at it. If you 
don't see any unit view in the cell, but suspect there might be 
one, then you can attempt indirect fire == 'fire-into' at it. 
Indirect fire against spatial subregions is currently not 
supported and would probably require some additional 
work to add. 

> Likewise, in a fantasy game, if an invisible unit
> attacks me, I'd like to have a unit-view, a la
> Nethack's 'I'.  

Do you know which direction it attacked you from? :-)

> Again, illusory enemies would be better represented by
> units (Hmmm, illusory enemies...  Sounds like I need
> to add more units to Opal...).

:-)

> indirect-hit-chance tables.  This way I could say that
> a unit representing an individual with a bolt action
> rifle would have a worse chance than an artillery
> piece firing explosive shells to hit a unit that it
> can't see.  Then you could extrapolate the
> indirect-fire-hit-chance table into a system of
> hitting other units within a hex, something I believe
> would be better suited and allow for more dynamic
> simulation of hits to stacked units than the current
> system.

If we are saying that precision (as Hans called it) is not 
factored into 'hit-chance' and 'fire-hit-chance' already, then 
this might be something worth considering. Interesting idea....

Eric

  parent reply	other threads:[~2004-08-19 16:05 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16 21:53 Hans Ronne
2004-08-16 22:14 ` Eric McDonald
2004-08-16 22:43   ` Hans Ronne
2004-08-17  0:33     ` Hans Ronne
2004-08-17  1:13       ` Eric McDonald
2004-08-17  1:39         ` Hans Ronne
2004-08-17  2:21           ` Eric McDonald
2004-08-17  4:28           ` Jim Kingdon
2004-08-17  5:17             ` Hans Ronne
2004-08-17 18:00               ` Eric McDonald
2004-08-18  5:26               ` Jim Kingdon
2004-08-18 11:11                 ` Hans Ronne
2004-08-17 16:14             ` Eric McDonald
2004-08-17  0:35     ` Eric McDonald
2004-08-17  1:16       ` Hans Ronne
2004-08-17  1:46         ` Eric McDonald
2004-08-17  3:03           ` Hans Ronne
2004-08-17  3:56             ` Eric McDonald
2004-08-17  1:30 ` Eric McDonald
2004-08-17  2:52   ` Hans Ronne
2004-08-17  2:53     ` Eric McDonald
2004-08-17  4:42       ` Jim Kingdon
2004-08-17 16:37         ` Eric McDonald
2004-08-17  4:48       ` Hans Ronne
2004-08-17 16:42         ` Eric McDonald
2004-08-18 10:56         ` Jim Kingdon
2004-08-17 11:06 ` Stan Shebs
2004-08-17 15:29   ` Hans Ronne
2004-08-17 16:01     ` Hans Ronne
2004-08-17 18:57       ` Eric McDonald
2004-08-17 20:38         ` Hans Ronne
2004-08-17 21:55           ` Eric McDonald
2004-08-17 23:42             ` Hans Ronne
2004-08-18  0:49               ` Eric McDonald
2004-08-18  4:59                 ` Hans Ronne
2004-08-18 15:28                   ` Eric McDonald
2004-08-19  6:37                     ` Elijah Meeks
2004-08-19 12:46                       ` Hans Ronne
2004-08-19 16:46                       ` Eric McDonald [this message]
2004-08-19 13:09                     ` Hans Ronne
2004-08-19 16:05                       ` Eric McDonald
2004-08-19 20:09                         ` Hans Ronne
2004-08-19 23:37                           ` Eric McDonald
2004-08-20  1:42                             ` Hans Ronne
2004-08-20  3:29                               ` Clearing the Air (long) Eric McDonald
2004-08-20 15:26                                 ` Stan Shebs
2004-08-18  5:30         ` Major bug and what to do about it (long) Jim Kingdon
2004-08-18 12:52           ` Hans Ronne
2004-08-17 18:23     ` Eric McDonald
2004-08-17 18:47       ` Hans Ronne
2004-08-17 18:59         ` Eric McDonald
2004-08-17 19:39           ` Hans Ronne
2004-08-17 21:14             ` 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.0408191149050.9287-100000@leon.phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --cc=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).