From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Peter Garrone <pgarrone@acay.com.au>
Cc: xconq7@sources.redhat.com
Subject: Re: Standard game problems in windows (20031214) version
Date: Wed, 17 Dec 2003 16:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0312171125020.7552-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <20031217075755.GB819@leonardo>
Hi Peter, others,
On Wed, 17 Dec 2003, Peter Garrone wrote:
> > I don't think we should automatically move in any direction other
> > than that specified by the user. Second-guessing the player is
> > generally not a good idea.
>
> I disagree. The path-finding implies that a move is possibly different.
> An aircraft, directed to go from A to B, might fly to C to get some
> fuel.
I don't entirely disagree when one is precomputing a path, though
I still think that one must think about how tight do you want to
keep the fuel budget when determining a path. If you say that a
unit should refuel once it has traversed enough path to use 50% of
its fuel, then you are quite possibly producing a very inefficient
path, even if it is the only one that is essentially guaranteed to
be safe.
The case I was looking at was: what happens if we get a certain
distance along a path and find that our primary refueling
opportunity might have vanished? And my answer is the same as
Jim's: the user needs to decide. Obviously if the
refueling point is on the path and can be reached/utilized, then
you let the automatic movement continue without user intervention;
I certainly was not disputing that....
Regards,
Eric
next prev parent reply other threads:[~2003-12-17 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 14:28 Martin Fehlhaber
2003-12-16 16:42 ` Hans Ronne
2003-12-16 17:18 ` Eric McDonald
2003-12-16 19:14 ` Bruno Boettcher
2003-12-16 22:55 ` Eric McDonald
2003-12-16 23:09 ` Bruno Boettcher
2003-12-17 10:27 ` Jim Kingdon
2003-12-17 10:28 ` Peter Garrone
2003-12-17 15:37 ` Peter Garrone
2003-12-17 16:54 ` Eric McDonald [this message]
2003-12-17 10:42 ` 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.0312171125020.7552-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).