public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Elijah Meeks <elijahmeeks@yahoo.com>
To: Hans Ronne <hronne@comhem.se>, "Henry J. Cobb" <hcobb@io.com>
Cc: xconq7@sources.redhat.com
Subject: Re: The battle for Taiwan
Date: Wed, 28 Jul 2004 23:17:00 -0000	[thread overview]
Message-ID: <20040728224755.64469.qmail@web13122.mail.yahoo.com> (raw)
In-Reply-To: <l03130300bd2da39303d3@[212.181.162.155]>

A slightly more crude manner to achieve this is to
build seed units, which can lose a material every turn
and starves when it runs out of material.  By setting
its wreck-type to the unit you want (And changing the
see-chances so that it is not visible to any other
players), you can set the material to be your delay. 
You can even change the starve hp so that there's some
variable to its appearance (A .25 hp loss to a 1 hp
unit would then appear sometime during the 1-4+ turns
after running out of its timer material).

It's crude, like I said, but I like it.  If you want a
group to appear at the same time, just set the
detonation option for one unit and have it only blow
up the seed units.

And I'd love to see a battle for Taiwan scenario,
myself.

Elijah

--- Hans Ronne <hronne@comhem.se> wrote:

> >This would be a fun scenario to build someday.
> >
> >Is there some option for delayed reinforcements so
> the American carriers
> >don't show up until the second month?
> 
> Yes. See the Gettysburg game for an example.
> 
> Hans
> 
> 
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail

  reply	other threads:[~2004-07-28 22:47 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 [this message]
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
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=20040728224755.64469.qmail@web13122.mail.yahoo.com \
    --to=elijahmeeks@yahoo.com \
    --cc=hcobb@io.com \
    --cc=hronne@comhem.se \
    --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).