From: Elijah Meeks <elijahmeeks@yahoo.com>
To: Lincoln Peters <sampln@sbcglobal.net>,
Xconq list <xconq7@sources.redhat.com>
Subject: Re: First stable version of improved ai_plan_research
Date: Thu, 09 Sep 2004 07:30:00 -0000 [thread overview]
Message-ID: <20040908222010.93147.qmail@web13126.mail.yahoo.com> (raw)
In-Reply-To: <1094671955.4338.71459.camel@localhost>
> A perfect AI would also have the following abilities
> for selecting
> advances, all of which are (as far as I can tell)
> impossible to
> implement in its current form:
>
You could add GDL support for this by letting the
Designers write weighted tables. Then someone could
define "Air Focused", "Space Focused", "Ground
Focused" and "Magic Focused" as each having different
values for the various techs and units (These same
values being integrated into the previously
brainstormed AI build recommendation tables) and each
could be randomly assigned per side (Or selected from
the side selection list, with a column next to the AI
column).
It would still be useful to have an
advance-precludes-advance table, in those cases when
two advances are actually in opposition to each other.
The two examples I can think of off the top of my
head are the different styles of Magic in Opal (You
shouldn't be able to research both Life and Death
magic, or Sorcery and Chaos) and when the advances
represent different ways to implement a new technology
(So that, instead of having a "3rd Generation Tank"
tech, you have a "No-Frills 3rd Generation Tank",
"Typical 3rd Generation Tank" and a "Cutting Edge 3rd
Generation Tank") so that different sides end up
fielding similar but different vehicles (All of which,
after finding whichever tech they chose, can then
research 4th Generation Tank techs).
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
next prev parent reply other threads:[~2004-09-08 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 22:20 Lincoln Peters
2004-09-09 7:30 ` Elijah Meeks [this message]
2004-09-10 4:03 ` Eric McDonald
2004-09-09 13:39 ` Andreas Bringedal
2004-09-09 16:39 ` Lincoln Peters
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=20040908222010.93147.qmail@web13126.mail.yahoo.com \
--to=elijahmeeks@yahoo.com \
--cc=sampln@sbcglobal.net \
--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).