Re: [Rails-devel] Train management

[Scott P. <sc...@re...>]

On Thu, Jun 9, 2011 at 5:17 PM, Erik Vos <eri...@xs...> wrote:

> OK, the 18TN 4-train obsoleting on buying the 2nd 6-train should work now.
> ****
>
> ** **
>
> The implementation is a bit provisional, as it only covers rusting yet.  I
> think we’ll have to move to a more generic approach, in which any type of
> action can be triggered that is normally associated with phase changes.
>

Erik, I played through a test game and verify that the second 6-train rusts
the 4-trains.
It looks like you implemented this with the following as a property of the
6-train.
 <Sub index="2" rustedTrain="4"/>

18TN's Game.xml is currently configured to obsolete the 2/3/4-trains.  All
of those should not have the obsoleting property.  The only trains that
obsolete are the 4-trains on the second 6-train (hard rust on 8-train).  As
train obsoletion is currently implemented, it is just a "free pass" at
another run once the train "rusts."  I think there is currently no mechanism
to make the train hard rust immediately, bypassing the obsolete "free pass."

As you said, we will have to take a look at a more general solution for the
half-phase changes.

Also, it would be nice to implement the "you must buy a train unless you
have no route" red text once obsolete trains are run and leave a company
trainless.  This must currently be triggered off something like a dividend
of zero because it does not appear after a company's obsolete trains run and
rust.