From: Elijah Meeks <elijahmeeks@yahoo.com>
To: Hans Ronne <hronne@comhem.se>
Cc: xconq7@sources.redhat.com
Subject: Re: Overrun actions (was: Consumption-per-fire?)
Date: Sat, 05 Jun 2004 22:30:00 -0000 [thread overview]
Message-ID: <20040605223022.2964.qmail@web13123.mail.yahoo.com> (raw)
In-Reply-To: <l03130305bce7b9ad62f3@[212.181.162.155]>
> I think that the second solution might be more
> logical, but it would change
> the interface behaviour. You would no longer be able
> to fire at a unit by
> clicking on it in move mode. This is perhaps not
> much of a problem since
> putting the cursor over the target and hitting "f"
> is just as easy (in
> fact, I think it is even easier than doing the
> clickaton). And you have to
> do this anyway if you want to fire from a distance,
> since clicking on the
> target only works for adjacent units.
>
> If we remove overrun by fire, units that can also
> attack will still be able
> to overrun by attack. One example of this is the
> godzillas in your game.
> They will use melee attacks if the overrun by fire
> code is commented out.
> Everything then works as expected.
The second option sounds like the most sensible. I
don't see much sense in overrun by fire, and it
doesn't correlate to any strategic games that I've
ever played.
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
next prev parent reply other threads:[~2004-06-05 22:30 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 [this message]
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
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=20040605223022.2964.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).