Re: [Rails-devel] Implementation details for revenue calculation

[Stefan F. (web.de) <ste...@we...>]

Another overview of the implementation details:

The implementation plan has changed:
1. 1830, 1889: done
2. 1835: very close
3. 18Kaas, 18EU: close
4. 1851, 1856, 18AL: not in the upcoming release

I expect with that after this weekend all games up to 
the third group will be supported.

Stefan

Specific implementations:

1830: VertexVisitSets (see previous mail)
1889: RevenueBonus (see previous mail)

1835:
Berlin: VertexVisitSets
Hamburg: (Multiple) RevenueBonus(es)
Open Question here if and how an invalid orientation of the brown Hamburg tile 
can be prevented.

18EU:
Offboard-2-Offboard: StaticRevenueModifier that creates RevenueBonus(es)
Hamburg: Definition of an additional sink vertex 
Paris, Berlin, Vienna: VertexVisitSets
Pullman: DynamicRevenueModifier

18Kaas:
Ruhr: StaticRevenueModifier that creates RevenueBonus(es)

Not yet decided:
The main issue for those games is that I have no own experience playing those, 
thus I have to test them more carefully first.

1851
Offboard-2-Offboard: see 18EU
Birmingham/Johnson City: RevenueBonus (phase dependent)
Birmingham: does not exist until Phase 4
Most likely this should be implemented outside of the revenue part. I would 
prefer that the hex is empty until phase 4 and that the phase change triggers 
the lay of that tile.

1856
Bonus tokens: When and how to create the RevenueBonus? 
(=> StaticRevenueModifier)

18AL
Bonus tokens and Named trains: When and how to create the RevenueBonus?
(=> StaticRevenueModifier)

------------------------------------------------------------------------------
_______________________________________________
Rails-devel mailing list
Rai...@li...
https://lists.sourceforge.net/lists/listinfo/rails-devel