From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: Hans Ronne <hronne@comhem.se>,
Elijah Meeks <elijahmeeks@yahoo.com>,
Xconq list <xconq7@sources.redhat.com>
Subject: Re: The battle for Taiwan
Date: Sun, 01 Aug 2004 16:53:00 -0000 [thread overview]
Message-ID: <41085FED.2070804@phy.cmich.edu> (raw)
In-Reply-To: <1091066223.3196.1049.camel@localhost>
Lincoln Peters wrote:
> Except that, if we do it your way, there is no variability in when the
> units appear.
I was proposing another way to address Henry Cobb's earlier question to
the list, which as far as I could tell, did not involve variability in
the turn of appearance. "My way" is essentially as twisted as the
Meeks-Ronne Method, and it was proposed in jest. Using the existing
mechanism ("appear", IIRC) is likely the best way to achieve what he wanted.
>If you want barbarian invaders to start appearing at
> random intervals but after at least 100 turns, you can add that
> randomness by using Elijah's method.
Yes, I am aware of that. I read his message.
For variability in the turn of appearance, Elijah's idea is quite novel
and creative. Good thinking, Elijah.
> I think that what Xconq should really have is a mechanism for generating
> independent units that appear in random places at random times.
I suggested that before (and not just for independent units), and I
believe you were the one who assumed that I meant random unit types as
well. The disucussion took place on the list last November or December,
if I am correct in the rememberance.
> Although in many cases, additional constraints would be required (it
> would rarely make sense for a barbarian horde to spontaneously appear
> adjacent to your capital city, for example).
IIRC, one thing I think I suggested to address this issue was starting
zones (such as countries). In the case of indep units, one could require
a minimum separation distance from any units belonging to a player side;
or, at least, that has been my private thinking on the issue, wrt
Wreckreation.
Eric
next prev parent reply other threads:[~2004-07-29 2:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 17:56 Issues with Time: Combat through the ages Henry J. Cobb
2004-07-28 18:25 ` Eric McDonald
2004-07-28 18:31 ` Henry J. Cobb
2004-07-28 18:38 ` The battle for Taiwan Henry J. Cobb
2004-07-28 18:45 ` Eric McDonald
2004-07-28 22:47 ` Hans Ronne
2004-07-28 23:17 ` Elijah Meeks
2004-07-29 0:18 ` Hans Ronne
2004-07-29 0:18 ` Elijah Meeks
2004-07-29 1:56 ` Eric McDonald
2004-07-29 2:25 ` Lincoln Peters
2004-08-01 16:53 ` Eric McDonald [this message]
2004-08-03 22:37 ` [xconq] My hacked up copy of time.g Henry J. Cobb
2004-08-04 0:15 ` Hans Ronne
2004-08-06 19:50 ` Hans Ronne
2004-08-04 0:48 ` Eric McDonald
2004-08-04 1:23 ` [xconq] My hacked up copy of time.g, 2nd attempt Henry J. Cobb
2004-08-05 3:33 ` [xconq] My hacked up copy of time.g Henry J. Cobb
[not found] ` <6988.68.126.82.218.1091675883.squirrel@webmail.io.com>
2004-08-05 5:29 ` Eric McDonald
2004-08-05 5:51 ` Henry J. Cobb
2004-08-05 7:02 ` Hans Ronne
2004-08-05 7:25 ` Henry J. Cobb
2004-08-05 14:52 ` Hans Ronne
2004-08-05 22:36 ` Eric McDonald
2004-08-04 1:23 ` Eric McDonald
2004-08-04 1:53 ` 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=41085FED.2070804@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=elijahmeeks@yahoo.com \
--cc=hronne@comhem.se \
--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).