From: Stefan F. <ste...@we...> - 2014-05-05 07:47:09
|
Hi Martin, I suggest the following to use for Rails 2.0. This is the result of a off-list discussion with Martin how to define terrain costs for 1846. The game features terrain cost on hex edges. Stefan * Define Terrain in Defaults: <Defaults> <Terrain type="mountain" cost="80" /> <Terrain type="river" cost="40" /> </Defaults> * Terrain on Hexes: <Hex name="D8" tile="0"/> <Terrain type="mountain"/> </Hex> * Terrain on Edges: <Edge from="D8" to="E9"> <Terrain type="river" /> </Edge> * This also allows moving the impassable definitions from Hexes to Edges: <Edge from="D8" to="E9"> <Impassable /> </Edge> The immediate advantage is that this avoids answering the question if double-definitions are required and (if not) what happens if there is a double-definition. Remark: From and to have no effect here, but there might be other occasions there this might be helpful in the future. |