[Rails-devel] Rules enforcement for Token lay (was: 1835 Pfalzbahn token lay)

[Stefan F. <ste...@we...>]

On 06/15/2012 01:05 AM, John David Galt wrote:
> On 2012-06-13 22:46, Mike Bourke wrote:
>> I'm pretty sure that we were playing 1st edition English Rules. Perhaps this
>> is one of the changes that took place between the two editions? Is it worth
>> considering offering the two as options choices during game setup?
>
> I have the impression that the present code does not enforce any rules about
> where tokens can be laid, so I wouldn't create an option for playing that way.
> If they are enforced later, then we'd want an option to turn off enforcement
> (and it is probably in the intended design already).
>

Current rules enforcement for tokens:
There are some rules with respect to token lays that are enforced by the 
current implementation. Some examples are:
* It is only possible to lay one token per OR.
* The correct cost of a token lay is enforced.
* Lay of home token is enforced (actually done automatically).
* No more tokens can be laid than slots are available.
* It is not possible to lay more tokens than available for the company.
* Correct handling of tokens after mergers.

If I do not forget something else here, there is only one (but an 
important one) rule missing: The check for connectivity.
However this is easy to add given the current code base, so expect this 
to be added in Rails2.1+ .

Similar to the automatic revenue calculation my current idea is to allow 
for different settings for connectivity rules enforcement for token (and 
tile) laying.

However it would still effect connectivity checks, the other rules (see 
above) would still be in place.

Most likely the option to switch on suggestions (highlighting valid 
hexes/tiles) should be better moved from the game options to the 
configuration options, as this would allow to make the option changeable 
during a game session.

Stefan