public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Hans Ronne <hronne@comhem.se>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: xconq7@sources.redhat.com
Subject: Re: Consumption-per-fire?
Date: Sat, 05 Jun 2004 19:30:00 -0000	[thread overview]
Message-ID: <l03130300bce7cbb7a162@[212.181.162.155]> (raw)
In-Reply-To: <1086455552.1485.129.camel@localhost.localdomain>

>>  Real capture at a distance might involve
>> teleportation or long-range psychic powers. BTW, teleportation is on my
>> post-7.5 list. I think it could be useful in many games.
>
>Good, then I can take it off my lengthy post-7.5 list. :-)
>Were you thinking in terms of making 'move-range' fully implemented in
>the movement/pathfinding and AI code, for the purpose of allowing units
>to "blink" or "phase" (to use some fantasy terminology)?
>Or were you thinking in terms of "portals" or "travel gates" that cause
>their occupants to be relocated to a pre-designated cell, a cell
>randomly chosen from a set of pre-designated cells, or a totally random
>cell (possibly of a certain terrain type)?

I was thinking of portals. No decent space game should be without
wormholes. And portals would also come handy if somebody decided to write a
Diablo II module for Xconq :-).

>(What would be even cooler, but certainly a radical change/feature,
>would be the ability to travel between maps. That would make
>quasi-recreations of games such as "Bard's Tale" possible.)

Yes. I think this was discussed on the list last year. Somebody wanted to
write a multi-level D&D type game to Xconq. I suggested walled of sections
within one big map, with yet to be implemented portals as the only
connections between them.

>> I also do this, mainly to force the AI to use fire instead of attacks when
>> possible. However, there is one case where a firing unit has to use melee
>> attack and that is if it is attacked, survives and then counterattacks.
>> Which is certainly a possible scenario. Think of Tennyson's Light Brigade
>> actually reaching the Russian guns with ensuing hand-to-hand combat in the
>> trenches.
>
>To me, the question is: is it even worth pretending that the guns can
>counterattack? They are essentially useless once the British are among
>them. The guns had their juicy chance when they were mowing down the
>charging brigade.... Once they are reached, I think the contest is
>essentially over, and it is time to bring Florence Nightingale to the
>scene.

True. But the xconq attack code does permit counterattacks, though only of
the melee type. That was the point I was trying to make.

Hans


  reply	other threads:[~2004-06-05 19:30 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-30  2:52 build doctrine question/bug? Tom Schaub
2004-05-30  3:28 ` Eric McDonald
2004-06-02 20:30   ` Consumption-per-fire? Elijah Meeks
2004-06-04 21:44     ` Consumption-per-fire? Hans Ronne
2004-06-04 22:15       ` Consumption-per-fire? Elijah Meeks
2004-06-04 22:50         ` Consumption-per-fire? Hans Ronne
2004-06-04 23:04           ` Consumption-per-fire? Elijah Meeks
2004-06-04 23:19             ` Consumption-per-fire? Eric McDonald
2004-06-05  3:37               ` Consumption-per-fire? Elijah Meeks
2004-06-05  4:22                 ` Consumption-per-fire? Eric McDonald
2004-06-05  8:11                   ` Consumption-per-fire? Hans Ronne
2004-06-05  8:22                     ` Consumption-per-fire? Hans Ronne
2004-06-05 13:10                     ` Consumption-per-fire? Eric McDonald
2004-06-05 15:03                       ` Consumption-per-fire? Hans Ronne
2004-06-05 15:57                         ` Consumption-per-fire? Elijah Meeks
2004-06-05 17:05                           ` Consumption-per-fire? Hans Ronne
2004-06-05 18:37                           ` Overrun actions (was: Consumption-per-fire?) Hans Ronne
2004-06-05 22:30                             ` Elijah Meeks
2004-06-05 22:54                             ` Jim Kingdon
2004-06-06  0:31                               ` Hans Ronne
2004-06-06  0:59                                 ` Elijah Meeks
2004-06-06  2:21                                   ` Hans Ronne
2004-06-06  6:17                             ` Eric McDonald
2004-06-06  7:39                               ` Hans Ronne
2004-06-06 13:33                                 ` Eric McDonald
2004-06-05 17:15                         ` Consumption-per-fire? Eric McDonald
2004-06-05 19:30                           ` Hans Ronne [this message]
2004-06-06  6:32                             ` Consumption-per-fire? Eric McDonald
2004-06-06  4:34                           ` Consumption-per-fire? mskala
2004-06-06  6:52                             ` Consumption-per-fire? Eric McDonald
2004-06-06  7:13                             ` Consumption-per-fire? Lincoln Peters
2004-06-05  7:05               ` Consumption-per-fire? Hans Ronne
2004-06-04 23:12           ` Consumption-per-fire? Eric McDonald
2004-06-04 22:22 ` build doctrine question/bug? Hans Ronne
2004-06-05 17:08 ` Hans Ronne

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='l03130300bce7cbb7a162@[212.181.162.155]' \
    --to=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).