From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Peter Garrone <pgarrone@acay.com.au>
Cc: xconq7@sources.redhat.com
Subject: Re: pathfinding refueling
Date: Sat, 20 Dec 2003 22:50:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0312201046270.20391-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <20031220065220.GD1667@leonardo>
On Sat, 20 Dec 2003, Peter Garrone wrote:
> These scenarios are not from any game in the library.
Correct. And I did not claim they were. Nonetheless, they are
valid hypothetical scenarios.
(And actually, if you look at the amount of c and f1 that are
available to land units in Bellum, you might recognize how close
this is to the fuel1 and fuel2 of the proposed scenarios.)
> No rational game would have
> separate sorts of extremely limited range fuels refueled from different
> points like this.
So I guess Bellum isn't rational....
Please let me know how you would do things differently.
> In such situations the player guides the unit to refueling points
> (wo)manually and presses t for take.
The player could do that if he or she wished to, but as I stated,
the player was requesting a final destination B from the
pathfinder. So, the question is, how would the pathfinder deal
with this?
>This sort of combat situation where
> fuel etc is short should not be automated
How do you prevent it from being automated if automation was
requested?
> But if the requirement were that all such situations should be
> automated, then the approach I have advocated would be in error.
If the player requests automation, then automation is indeed a
requirement. (And this is no different than present behavior.)
> that is not what I am trying to achieve anyway. I dont think its what
> you would really like either, Eric.
In a scenario 1-like situation, I would probably move the unit by
hand. In a scenario 2-like situation, I might let the automation
do the work to a avoid the "clickathon".
> player just does what is done now. But the approach I am outlining
> simply reduces the micromanagement associated with
> 1) ferrying aircraft from point of production to the front.
As Bruno would probably mention, standing orders also do this.
(Though they take some effort to set up initially).
But, I agree, that your approach would likely work well in dealing
with this case.
> 2) combat situations where aircraft have to continuously get fuel almost
> every turn.
It is less clear how your proposal would help here. I think that
the second scenario (or variations thereof) might show up fairly
frequently in this case.
> I have spent hours on all these emails. I would rather just code up my
> approach now thanks. Fat chance.
So then code it up. I already told you that I am not stopping you
(I cannot stop you). Just don't expect me to check it in; I think
your proposed solution is a bit narrow-minded in some cases.
next prev parent reply other threads:[~2003-12-20 16:09 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 [this message]
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
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=Pine.LNX.4.44.0312201046270.20391-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=pgarrone@acay.com.au \
--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).