This is the mail archive of the xconq7@sources.redhat.com mailing list for the Xconq project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Bug: Tank sitting in water

From: Lincoln Peters <peters2000 at mindspring dot com>
To: Hans Ronne <hronne at telia dot com>
Cc: Xconq list <xconq7 at sources dot redhat dot com>
Date: 20 Jan 2003 11:43:16 -0800
Subject: Re: Bug: Tank sitting in water
Organization:
References: <l03130300ba4cc6206f14@[212.181.162.155]> <l03130302ba4c1a8d1284@[212.181.162.155]> <l03130300ba4b822c3b01@[212.181.162.155]> <l03130300ba4a474a28c5@[212.181.162.155]> <l03130300ba4b822c3b01@[212.181.162.155]> <l03130302ba4c1a8d1284@[212.181.162.155]> <l03130300ba4cc6206f14@[212.181.162.155]> <l03130302ba515d5c1755@[212.181.162.155]>

Oops, the update was older than I thought.  I updated it again, and now
everything works fine.

On Mon, 2003-01-20 at 00:11, Hans Ronne wrote:
> That's strange. The first "tank sitting in water fix" did have exactly this
> effect. But the second fix, which was checked in one week ago, was supposed
> to solve the problem. See my email a few days ago. It removed the recently
> introduced check for terrain_always_impassable, so there is no way this
> code could now interfere with the use of connections.  Are you sure you
> pulled a fresh update, and not a stale one?

-- 
Lincoln Peters <peters2000@mindspring.com>

References:
- Re: Bug: Tank sitting in water
  - From: Hans Ronne
- Re: Bug: Tank sitting in water
  - From: Hans Ronne
- Re: Bug: Tank sitting in water
  - From: Hans Ronne
- Re: Bug: Tank sitting in water
  - From: Hans Ronne
- Re: Bug: Tank sitting in water
  - From: Hans Ronne

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]