From: Brett L. <wak...@gm...> - 2008-02-26 22:14:21
|
On Tue, 2008-02-26 at 22:54 +0100, Erik Vos wrote: > > Also, in the case of 1870, there is a standard and a variant way of > > handling destination tokens. > > > > The standard rule is that destination tokens don't occupy one of the > > normal city spaces. > > > > The variant is they do. > > 1870 is beyond my horizon right now, but it'll be considered when the time > comes... > > Erik. Of course. The point isn't 'this feature is needed to implement 1870'. The point is, there is at least one game that has requirements for token placement outside of town spots on a map hex. We need to either define an additional "town" spot for map hexes that allow token placements for certain game mechanics, such as destination runs. Or we need to define tokens in a way that allows them to be used in places other than city spots. The big thing I don't want to see us do is specializing the tokens into "town tokens" and "non-town tokens". The board games don't make this distinction, and I see no reason for us to do it either. These are generic enough mechanisms that I don't think 1870 is the only game that uses them. So, if you're going to be cleaning up the token code, this is something to keep in mind and, if you don't code it directly, leave room in your design to add it later. ---Brett. If you're going to do something tonight that you'll be sorry for tomorrow morning, sleep late. -- Henny Youngman |