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: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Marketing Xconq?
Date: Tue, 18 Nov 2003 02:34:00 -0000	[thread overview]
Message-ID: <1069120644.29637.83838.camel@odysseus.peterslan> (raw)
In-Reply-To: <Pine.LNX.4.44.0311172005060.23006-100000@leon.phy.cmich.edu>

On Mon, 2003-11-17 at 17:13, Eric McDonald wrote:
> Hello Eric,
> 
> On Mon, 17 Nov 2003, Dr Eric Edward Moore wrote:
> 
> > Eric McDonald <mcdonald@phy.cmich.edu> writes:
> > 
> > > Similarly, I think Xconq could benefit from a reinforcements 
> > > model, where forces simply appear at certain turns.
> > 
> > Like the "appear" unit property?  It's used in gettysburg.g
> 
> Similar, but "appear" is a unit property, and not a unit-type 
> property. When I wrote the above remark, I wasn't really thinking 
> in terms of pre-built scenarios, but something more general, as an 
> alternative (or complement) to creation/building. But, yes, I will 
> concede that a reinforcements model does exist in the sense 
> that you mention.

It sounds like you're talking about random units being created at random
places on the map for random sides, although none of those are likely
meant to be 100% random (e.g. it would be ridiculous for a nuclear bomb,
owned by your opponent, to randomly appear next to *your* capital
city!).

I recall thinking that something like that might be interesting in
bolodd.g: Every so often, an independent unit (perhaps goblins at low
levels, with more powerful stuff as the game progresses) appears out of
nowhere (but preferably in an area that nobody can see) and wreaks havoc
with any non-independent units it can find.  Of course, I don't expect
anything like that to become possible until well after 7.5.

  reply	other threads:[~2003-11-18  2:14 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 15:42 Bill Macon
2003-11-17 18:55 ` Marketing Xconq? + battle isle suggestion Andreas Bringedal
2003-11-17 22:04   ` better Windows UI Brandon J. Van Every
2003-11-18  3:12     ` Erik Jessen
2003-11-17 21:56 ` Marketing Xconq? Eric McDonald
2003-11-17 22:38   ` Brandon J. Van Every
2003-11-18  3:15     ` Erik Jessen
2003-11-18  3:39       ` New Interpreter (was RE: Marketing Xconq?) Eric McDonald
2003-11-18  4:01         ` Erik Jessen
2003-11-18  4:05           ` Eric McDonald
2003-11-18 10:37             ` setgid (was: RE: New Interpreter (was RE: Marketing Xconq?)) Lincoln Peters
2003-11-18 15:52               ` Jim Kingdon
2003-11-18  5:17       ` Python in Xconq Brandon J. Van Every
2003-11-18 11:33         ` Erik Jessen
2003-11-18 13:37           ` OT Python stuff (was RE: Python in Xconq) Mark A. Flacy
2003-11-19 15:08             ` Erik Jessen
2003-11-19 16:44               ` Bruno Boettcher
2003-11-19 17:58                 ` Eric McDonald
2003-11-19 21:18                   ` GDL, XML and others...Re: " Jakob Ilves
2003-11-19 23:13                     ` Brandon J. Van Every
2003-11-20  5:12                     ` Eric McDonald
2003-11-20  8:54                       ` Bruno Boettcher
2003-11-20 11:01                         ` Jakob Ilves
2003-11-20 11:19                           ` Brandon J. Van Every
2003-11-20 12:59                             ` Jakob Ilves
2003-11-20 13:54                               ` One Hex Combat Resolution, and jeweled teeth Brandon J. Van Every
2003-11-20 17:06                                 ` Eric E Moore
2003-11-20 17:37                                   ` Jakob Ilves
2003-11-20 17:47                                     ` Emmanuel Fritsch
2003-11-20 19:53                                     ` Eric E Moore
2003-11-21  2:16                                   ` Eric McDonald
2003-11-21  3:03                                     ` What is Python really good for? Brandon J. Van Every
2003-11-20 11:36                           ` GDL, XML and others...Re: OT Python stuff (was RE: Python in Xconq) Bruno Boettcher
2003-11-20  4:38                   ` Erik Jessen
2003-11-20 10:19                     ` cheating Brandon J. Van Every
2003-11-21  1:46                       ` cheating Eric McDonald
2003-11-21  2:32                         ` cheating Brandon J. Van Every
2003-11-21  9:30                           ` Managing "Designers disgust". cheating Jakob Ilves
2003-11-21  9:33                             ` Brandon J. Van Every
2003-11-21 12:36                               ` Jakob Ilves
2003-11-21 14:28                                 ` Brandon J. Van Every
2003-11-19 22:14                 ` OT Python stuff (was RE: Python in Xconq) Brandon J. Van Every
2003-11-20  3:10                 ` Erik Jessen
2003-11-18  1:13   ` Marketing Xconq? Dr Eric Edward Moore
2003-11-18  1:31     ` Eric McDonald
2003-11-18  2:34       ` Lincoln Peters [this message]
2003-11-18  3:11         ` Eric McDonald
  -- strict thread matches above, loose matches on Subject: below --
2003-11-18 17:06 Bill Macon
2003-11-17  7:50 Brandon J. Van Every

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=1069120644.29637.83838.camel@odysseus.peterslan \
    --to=sampln@sbcglobal.net \
    --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).