From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Feature Request: Advance Prohibits Advance
Date: Sun, 05 Sep 2004 19:43:00 -0000 [thread overview]
Message-ID: <413B48C5.8080608@phy.cmich.edu> (raw)
In-Reply-To: <20040905164141.65066.qmail@web13124.mail.yahoo.com>
Elijah Meeks wrote:
> 1) It's more complicated. Not having seen the code, I
> don't know how much, but a simple shut-off switch
> would, I think be straightforward.
You are possibly right in this regard. I'll think some more about it.
>It would also
> allow the game designer to simulate much of what
> you're talking about, he'd just have to create a few
> more techs, so that you're getting the same tech, only
> cheaper,
I see. So are you going to race Lincoln to 10000 advances to win an
additional donut? :-)
> 2) The AI doesn't choose research very well. Really,
> this is for the AI, because a player will probably
> focus, anyway, while the AI will choose its research
> haphazardly and I wouldn't be surprised to see it
> short-circuiting by researching an almost-infinite-rp
> tech.
Ah ha. Trying to make the AI look like it has a brain? That is also the
mark of a seasoned Xconq developer.
> Of course, if I'm wrong about these points, which is a
> decent possibility given my lack of familiarity with
> the research or AI code, then by all means I'd prefer
> a more featured implementation.
No. I think you made valid points. You are the one actually using
advances. Like I said, I have barely touched the stuff. I'll think some
more about it.
But, right now, I am about to add support for prefix args to the SDL
interface.
Eric
next prev parent reply other threads:[~2004-09-05 17:11 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040827050942.5961.qmail@web13122.mail.yahoo.com>
2004-08-27 17:09 ` CXP??? Eric McDonald
2004-08-28 2:51 ` CXP??? Elijah Meeks
2004-08-28 3:47 ` Multiple Image Use Elijah Meeks
2004-08-28 4:02 ` Eric McDonald
2004-08-28 4:33 ` Elijah Meeks
2004-09-01 7:30 ` Standard Game Graphics Elijah Meeks
2004-09-01 16:18 ` Jim Kingdon
2004-09-01 18:30 ` Eric McDonald
2004-09-02 1:43 ` Elijah Meeks
2004-09-02 4:24 ` Eric McDonald
2004-09-03 2:30 ` Jim Kingdon
2004-09-03 3:01 ` Elijah Meeks
2004-09-03 3:17 ` Eric McDonald
2004-09-03 5:10 ` Elijah Meeks
2004-09-03 5:11 ` Jim Kingdon
2004-09-03 6:10 ` Jim Kingdon
2004-09-03 17:18 ` Changing the Standard Game Elijah Meeks
2004-09-04 2:06 ` Eric McDonald
2004-09-04 17:46 ` Lincoln Peters
2004-09-05 1:48 ` Eric McDonald
2004-09-05 6:02 ` Feature Request: Advance Prohibits Advance Elijah Meeks
2004-09-05 16:25 ` Eric McDonald
2004-09-05 16:41 ` mskala
2004-09-05 16:54 ` Eric McDonald
2004-09-05 17:11 ` mskala
2004-09-05 17:01 ` Elijah Meeks
2004-09-05 16:48 ` Elijah Meeks
2004-09-05 19:43 ` Eric McDonald [this message]
2004-09-05 16:50 ` mskala
2004-09-05 16:55 ` Eric McDonald
2004-09-05 16:55 ` Lincoln Peters
2004-09-05 17:01 ` Elijah Meeks
2004-09-05 19:52 ` Jim Kingdon
2004-09-05 20:16 ` Eric McDonald
2004-09-05 19:58 ` Lincoln Peters
2004-09-05 20:15 ` Elijah Meeks
2004-09-05 15:52 ` Changing the Standard Game Lincoln Peters
2004-09-05 16:36 ` Eric McDonald
2004-09-05 20:09 ` Jim Kingdon
2004-09-05 20:14 ` Jim Kingdon
2004-09-05 20:40 ` Elijah Meeks
2004-09-05 22:09 ` Eric McDonald
2004-09-03 23:11 ` Standard Game Graphics 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=413B48C5.8080608@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=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).