Re: [Rails-devel] 1835 Schlesien

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

>> However, it seems to me that a "variant" such as Clemens which changes
>> only the start packet should not be listed as a variant but merely an
option in
>> the Options tab -- so that it can be played with another variant.
Similarly for
>> other small changes.
> 
> Agreed, in principle, but here we again run into the problems of
compatibility
> testing and the introduction of new source of bugs as a consequence.

And backwards compatibility, mostly for existing test cases.

My summary: a game option relates to a variant as a (medical) symptom
relates to a syndrome.
A game option covers a single aspect, a variant covers multiple aspects.

My latest proposal is:

1. Create the new InitialRoundType option as described before.  It only
covers the start packet distribution method (not the start packet itself;
that is variant stuff).
The initial values will cover the methods already implemented: Standard,
Snake and Clemens.

2. Schlesien will become a new variant.  
Do we agree that we can forget the original Coalfields variant, which does
not change train and tile quantities, but is otherwise identical?

3. For backwards compatibility reasons, the Snake and Clemens _variants_
will be kept temporarily (to be dropped in Rails 2.0).
Saved file conversion will be built in: both versions can be loaded, but
only the new file version will be saved.

4. A new configuration flag (XML tag or attribute) will allow to ignore the
InitialRoundType setting.
Future new variants may encompass new start packet distribution methods.
Case by case we will have to consider if such methods are generic enough to
become another InitialRoundType value. If not, this flag must be set with
the new variant.

Erik.