public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kingdon <kingdon@panix.com>
To: xconq7@sources.redhat.com
Subject: Re: Weird fuel behavior
Date: Tue, 20 Jul 2004 08:05:00 -0000	[thread overview]
Message-ID: <200407200525.i6K5PRM00717@panix5.panix.com> (raw)
In-Reply-To: <40FAF653.9090602@phy.cmich.edu> (message from Eric McDonald on Sun, 18 Jul 2004 16:14:43 -0600)

> We shouldn't have to resort to quoting GDL when explaining a game's 
> behavior.

A nice ideal to have.

Better documentation/help is always good, but there's also the
question of the user interface showing the user what happened.  Right
now, you kind of need to know the rules of xconq (and your particular
game) to understand it, and of course it would be better if xconq
helped you learn said rules by showing them in action as clearly as
possible.

It's not an easy problem.  Having a huge number of messages somewhere
of the sort ("unit xxx starved" etc) won't work (unless perhaps for
rare events, which starving might be).  Maybe being able to click on a
unit and issue a command saying "what's going on with this unit?"
(e.g. "tried to attack last turn, but didn't have ammo").  Or I guess
it would be a cell in the case of a now-vanished unit...

  parent reply	other threads:[~2004-07-20  5:25 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 [this message]
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
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=200407200525.i6K5PRM00717@panix5.panix.com \
    --to=kingdon@panix.com \
    --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).