From: Hans Ronne <hronne@comhem.se>
To: xconq7@sources.redhat.com
Subject: Improved rearm and repair code
Date: Tue, 20 Jul 2004 00:45:00 -0000 [thread overview]
Message-ID: <l03130300bd22161ba2e5@[212.181.162.155]> (raw)
I have checked in the second part of the improved resupply code, which now
also works for rearm and repair tasks. The main difference from the old
code is that supply inlengths and outlengths (and repair ranges) now are
handled correctly. Thus, if supplies or repair can be obtained at som
distance from another unit, the AI will now move the unit in need to the
closest cell within the supply or repair range.
Hans
P.S. I have also fixed an annoying bug in the X11 interface which has been
there for as long as I can remember. Just in case somebody though this
interface was no longer maintained :-).
reply other threads:[~2004-07-20 0:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='l03130300bd22161ba2e5@[212.181.162.155]' \
--to=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).