From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Hans Ronne <hronne@comhem.se>
Cc: xconq7@sources.redhat.com
Subject: Re: New Action: change-type
Date: Wed, 07 Jan 2004 04:31:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0401062322480.7057-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <l03130301bc2133e8c6b3@[212.181.162.155]>
On Wed, 7 Jan 2004, Hans Ronne wrote:
> > I have plans to extend Xconq to allow automatic type changes
> >upon such triggers as a unit reaching a certain size or gaining
> >sufficient amounts of one or more materials.
>
> This is what I had in mind for the advances game. A time.g-like upgrade
> path tribe->village->town->city->metropolis that would be conditioned both
> on size and the availability of certain advances and/or facilities. What we
I want this for Bellum as well, particularly the upgrade keyed on
size. That way I wouldn't have to waste a material slot for "city
points" (I think the material is called "timer" in Specula). Also,
it would mean that we wouldn't have to teach the AI about manual
change-type right away, at least not for Advances or Bellum....
> would need for that is code in run_turn_start that upgrades (or downgrades)
> units that fulfil certain conditions.
OK. That is where I will look then. I was just going to search
around until I found wherever the advanced unit size increment was
called and put in the new auto type change call somewhere after
that (unless I saw reason to do otherwise).
Eric
next prev parent reply other threads:[~2004-01-07 4:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 2:40 Eric McDonald
2004-01-07 2:47 ` Erik Jessen
2004-01-07 3:30 ` Eric McDonald
2004-01-07 2:51 ` Lincoln Peters
2004-01-07 4:04 ` Hans Ronne
2004-01-07 4:31 ` Eric McDonald [this message]
2004-01-07 20:08 ` klaus schilling
2004-01-07 20:17 ` Eric McDonald
2004-01-07 20:26 ` Hans Ronne
2004-01-07 20:47 ` Eric McDonald
2004-01-07 21:22 ` Eric McDonald
2004-01-08 6:28 ` Erik Jessen
2004-01-08 16:26 ` Eric McDonald
2004-01-10 5:49 ` Erik Jessen
2004-01-10 16:42 ` Eric McDonald
2004-01-10 17:57 ` Hans Ronne
2004-01-10 18:59 ` HW requirements Erik Jessen
2004-01-10 19:44 ` Hans Ronne
2004-01-10 23:31 ` klaus schilling
2004-01-11 0:25 ` Erik Jessen
2004-01-11 3:44 ` Jim Kingdon
2004-01-11 7:25 ` Erik Jessen
2004-01-11 7:45 ` Eric McDonald
2004-01-11 7:52 ` Erik Jessen
2004-01-11 21:19 ` Jim Kingdon
2004-01-11 0:31 ` Hans Ronne
2004-01-08 3:48 ` New Action: change-type Hans Ronne
2004-01-08 4:28 ` Eric McDonald
2004-01-08 6:39 ` Hans Ronne
2004-01-08 16:46 ` Eric McDonald
2004-01-07 12:46 Bill Macon
2004-01-07 13:37 ` Mark A. Flacy
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=Pine.LNX.4.44.0401062322480.7057-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--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).