public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Hans Ronne <hronne@comhem.se>
Cc: bboett@adlp.org, <xconq7@sources.redhat.com>
Subject: Re: fighters fighting without ammo
Date: Sat, 13 Dec 2003 19:55:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0312130935580.6182-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <l03130303bc00a1047c50@[212.181.162.155]>

Hi Hans, Bruno, others,

On Sat, 13 Dec 2003, Hans Ronne wrote:

> One easy way to achieve this is to extend the default unit tactical-range,
> which is where the action-reaction code takes over. Right now it is set to
> 4 cells, which means that the AI will attack anything that comes within 4
> cells of one of its units. This could easily be changed to 20 cells, for
> example. I think there would be a negative effect on performance, but I
> haven't tested this rigourously.

I have set this value higher for units in Bellum Aeternum. In the 
case of aircraft, it is significantly higher. I think it has 
adversely affected performance some, especially once the game 
reaches a point where there are lots of units clogged up on the 
tips of peninsulae (a problem which is alleviated by the new 
path-finding). But the AI is better at coming after targets than 
in the standard game, IMO.

  Regards,
   Eric

  reply	other threads:[~2003-12-13 14:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-07 16:07 Kenneth Gonsalves
2003-12-07 16:54 ` Lincoln Peters
2003-12-07 17:36 ` Jim Kingdon
2003-12-07 18:13   ` Skeezics Boondoggle
2003-12-07 23:54     ` Bruno Boettcher
2003-12-13  5:11       ` Eric McDonald
2003-12-13 10:57         ` Bruno Boettcher
2003-12-13 12:02           ` Hans Ronne
2003-12-13 19:55             ` Eric McDonald [this message]
2003-12-13 20:02             ` Jim Kingdon
2003-12-14  4:33               ` Hans Ronne
2003-12-08  8:19     ` Kenneth Gonsalves
2003-12-13  4:59     ` Eric McDonald

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.0312130935580.6182-100000@leon.phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --cc=bboett@adlp.org \
    --cc=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).