From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23632 invoked by alias); 20 Jul 2004 05:25:28 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 23591 invoked from network); 20 Jul 2004 05:25:27 -0000 Received: from unknown (HELO mail3.panix.com) (166.84.1.74) by sourceware.org with SMTP; 20 Jul 2004 05:25:27 -0000 Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail3.panix.com (Postfix) with ESMTP id 3B70A9821D; Tue, 20 Jul 2004 01:25:27 -0400 (EDT) Received: (from kingdon@localhost) by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i6K5PRM00717; Tue, 20 Jul 2004 01:25:27 -0400 (EDT) Date: Tue, 20 Jul 2004 08:05:00 -0000 Message-Id: <200407200525.i6K5PRM00717@panix5.panix.com> From: Jim Kingdon To: xconq7@sources.redhat.com In-reply-to: <40FAF653.9090602@phy.cmich.edu> (message from Eric McDonald on Sun, 18 Jul 2004 16:14:43 -0600) Subject: Re: Weird fuel behavior References: <40FAF653.9090602@phy.cmich.edu> X-SW-Source: 2004/txt/msg00779.txt.bz2 > 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...