From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27601 invoked by alias); 8 Dec 2003 22:48:31 -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 27591 invoked from network); 8 Dec 2003 22:48:30 -0000 Received: from unknown (HELO smtp801.mail.ukl.yahoo.com) (217.12.12.138) by sources.redhat.com with SMTP; 8 Dec 2003 22:48:30 -0000 Received: from adsl-64-175-248-254.dsl.sntc01.pacbell.net (HELO 6-allhosts) (sampln@sbcglobal.net@64.175.248.254 with plain) by smtp1.bt.mail.vip.ukl.yahoo.com with SMTP; 8 Dec 2003 22:48:29 -0000 Subject: Re: Cannot do anything in water From: Lincoln Peters To: Hans Ronne Cc: Jim Kingdon , Xconq list In-Reply-To: References: <1070854101.22214.7955.camel@odysseus> (message from Lincoln Peters on Sun, 07 Dec 2003 19:28:22 -0800) <1070854101.22214.7955.camel@odysseus> Content-Type: text/plain Message-Id: <1070923833.22214.16973.camel@odysseus> Mime-Version: 1.0 Date: Tue, 09 Dec 2003 00:40:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003/txt/msg01004.txt.bz2 On Mon, 2003-12-08 at 11:39, Hans Ronne wrote: > >> I was trying to work on my new game module, and now I've found that, if > >> I try to make a unit move into a water cell (and it can enter water > >> cells), it expends 1 ACP but does not go anywhere! > > > >Probably the same bug as > >http://sources.redhat.com/ml/xconq7/2003/msg00960.html It does look similar, although I don't think that I ever saw it happen to land units as they moved across land (and my new game does not contain air units). > > > >> Could it be a bug in the new pathfinding algorithm? > > Maybe. But not the construction problem since it does not involve > path-finding. If both are manifestations of the same bug, I would rather > suspect the terrain occupancy code. If that code could prevent movement while still causing a unit to consume ACP, I imagine that it might be the source of the problem. > > OTOH, The construction bug sounds more like an undefined action being > allowed following an illegal click. The program should just beep instead > and refuse to do anything if you click in the wrong cell. That's not what I've observed. I've often found that if the cell I tell it to build in is illegal (e.g. try to build a city in the water), but it can build in a nearby legal cell without moving (the cell is within its create-range), it will build in that alternate location instead. And it never asks if that is what I want to do. Although I suppose that there could be two bugs at work here... Lincoln Peters