Re: [Rails-devel] 18EU Tile number overlaps

[brett l. <wak...@gm...>]

On 10/24/07, John A. Tamplin <ja...@ja...> wrote:
> Chris Shaffer wrote:
> > I strongly suggest you keep the same numbers, but indicate in some way
> > that they are variants.  The game should be as similar to the printed
> > version as possible, despite tile numbering conflicts.
> >
> You already have to deal with multiple identical tile numbers that have
> different track.  I suggest using the same solution I do in my database
> -- I have a unique tile ID and an attribute of the tile is the number to
> display on the tile.
>
> Also, note that tiles 80-83 are in fact identical to the "standard"
> 80-83 -- they have the same connectivity between edges, but are just
> drawn differently.
>


Just to play devil's advocate for a moment...

What's the reasoning behind keeping the tile numbering the same?  If
it's merely because that's what people already know and use for PBEM,
that reasoning strikes me as tenuous at best.  So long as Rails uses
an internally consistent numbering scheme, the tile numbering is
largely irrelevant for actual gameplay.

In other words, the gameplay value of Tile #9 isn't the fact that it's
number nine, but the fact that it represents track going from one side
of the hex to the opposite side in a straight line. So, therefore
whether it's labelled 9 or 99 doesn't really matter at all, does it?

FWIW - I believe the previous numbering collisions were dealt with by
bumping the tile numbers into a new range (e.g. 65 became 2065).
Though, my memory isn't clear on this point, which is what instigated
the question in the first place. :-)


---Brett.