public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "Henry J. Cobb" <hcobb@io.com>
To: "Eric McDonald" <mcdonald@phy.cmich.edu>
Cc: "Henry J. Cobb" <hcobb@io.com>, xconq7@sources.redhat.com
Subject: Re: Issues with Time: Combat through the ages.
Date: Wed, 28 Jul 2004 18:31:00 -0000	[thread overview]
Message-ID: <4870.68.126.82.218.1091039135.squirrel@webmail.io.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0407281354120.28251-100000@leon.phy.cmich.edu>

Eric McDonald wrote:
> On Wed, 28 Jul 2004, Henry J. Cobb wrote:
>> Infantry should be cheaper to build than armor.
>
> How much cheaper would you suggest? And why?

Infantry production needs to be continued into the Postmodern era for
helicopter operations.  (And Calvary needs to be continued into Metros so
you've got something other than just infantry during this time.)

Perhaps have a best ground combatant cost of say 6 turns and the mix
changes and improves over time.  (Infantry and armor could both be at 6
and Cavalry at 8.)

> Also, did you ever figure out what more reasonable capture chances
> would be for the Galaxy 2 game?

The problem is sequencing rather that percentages.

The human player should not be allowed to just sit on his worlds and come
out and snipe as needed.

Perhaps allow the enemy ships to bombard the planets and eliminate the
ships that are parked on the landing field.

-- 
Henry J. Cobb's Completely Unofficial list of GURPS Vehicle Builder fixes
and workarounds.  http://www.io.com/~hcobb/gurps/gvb_faq.txt

  reply	other threads:[~2004-07-28 18:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 17:56 Henry J. Cobb
2004-07-28 18:25 ` Eric McDonald
2004-07-28 18:31   ` Henry J. Cobb [this message]
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
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=4870.68.126.82.218.1091039135.squirrel@webmail.io.com \
    --to=hcobb@io.com \
    --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).