From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31719 invoked by alias); 30 Dec 2003 18:26:34 -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 31712 invoked from network); 30 Dec 2003 18:26:33 -0000 Received: from unknown (HELO mail1.panix.com) (166.84.1.72) by sources.redhat.com with SMTP; 30 Dec 2003 18:26:33 -0000 Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail1.panix.com (Postfix) with ESMTP id 1AAB248716; Tue, 30 Dec 2003 13:26:33 -0500 (EST) Received: (from kingdon@localhost) by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id hBUIQXi08764; Tue, 30 Dec 2003 13:26:33 -0500 (EST) Date: Wed, 31 Dec 2003 19:10:00 -0000 Message-Id: <200312301826.hBUIQXi08764@panix5.panix.com> From: Jim Kingdon To: mcdonald@phy.cmich.edu Cc: xconq7@sources.redhat.com In-reply-to: (message from Eric McDonald on Sun, 21 Dec 2003 02:22:27 -0500 (EST)) Subject: Re: annoying new bug in movement References: X-SW-Source: 2003/txt/msg01110.txt.bz2 > (2) do_move_action . . . > But at least now a notification is provided to let the player know > that the movement cannot be performed, and ACP is prevented from > being deducted in such a circumstance. I tried this with the test case I've been using, and it does have the intended effect (now ACP is not deducted, and I get the "%s was unable to perform requested move to %d,%d." message). Not a full fix, but better than it was.