public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kingdon <kingdon@panix.com>
To: mcdonald@phy.cmich.edu
Cc: xconq7@sources.redhat.com
Subject: Re: Weird fuel behavior
Date: Tue, 20 Jul 2004 15:40:00 -0000	[thread overview]
Message-ID: <200407201517.i6KFHni14489@panix5.panix.com> (raw)
In-Reply-To: <40FD2029.5090109@phy.cmich.edu> (message from Eric McDonald on Tue, 20 Jul 2004 07:37:45 -0600)

> I think that there a number of instances where notifications should be 
> issued, but are not.

I don't like the notifications as they exist now because there is also
lots of noise, as well as useful information.  So if we get rid of
some of the useless ones while we add new ones, I might be with you.
My favorite example of a useless one is when you hit "t" for take and
it says "unit got 5 fuel" - I can see telling the user somehow, but
not putting into a history along with unexpected occurrences.  Perhaps
an even better example is the "unit completed" messages at the start
of each turn - it isn't as if you need to see those messages so you
can hunt down each one and give it orders - the UI will prompt you for
what each of the new units should do, which is sufficient indication
of their having been created.  And the mess of "unit completed"
messages tends to obscure whatever the AI opponent did at the end of
last turn or the start of this one.

>   "Your dee-stroy-er, strength 1, ree-pelled an at-tack-ing dee-stroy-er."
>   "Dee-stroy-er dee-stroyed your dee-stroy-er."

Sort of, but with a "click for details" on each line.  So the summary
is "Your 15th bomber destroyed the Sudanese 132nd armor", the details
might be:

    Bomber versus armor hit chance starts at 25%.
    This armor is in a city, which gives it 50% protection.
    So the hit chance was 12%.
    The dice were rolled, and got a hit.
    Bomber versus armor damage is 1 hit point.
    The armor started with 1 hit point, so it was left with 0, and was
    destroyed.
    Its material was destoyed with it.... (or wrecking, or whatever
    consequences of destruction would be).

Obviously putting too much information in this window could just lead
to information overload, but I was hoping to at least have enough to
make it clear why something happened (especially to cover mistake or
quasi-mistake situations, like making attacks which have 0% or almost
0% chance of success, or perhaps defensive fortifications which were
useless in the particular situation, or something like that).

> Maybe an unit graveyard window would be useful for displaying pastunits 
> and their associated event logs. Have the most recently deceased
> units 

I like this one.

Units going away is one of the particularly distressing and
(potentially) surprising events, so having a window for it seems to
make sense.

  reply	other threads:[~2004-07-20 15:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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-24 23:19                                           ` Action-Notices list Elijah Meeks
2004-07-26  1:31                                             ` Eric McDonald
2004-07-21  0:55                                   ` Weird fuel behavior Hans Ronne
2004-07-24 20:50                                     ` Eric McDonald
2004-07-20 15:17                       ` Eric McDonald
2004-07-20 15:40                         ` Jim Kingdon [this message]
2004-07-19  3:07                   ` Robert Goulding
2004-07-17 12:47 Hans Ronne
2004-07-19  8:07 Robert Goulding
2004-07-19 18:14 ` 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=200407201517.i6KFHni14489@panix5.panix.com \
    --to=kingdon@panix.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).