From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Peter Garrone <pgarrone@acay.com.au>
Cc: xconq7@sources.redhat.com, Hans Ronne <hronne@comhem.se>
Subject: Re: plan_transport
Date: Sun, 07 Dec 2003 02:02:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0312061949250.32155-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <20031206224329.GA473@leonardo>
Hi Peter, Hans, others,
I agree with most of your points.
On Sun, 7 Dec 2003, Peter Garrone wrote:
> - Something needs to be added to the ai code so that it can distinguish
> a simple ferry from something offensive, like an aircraft carrier or
> bireme/trireme. This is asking a lot but perhaps some simple
> heuristic could fix this. So a bireme would not go onto
> PLAN_TRANSPORT, but instead grab an archer to help it in sea-battles.
Perhaps this could be an additional U_PROP or UU_TABLE rather than
an AI heuristic. That way the game designer has the flexibility
to designate units in some 'ai-occupant-helps-transport' table.
Another thing that I have been thinking about for a couple of
months now is whether 'ai-peace-garrison' and 'ai-war-garrison'
are really the best ways to go about specifying occupant/transport
recommendations to the AI. I think that perhaps these should be
TableUU things, so that the AI (with proper coding added) can be
more discriminating about which units to garrison with.
> - consideration could be given to implementing refueling behavior,
> a boring detail for the human player,
> while extending the pathfinding state space.
Sounds good.
> This is my "wishlist". I will attempt to implement it in stages, so
> that a partial implementation may suffice for a 7.5 release, comments
> invited,
Thanks,
Eric
next prev parent reply other threads:[~2003-12-07 0:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 0:59 plan_transport Peter Garrone
2003-12-07 2:02 ` Eric McDonald [this message]
2003-12-08 0:28 ` plan_transport Peter Garrone
2003-12-08 1:23 ` plan_transport Hans Ronne
2003-12-07 8:26 ` plan_transport Hans Ronne
2003-12-08 0:50 ` plan_transport Peter Garrone
2003-12-08 3:26 ` plan_transport Hans Ronne
2003-12-08 3:55 ` plan_transport 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=Pine.LNX.4.44.0312061949250.32155-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=hronne@comhem.se \
--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).