From: Hans Ronne <hronne@comhem.se>
To: xconq7@sources.redhat.com
Subject: More Xconq bug fixes
Date: Thu, 19 Aug 2004 15:32:00 -0000 [thread overview]
Message-ID: <l03130303bd4a54ff94c6@[212.181.162.155]> (raw)
My latest bunch of bug fixes has been checked in. Most of them are
concerned with how the kernel and AI code deal with non-mobile units that
can fire. This kind of unit is not very common in existing games, and was
therefore not handled correctly.
One new feature is the ability to set maximal and minimal sizes for
advanced units (size-min and size-max). This is useful if you want to avoid
runaway unit growth or units starving to death.
I have not dealt with the problems that were recently discussed on the list
yet, except for some preliminary moves, such as adding code for unit view
validation and clearance (still unused).
Hans
next reply other threads:[~2004-08-19 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 15:32 Hans Ronne [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-06 7:27 Hans Ronne
2002-07-24 22:30 More xconq " Hans Ronne
2002-07-22 4:55 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='l03130303bd4a54ff94c6@[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).