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

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

18AL named trains:

Erik:
I took your advice to add a game option: Choosing it the assignment of the 
name chits is done by the revenue calculator. In addition it deactivates the 
manual assignment. I have defined this as the default option.

In  that respect: If I have figured it out correctly the default option in the 
gamelist.xml defines the default for new games, the one in the specific 
game.xml sets the one for saved games. Correct? Thus there is no need for an 
additional undefined setting, as I intended to add.

Alex:
For 18AL this additional limitation is not active, as of the 4 locations 3 are 
red areas, thus one train could never apply for both chits.

In general the scoring of bonuses in cases where one train can only score a 
subset of a larger set and each bonus can only be scored by one train is a 
non trivial task and would require a enumeration.
 
At least I see no simply algorithm to assign the bonuses if a train could be 
eligible for several bonuses. Thus I chose to define a specific modifier for 
this simpler case here.

Stefan


On Wednesday 26 May 2010 02:28:24 alexti wrote:
> To my knowledge name chits are transferable at any time. Effectively they
> act as a location pair bonus available to one train only. The only extra
> limitation is that 2 name chits can not be assigned to the same train.
>
> On Tue, 25 May 2010 13:53:13 -0600, Stefan Frey <ste...@we...> wrote:
> > Another update to the update below:
> >
> > All remaining issues below are fixed now, namely the named trains
> > can be saved and are still assigned after (re-)loading.
> >
> > In hindsight I wonder now, if the naming of trains should not be part of
> > the
> > optimization process instead being done manually by the players.
> >
> > Having never played 18AL before, I assumed that the assignment is fixed
> > (at
> > least as long as the train does not rust).
> >
> > But from the rules (and the current implemenation) the owner can change
> > it
> > anytime. Theme aside in my eyes the named trains is a plain revenue bonus
> > (visit two vertices) which is available only for one train and
> > should/could
> > have been implemented accordingly.
> >
> > In my eyes this is similar to the Pullman car of 18EU, where the rules
> > state
> > that the owner chooses a station for doube counting, but in Rails the
> > Pullman
> > car takes part in the search for the optimal run.
> >
> > Opinions from more experienced 18AL players are welcome.
> >
> > Stefan
> >
> > On Friday 21 May 2010 18:18:49 Stefan Frey wrote:
> >> Again some more update:
> >>
> >> Full support for 18AL and 18EU is in, 1851 has only Birmingham missing.
> >> More details see below.
> >>
> >> As Brett and Erik keep quiet about their preference for a release soon,
> >> I
> >> kept adding functionality.
> >> Fortunately this proved to be very easy, as most elements are well
> >> prepared. I was especially surprised by the excellent support of named
> >> trains in 18AL, as  without revenue calculation it served no real
> >> purpose.
> >> Thus it is not surprising that there are still some minor hassles, which
> >> will be easy to iron out.
> >>
> >> Known open issues:
> >> -> Invisible Birmingham tile
> >> -> Named trains are not assigned after reload
> >> -> 4D in 18AL do not score double (they are not correctly initialized)
> >> -> Graph optimization after off-board area token is not correct
> >>
> >> Complete summary of revenue specifics:
> >>
> >> Independent tests of those is appreciated.
> >> Map Correction allows to create scenarios easily.
> >> Under NetworkInfo one can run any type of trains in any game, simply use
> >> standard train type names (like D, 4+4, 10, 5E, 4D).
> >>
> >> 1830:
> >> Multi-Hex off-board locations
> >>
> >> 1889:
> >> Diesel Revenue Bonus at off-board locations
> >>
> >> 1835:
> >> Berlin: No visit of multiple stations (yellow tile only)
> >> Hamburg: Elbe malus
> >> Plus Trains
> >>
> >> 18EU:
> >> Offboard-Bonus: Dependent on number of tokens visited
> >> Hamburg: Termination vs. Non-Termination
> >> Paris, Berlin, Vienna: No visit of multiple stations
> >> Pullman: Bonus for most valuable city
> >> Trains do not count Towns
> >>
> >> 18Kaas:
> >> Ruhr: Bonus for other stations/cities
> >>
> >> 1851
> >> Offboard-2-Offboard: 10 bonus for each stop
> >> Invisible Birmingham: still open
> >>
> >> 1856
> >> Bonus tokens
> >>
> >> 18AL
> >> Bonus tokens
> >> Named Trains
> >> Nashville, Mobile: Off-map destinations with token slot
> >> Trains do not count Towns
> >> 4D trains
> >>
> >> Conversion from Rails to Network attributes:
> >>
> >> - If a Rails hex has a value attribute, that value takes preference for
> >> all
> >> stations on that hex, thus the value attribute of the stations of the
> >> tile
> >> laid is irrelevant (no need for -1 or 0).
> >>
> >> - Run-Through ("Not a sink") rule listed by priority
> >> 1) Off-Map city: No one runs through (even with own token)
> >> 2) Slots=0: All run through
> >> 3) Nb Tokens = Slots: Only run through with own token
> >> 4) Nb Tokens < Slots: All run through
> >> In addition to rule 1: An own token in an off-map city allows to run
> >> from.
> >>
> >> - Location names to identify vertex sets:
> >> The location name is the combination of the city attribute of the hex
> >> and
> >> city tile. If any of them are undefined or equal to "", no location is
> >> defined. Exception are off-map cities, for which only the hex attribute
> >> is
> >> considered.
> >>
> >> Stefan
> >>
> >> ------------------------------------------------------------------------
> >>--- ---
> >>
> >> _______________________________________________
> >> Rails-devel mailing list
> >> Rai...@li...
> >> https://lists.sourceforge.net/lists/listinfo/rails-devel
> >
> > -------------------------------------------------------------------------
> >-----
> >
> > _______________________________________________
> > Rails-devel mailing list
> > Rai...@li...
> > https://lists.sourceforge.net/lists/listinfo/rails-devel