Re: [Rails-devel] bug 1880 revenue calculation 6E

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

Volker:
thanks for reporting the bug: The train calculation is wrong for the 
1880 E-trains.

The train used here is the E-train from 1826 (for this game E stands for 
"Electrical"). The 1826 E-train simply passes all towns on its route. I 
would have preferred a different label for such a train, e.g. X for 
eXpress-trains...

For such a train Rails calculates the optimal value in your example.

However the 1880 E-train (I found no reference in the rules, what E 
means in this case) can choose to omit any station (cities/towns, or in 
1880 rules language: large/small cities). This in fact is a Diesel 
train, that chooses the top # of stations on the route to be counted.

This train is so far not supported by Rails, however it can be created 
using a RevenueModifier (here RevenueDynamicModifier).

Unless someone else volunteers ;-), I will implement the required modifier.

Stefan

On 05/15/2014 09:59 AM, vol...@ar... wrote:
> Hi,
>
> here is an other bug in the revenue calculation.
> the SCR runs a 6E Trains, which is allowed to pass any station (normal and small station).
> Rails pass the small station at the revenue-calculation.
> Rails revenue: 270. It should be 310
> see savefile and picture.
>
> greetings volker
>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
>
>
>
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>