From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17654 invoked by alias); 10 Aug 2004 20:44:33 -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 17645 invoked from network); 10 Aug 2004 20:44:32 -0000 Received: from unknown (HELO av8-2-sn2.hy.skanova.net) (81.228.8.111) by sourceware.org with SMTP; 10 Aug 2004 20:44:32 -0000 Received: by av8-2-sn2.hy.skanova.net (Postfix, from userid 502) id 8ADC437E49; Tue, 10 Aug 2004 22:44:25 +0200 (CEST) Received: from smtp2-1-sn2.hy.skanova.net (smtp2-1-sn2.hy.skanova.net [81.228.8.177]) by av8-2-sn2.hy.skanova.net (Postfix) with ESMTP id 7AAB237E42; Tue, 10 Aug 2004 22:44:25 +0200 (CEST) Received: from [212.181.162.155] (h155n1fls24o1048.bredband.comhem.se [212.181.162.155]) by smtp2-1-sn2.hy.skanova.net (Postfix) with ESMTP id 1195E37E47; Tue, 10 Aug 2004 22:44:31 +0200 (CEST) X-Sender: u22611592@m1.226.comhem.se Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 11 Aug 2004 01:23:00 -0000 To: Robert Goulding From: Hans Ronne Subject: Re: time.g weirdness Cc: xconq7@sources.redhat.com X-SW-Source: 2004/txt/msg00863.txt.bz2 >Twice I've been playing time.g using the new Mac OSX binaries; and in >both games something weird has happened to one of my triremes. Having >developed tech to the City level, I've sent off an unneeded trireme to >explore uncharted territory by clicking at random on a black section of >the map. Each time, the boat has reached the place I clicked - but >that place was inland, so that the trireme is now stuck! I've attached >a little snapshot from my most recent game. Here, the trireme is >awaiting orders, having reached the position I sent it to... OK, I have managed to reproduce this now, and I think I know what is going on. The ship is actually behaving as it should, since ships can move along rivers in time.g: (table mp-to-traverse (ship river 2) (ground road 1) ) This is called a "border slide" in Xconq terminology. Now, the real problem is that Xconq fails to set a move task that requires a border slide when you try to do this manually. This is because the move command pre-flight code doesn't know about border slides. I think that Peter Garrone added some code that addressed this problem, but it was probably removed with his path-finding code. Anyway, the command pre-flight also has other problems, as I mentioned earlier, so it is probably due for an overhaul. Hans