public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "Mark A. Flacy" <mflacy1@comcast.net>
To: xconq7@sources.redhat.com
Subject: Re: pathfinding refueling
Date: Sun, 21 Dec 2003 07:27:00 -0000	[thread overview]
Message-ID: <87zndmq4mj.fsf@flacy.home.flacy> (raw)
In-Reply-To: <20031220224534.GB725@leonardo>

>>>>> "Peter" == Peter Garrone <pgarrone@acay.com.au> writes:
Peter> 
Peter> But none of the units in bellum use more than one sort of fuel.

Eh?  *Every* unit in bellum uses a fuel and "command and control" points to
perform movement.  They *both* constrain the maximum possible distance that
a unit can move.

And from my experiences with bellum, "c" is a bigger constraint than fuel
for non-aircraft units.  My "clickathons" are due to "c" rather than "f1"
or "f2".

When I send units across the map, there is NOTHING more irritating than it
stopping because it ran out of "c" along the way to ask me what to do.  I
still want the #$@!!$! unit to move across the map to same place that I
told it to move to earlier.

I only want units to stop if they are low on something that will kill
them.  That's fuel for aircraft as well as the "s" for everything else.  If
they run out of something else along the way, they can wait for me to
establish a supply line hopefully without forgetting the original mission.

That's what happens when real military units run out of fuel; you continue
with the previous mission unless you've been told differently.


-- 
 Mark A. Flacy
 Any opinions expressed above are my own.  Any facts expressed above
 would imply that I know what I'm writing about.  Sometimes, I do!
"Yes, but every time I try to see things your way, I get a headache."
  --Unknown

  reply	other threads:[~2003-12-21  2:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031218063340.GA733@leonardo>
2003-12-18 21:54 ` Eric McDonald
2003-12-19  1:43   ` Peter Garrone
2003-12-19  4:12     ` Eric McDonald
2003-12-20  6:44       ` Peter Garrone
2003-12-20 23:00         ` pathfinding refueling 2 (was Re: pathfinding refueling) Eric McDonald
2003-12-20  6:43     ` pathfinding refueling Eric McDonald
2003-12-20  6:43       ` Peter Garrone
2003-12-20 22:50         ` Eric McDonald
2003-12-20 23:00           ` Hans Ronne
2003-12-21  2:36             ` Peter Garrone
2003-12-20 23:21           ` Peter Garrone
2003-12-21  7:27             ` Mark A. Flacy [this message]
2003-12-20  6:43     ` Hans Ronne
2003-12-20 16:09       ` Peter Garrone
2003-12-20 17:08         ` Hans Ronne
2003-12-20 23:31           ` Peter Garrone
2003-12-21  7:22             ` Hans Ronne
2003-12-21 23:07               ` Peter Garrone
2003-12-22 11:46                 ` Hans Ronne
2003-12-23  4:08                 ` Lincoln Peters
2003-12-23  4:25                   ` Peter Garrone
2003-12-17 10:28 Peter Garrone
2003-12-18  5:30 ` Eric McDonald
2003-12-19  0:12 ` Jim Kingdon
2003-12-20 11:55   ` Peter Garrone

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=87zndmq4mj.fsf@flacy.home.flacy \
    --to=mflacy1@comcast.net \
    --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).