Complete.Org: Mailing Lists: Archives: freeciv-dev: January 2004:
[Freeciv-Dev] Re: (PR#7259) new function tile_has_river
Home

[Freeciv-Dev] Re: (PR#7259) new function tile_has_river

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: jdorje@xxxxxxxxxxxxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#7259) new function tile_has_river
From: "rwetmore@xxxxxxxxxxxx" <rwetmore@xxxxxxxxxxxx>
Date: Sun, 18 Jan 2004 10:13:23 -0800
Reply-to: rt@xxxxxxxxxxx

<URL: http://rt.freeciv.org/Ticket/Display.html?id=7259 >


Jason Short wrote:
> <URL: http://rt.freeciv.org/Ticket/Display.html?id=7259 >
> 
> Vasco Alexandre da Silva Costa wrote:
[...]
>>Remember, Freeciv used to just emulate Civ1. I assume the T_RIVER flag is
>>to allow reading of old Freeciv scenarios.

The T_RIVER tile type was the original river implementation.

> All savegames will be affected.  Per's hack to replace T_RIVER with 
> T_GRASSLAND + S_RIVER is good, but if the terrain came entirely from the 
> ruleset there wouldn't _be_ any T_RIVER and this would be impossible.
> 
> Generally, Freeciv is backward-compatible with its savegames.  But a 
> (significant) change to the ruleset breaks savegame compatability.  Is 
> there anything we can do about this?
> 
> jason

There is nothing to stop one from reading (and writing) Civ1 compatible
savegames while generally eliminating T_RIVER from all internal
implementation code. The only real issue is one of effort, I'm pretty sure.

Cheers,
RossW
=====




[Prev in Thread] Current Thread [Next in Thread]