public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Lincoln Peters <sampln@sbcglobal.net>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: Hans Ronne <hronne@comhem.se>,
	Elijah Meeks <elijahmeeks@yahoo.com>,
	 Xconq list <xconq7@sources.redhat.com>
Subject: Re: The battle for Taiwan
Date: Thu, 29 Jul 2004 02:25:00 -0000	[thread overview]
Message-ID: <1091066223.3196.1049.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0407282015280.30335-100000@leon.phy.cmich.edu>

On Wed, 2004-07-28 at 17:18, Eric McDonald wrote:
> You guys are a bit twisted, IMO. :-)
> Just use the existing auto-upgrade mechanism with an unseen unit 
> that grows in size at the rate of one size point per turn (don't 
> require any materials for the growth). Once the target size/turn 
> is achieved, then auto-upgrade to a seen reinforcement unit.

Except that, if we do it your way, there is no variability in when the
units appear.  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.  Using your method, the barbarians
would all appear simultaneously.


I think that what Xconq should really have is a mechanism for generating
independent units that appear in random places at random times. 
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).

In knights.g, or a derivative thereof, I might use such a mechanism to
cause monsters to appear semi-randomly.  Lowly monsters such as goblins
are pretty weak, and so could appear at any time without presenting an
overwhelming challenge.  A great red wyrm, on the other hand, could end
the game before it even begins if it appears before each side has at
least a few 20th-level knights.  And above all, such creatures should
never randomly appear within areas that have been explored by one or
more sides (since such areas are civilized and clear of monsters),
although a monster could randomly appear in an unexplored area and move
into an explored area.

---
Lincoln Peters
<sampln@sbcglobal.net>

This generation doesn't have emotional baggage.  We have emotional moving vans.
		-- Bruce Feirstein

  reply	other threads:[~2004-07-29  1:56 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 [this message]
2004-08-01 16:53                 ` Eric McDonald
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=1091066223.3196.1049.camel@localhost \
    --to=sampln@sbcglobal.net \
    --cc=elijahmeeks@yahoo.com \
    --cc=hronne@comhem.se \
    --cc=mcdonald@phy.cmich.edu \
    --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).