From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15404 invoked by alias); 23 Dec 2003 04:08:14 -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 15397 invoked from network); 23 Dec 2003 04:08:14 -0000 Received: from unknown (HELO smtp813.mail.sc5.yahoo.com) (66.163.170.83) by sources.redhat.com with SMTP; 23 Dec 2003 04:08:14 -0000 Received: from unknown (HELO 6-allhosts) (sampln@sbcglobal.net@64.175.248.254 with plain) by smtp813.mail.sc5.yahoo.com with SMTP; 23 Dec 2003 04:08:13 -0000 Subject: Re: annoying new bug in movement From: Lincoln Peters To: Eric McDonald Cc: Xconq list In-Reply-To: References: Content-Type: text/plain Message-Id: <1072152692.31574.1730.camel@odysseus> Mime-Version: 1.0 Date: Tue, 23 Dec 2003 04:40:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003/txt/msg01103.txt.bz2 I just tested the new patch with bolodd2.g, and found that, although an ACP is no longer burned when a move action fails, I still get an error when I try to make a naval unit move into water: Your 1st boat was unable to perform requested move to 30,13 If I try to perform an illegal move (e.g. move the boat into a land cell, or move a ground unit into a water cell), it gives me a different error (as it has given since at least 7.4.1): Your 1st boat can never do this! It would seem that a bug still exists somewhere in the pathfinding code... -- Lincoln Peters