From: Stefan F. <ste...@we...> - 2012-05-15 10:26:10
|
John & Erik: sorry for not responding earlier, pretty busy period now: It is great to see an 1837 implementation soon, as I was able to play that game already - even if I do not own a copy myself next to 1849/1850 Sicily the ugliest gap of my collection. You touched the problem about how to implement the 1837 revenue calculation. Most train properties are already covered by the settings in xml. The main issue is the handling of G-Trains and coal companies. There are several possibilities to handle that I would suggest the following: A) Give no home token to coal companies (this avoids displaying them). Instead add a StaticGraphModifier that adds a home token for coal companies for revenue and route purposes. B) Define the coal tiles as offboard fields. Add a StaticRevenueModifier that removes the offboard (major scoring) node and replace it by a bonus vertex for the G-trains only. (Bonus vertices can be defined to be train dependent, whereas scoring nodes have to be identical). C) Add a name="Mine" attribute to all mines. This automatically treats them as a VertexVisitSet and thus a train can only visit one of them. Alternatively this could be checked in step D) too. D) Add a DynamicRevenueModifier that checks that routes of G-Trains have at least one mine in their route, otherwise the route will be void. I can easily add those elements, however I will wait until it is possible to have 1837 at least startup, so that I am able to test. Stefan |