From: Elijah Meeks <elijahmeeks@yahoo.com>
To: xconq7@sources.redhat.com
Subject: AI Motivation for non-combat units
Date: Tue, 13 Jul 2004 23:08:00 -0000 [thread overview]
Message-ID: <20040713230137.4816.qmail@web13125.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0407131504350.20762-100000@leon.phy.cmich.edu>
I'm in the middle of implementing Carrier Air Wings in
AWLS, and I just wondered, is it worth it? Once I'm
done, carriers will no longer have an Attack or Fire
Attack, so doesn't this mean the AI won't use them as
a combat unit? I know it doesn't deal with transports
well, but if I allow for disembarking of Carrier Air
Wings (A somewhat logical event), won't it just bump
into some piece of land somewhere and dump them right
next to a Crack Reinforced Armor Group?
Any hints on how to tag a Carrier so that the AI deals
with it well after it's lost its attack? Should I
leave it with a minor Attack or Fire Attack?
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
next prev parent reply other threads:[~2004-07-13 23:01 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1088896371.19592.ezmlm@sources.redhat.com>
2004-07-03 23:21 ` Just say no to bungee paratroopers Henry J. Cobb
2004-07-03 23:55 ` Eric McDonald
2004-07-04 0:55 ` Hans Ronne
2004-07-04 1:39 ` Eric McDonald
2004-07-04 3:17 ` Hans Ronne
2004-07-04 1:14 ` Jim Kingdon
2004-07-04 3:37 ` Henry J. Cobb
2004-07-04 6:13 ` Henry J. Cobb
2004-07-04 15:13 ` Hans Ronne
2004-07-04 18:01 ` Jim Kingdon
2004-07-04 21:38 ` Hans Ronne
2004-07-04 21:57 ` mskala
2004-07-05 3:30 ` Hans Ronne
2004-07-09 1:17 ` Henry J. Cobb
[not found] ` <40EDFCDE.9000902@phy.cmich.edu>
2004-07-09 3:37 ` Henry J. Cobb
[not found] ` <40EEAD66.50109@phy.cmich.edu>
2004-07-09 16:02 ` Henry J. Cobb
2004-07-09 16:10 ` Hans Ronne
2004-07-10 4:38 ` Henry J. Cobb
2004-07-12 1:25 ` Carrier groups Henry J. Cobb
2004-07-12 3:27 ` Hans Ronne
2004-07-12 7:00 ` Henry J. Cobb
2004-07-09 16:47 ` Just say no to bungee paratroopers Jim Kingdon
2004-07-09 16:54 ` Elijah Meeks
2004-07-09 17:00 ` Wrecking Issues Elijah Meeks
2004-07-09 17:16 ` Eric McDonald
2004-07-10 21:40 ` Eric McDonald
2004-07-09 17:45 ` AI Help Elijah Meeks
2004-07-09 18:15 ` Hans Ronne
2004-07-09 18:26 ` Eric McDonald
2004-07-09 19:03 ` Elijah Meeks
2004-07-09 19:45 ` Side Selection Bugs Elijah Meeks
2004-07-09 19:46 ` Hans Ronne
2004-07-11 1:47 ` AWLS: Korea 2006 Eric McDonald
2004-07-11 4:16 ` Elijah Meeks
2004-07-13 2:40 ` More Feedback on " Eric McDonald
2004-07-13 3:48 ` Elijah Meeks
2004-07-13 4:42 ` Eric McDonald
2004-07-13 17:20 ` Elijah Meeks
2004-07-13 17:28 ` Combat result tracking? Elijah Meeks
2004-07-13 17:46 ` Eric McDonald
2004-07-13 18:10 ` Hans Ronne
2004-07-13 18:57 ` Eric McDonald
2004-07-13 19:10 ` Elijah Meeks
2004-07-13 20:23 ` Eric McDonald
2004-07-13 23:08 ` Elijah Meeks [this message]
2004-07-14 0:33 ` AI Motivation for non-combat units Hans Ronne
2004-07-13 23:01 ` Combat result tracking? Hans Ronne
2004-07-14 1:04 ` Skeezics Boondoggle
2004-07-14 1:20 ` Eric McDonald
2004-07-14 15:27 ` Counterfire Elijah Meeks
2004-07-15 16:04 ` Counterfire Eric McDonald
2004-07-11 9:44 ` AI Help Jim Kingdon
2004-07-11 10:08 ` Hans Ronne
2004-07-12 18:07 ` Jim Kingdon
2004-07-09 18:09 ` Just say no to bungee paratroopers Hans Ronne
2004-07-11 6:01 ` Jim Kingdon
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=20040713230137.4816.qmail@web13125.mail.yahoo.com \
--to=elijahmeeks@yahoo.com \
--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).