Re: [Rails-devel] A subtle 1835 bug (1.7.4)

[Erik V. <eri...@xs...>]

I suspect the reason is, that the hex pairs C13/D12 and E13/F12 are not
considered "neighbours" in the sense that no track can ever be laid across
their common edges.
For simplicity (or laziness) reasons, I had used this same "neighbour"
concept to find neighbours for the purpose of hex distance calculation, but
apparently I had completely overlooked that impassability aspect.

The fix is to obtain the neighbouring hexes in a more direct way, ignoring
impassabilities.  The cost is now calculated as the correct 140M.

However, to deal with the 1835 "crow without a passport" aspect, all hexes
used in the calculation must still be non-null.
Should other games have hex distance calculation rules that do not ignore
null hexes, then we have another problem...

Erik

> -----Original Message-----
> From: John David Galt [mailto:jd...@di...]
> Sent: Sunday, May 27, 2012 11:50 PM
> To: rai...@li...
> Subject: [Rails-devel] A subtle 1835 bug (1.7.4)
> 
> At the point of this save file, MS just laid a token in Frankfurt (7 hexes
away
> from its home) but was charged 160.I suspect t