public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "Robert Goulding" <Goulding.2@nd.edu>
To: "Hans Ronne" <hronne@comhem.se>
Cc: <xconq7@sources.redhat.com>
Subject: Re: Weird fuel behavior
Date: Mon, 19 Jul 2004 08:07:00 -0000	[thread overview]
Message-ID: <001301c46d3d$8b3a1a50$feb3fea9@blackbox> (raw)


> >
> > Now, what this table means is that the mine has a 25% chance each turn
of
> > loosing one hp if it is out of ammo. Since it only has 1 hp (and room
for
> 1
> > ammo) it is either filled up with ammo and safe, or empty and subject to
> > random destruction. This may be why you don't see a SupplyLow warning.
> >
>
> All right, last question then I'll shut up about this.  The mines are all
> produced with ammo 0/1; do I need to get a unit onto their hex and 'g'ive
> them some ammo each time I create one?
>
Having just tried out another lhs.g game, I simply cannot see how the mines
are fueled.  They are born with no ammo, will neither 't'ake any from the
engineer that made them (or from any other unit sharing their hex), nor can
such units 'g'ive them anything (and I've just tested this out at length).
They do not happily resupply themselves from nearby units or towns, as I now
understand other units are supposed to do - and so they drop off the map 1
turn in 4!  How can I save my mines!!?  Am I missing something about
resupply?

Robert.

             reply	other threads:[~2004-07-19  3:07 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-19  8:07 Robert Goulding [this message]
2004-07-19 18:14 ` Hans Ronne
  -- strict thread matches above, loose matches on Subject: below --
2004-07-17 12:47 Hans Ronne
2004-07-17  9:50 Robert Goulding
2004-07-17  9:57 ` Hans Ronne
2004-07-17 14:16   ` Robert Goulding
2004-07-17 20:06     ` Hans Ronne
2004-07-17 20:31       ` Robert Goulding
2004-07-17 21:13         ` Hans Ronne
2004-07-17 21:31           ` Robert Goulding
2004-07-18 13:07             ` Hans Ronne
2004-07-18 20:20               ` Robert Goulding
2004-07-18 22:14                 ` Hans Ronne
2004-07-18 22:16                   ` Eric McDonald
2004-07-19  2:50                     ` Hans Ronne
2004-07-20  8:05                     ` Jim Kingdon
2004-07-20 13:38                       ` Hans Ronne
2004-07-20 19:19                         ` Jim Kingdon
2004-07-20 19:50                           ` Hans Ronne
2004-07-20 21:36                             ` Eric McDonald
2004-07-20 22:07                               ` Hans Ronne
2004-07-20 23:12                                 ` Eric McDonald
2004-07-21  0:32                                   ` Stan Shebs
2004-07-21  0:47                                     ` Eric McDonald
2004-07-21  1:11                                       ` Hans Ronne
2004-07-21  1:33                                         ` Eric McDonald
2004-07-21  0:55                                   ` Hans Ronne
2004-07-24 20:50                                     ` Eric McDonald
2004-07-20 15:17                       ` Eric McDonald
2004-07-20 15:40                         ` Jim Kingdon
2004-07-19  3:07                   ` Robert Goulding

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='001301c46d3d$8b3a1a50$feb3fea9@blackbox' \
    --to=goulding.2@nd.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).