From: Eric McDonald <mcdonald@phy.cmich.edu>
To: mskala@ansuz.sooke.bc.ca
Cc: Elijah Meeks <elijahmeeks@yahoo.com>,
Xconq list <xconq7@sources.redhat.com>
Subject: Re: Feature Request: Advance Prohibits Advance
Date: Sun, 05 Sep 2004 16:55:00 -0000 [thread overview]
Message-ID: <413B44E9.1060903@phy.cmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.21.0409051235040.29256-100000@diamond.ansuz.sooke.bc.ca>
mskala@ansuz.sooke.bc.ca wrote:
> On Sun, 5 Sep 2004, Eric McDonald wrote:
> I looked it up in the manual, and it turns out there's an
> advance-consumption-per-rp table which (assuming it's implemented) does
> more or less what I thought would be necessary. To force the side to
> choose ground or space battles, you have an advance for each which
> requires a point of "research commitment", and you only get one point of
> that, so you have to choose one or the other. To force choosing one or
> the other first, but eventually allow them both, make it require 100
> points of research commitment, give the side 100 points, but then make it
> hard to produce additional points... so they can eventually make another
> 100 and take the other path, but it'll take a while.
This is an interesting thought. Among other things, it shows me that you
are fit to be considered a "seasoned" Xconq game designer, because of
demonstrated aptitude at twisting existing features to mimic
non-existent features. :-)
> The "advances speed up other advances" thing could also be done easily
> with materials.... having "Formal Logic" increases your production of
> "journal papers", which are needed for other advances.
Depends on which journal, and who the author(s) and referee were. For
some, I think formal logic serves as a detriment....
Eric
next prev parent reply other threads:[~2004-09-05 16:55 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
2004-09-05 16:50 ` mskala
2004-09-05 16:55 ` Eric McDonald [this message]
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=413B44E9.1060903@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=elijahmeeks@yahoo.com \
--cc=mskala@ansuz.sooke.bc.ca \
--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).