public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Hans Ronne <hronne@comhem.se>
Cc: xconq7@sources.redhat.com
Subject: Re: Overrun actions (was: Consumption-per-fire?)
Date: Sun, 06 Jun 2004 13:33:00 -0000	[thread overview]
Message-ID: <1086528611.1485.227.camel@localhost.localdomain> (raw)
In-Reply-To: <l03130300bce8763bbe35@[212.181.162.155]>

On Sun, 2004-06-06 at 01:37, Hans Ronne wrote:

> Another thing that I found while looking into overruns is that
> left-clicking on  an enemy unit now only works from adjacent cells. If you
> do it from further away, you get the "no room" error message. 

Now that you mention this, I think I have seen this as well. If the
enemy existed anywhere on the path but the destination cell, I would
expect it to appear as a blockage (though "no room" is probably not the
best diagnostic). However, I would agree that an enemy unit should be
allowed in the destination cell, and that, if detected there, a move-to
(with nearness set to 1, or 'fire-range'/'attack-range' if we want to be
smarter) should be set.

> the enemy unit and then prompt for instructions what to do. Alternatively,
> one could make it possible to schedule a move + overrun task this way.

I would worry about accidental clicks triggering this automatic
behavior, though I agree that it would be quite nice and fluid to set
the overrun and then push the abovementioned move-to ahead of it.

Eric

  reply	other threads:[~2004-06-06 13:33 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-30  2:52 build doctrine question/bug? Tom Schaub
2004-05-30  3:28 ` Eric McDonald
2004-06-02 20:30   ` Consumption-per-fire? Elijah Meeks
2004-06-04 21:44     ` Consumption-per-fire? Hans Ronne
2004-06-04 22:15       ` Consumption-per-fire? Elijah Meeks
2004-06-04 22:50         ` Consumption-per-fire? Hans Ronne
2004-06-04 23:04           ` Consumption-per-fire? Elijah Meeks
2004-06-04 23:19             ` Consumption-per-fire? Eric McDonald
2004-06-05  3:37               ` Consumption-per-fire? Elijah Meeks
2004-06-05  4:22                 ` Consumption-per-fire? Eric McDonald
2004-06-05  8:11                   ` Consumption-per-fire? Hans Ronne
2004-06-05  8:22                     ` Consumption-per-fire? Hans Ronne
2004-06-05 13:10                     ` Consumption-per-fire? Eric McDonald
2004-06-05 15:03                       ` Consumption-per-fire? Hans Ronne
2004-06-05 15:57                         ` Consumption-per-fire? Elijah Meeks
2004-06-05 17:05                           ` Consumption-per-fire? Hans Ronne
2004-06-05 18:37                           ` Overrun actions (was: Consumption-per-fire?) Hans Ronne
2004-06-05 22:30                             ` Elijah Meeks
2004-06-05 22:54                             ` Jim Kingdon
2004-06-06  0:31                               ` Hans Ronne
2004-06-06  0:59                                 ` Elijah Meeks
2004-06-06  2:21                                   ` Hans Ronne
2004-06-06  6:17                             ` Eric McDonald
2004-06-06  7:39                               ` Hans Ronne
2004-06-06 13:33                                 ` Eric McDonald [this message]
2004-06-05 17:15                         ` Consumption-per-fire? Eric McDonald
2004-06-05 19:30                           ` Consumption-per-fire? Hans Ronne
2004-06-06  6:32                             ` Consumption-per-fire? Eric McDonald
2004-06-06  4:34                           ` Consumption-per-fire? mskala
2004-06-06  6:52                             ` Consumption-per-fire? Eric McDonald
2004-06-06  7:13                             ` Consumption-per-fire? Lincoln Peters
2004-06-05  7:05               ` Consumption-per-fire? Hans Ronne
2004-06-04 23:12           ` Consumption-per-fire? Eric McDonald
2004-06-04 22:22 ` build doctrine question/bug? Hans Ronne
2004-06-05 17:08 ` Hans Ronne

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=1086528611.1485.227.camel@localhost.localdomain \
    --to=mcdonald@phy.cmich.edu \
    --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).