rails-users

[Rails-users] Rails 1.3 is now available.

[brett l. <bre...@gm...>]

I'm pleased to announce that Rails 1.3 is now available.

This release adds an initial implementation of automated route and
revenue calculation as well as bug fixes for 1830, 1856, 1889. Also in
this release is revised documentation on how well-supported each game
is.

Download the new release at http://rails.sourceforge.net/

---Brett.

Re: [Rails-users] [Rails-announce] Rails 1.3 is now available.

[Jeff F. <fe...@op...>]

I just loaded up an 1830 save file in which I ended the previous OR by 
exchanging a 4 train for a D.  When I make the move and save the file 
(using either Rails 1.2.2 or Rails 1.3), Rails 1.3 says it's an illegal 
move and rewinds the game back to the buy train step.  It's definitely 
legal, and Rails 1.3 lets me do it, but it won't let me load up a save 
containing the move.

Jeff

brett lentz wrote:
> I'm pleased to announce that Rails 1.3 is now available.
>
> This release adds an initial implementation of automated route and
> revenue calculation as well as bug fixes for 1830, 1856, 1889. Also in
> this release is revised documentation on how well-supported each game
> is.
>
> Download the new release at http://rails.sourceforge.net/
>
> ---Brett.
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Rails-announce mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-announce
>
>
>   

Re: [Rails-users] [Rails-announce] Rails 1.3 is now available.

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

To avoid some disappointment with this release I will give some more hints
what to expect.

There has been some bug-fixes which can cause some save files to be 
incompatible with the new release. Exchange of trains is one example.
If such an error occurs either stay with the previous release or start at that 
point and replay the missing moves.

Another thing to mention is that route and revenue calculation is disabled by 
default for save files from previous Rails version. This allows pbem users to 
update to that rails version for bug-fixes who do want to play with automatic 
game support turned on. For new games the default is to activate them, but 
each of them can be deactivated under the game options.

And to finish here is that Erik has improved 1835 that it is ready for serious 
testing, but please do not start long-running pbems yet ;-)

Stefan

On Monday 31 May 2010 16:45:46 Jeff Feuer wrote:
> I just loaded up an 1830 save file in which I ended the previous OR by
> exchanging a 4 train for a D.  When I make the move and save the file
> (using either Rails 1.2.2 or Rails 1.3), Rails 1.3 says it's an illegal
> move and rewinds the game back to the buy train step.  It's definitely
> legal, and Rails 1.3 lets me do it, but it won't let me load up a save
> containing the move.
>
> Jeff
>
> brett lentz wrote:
> > I'm pleased to announce that Rails 1.3 is now available.
> >
> > This release adds an initial implementation of automated route and
> > revenue calculation as well as bug fixes for 1830, 1856, 1889. Also in
> > this release is revised documentation on how well-supported each game
> > is.
> >
> > Download the new release at http://rails.sourceforge.net/
> >
> > ---Brett.
> >
> > -------------------------------------------------------------------------
> >-----
> >
> > _______________________________________________
> > Rails-announce mailing list
> > Rai...@li...
> > https://lists.sourceforge.net/lists/listinfo/rails-announce
>
> ---------------------------------------------------------------------------
>---
>
> _______________________________________________
> Rails-users mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-users

Re: [Rails-users] [Rails-announce] Rails 1.3 is now available.

[Jeff F. <fe...@op...>]

I tried starting at that point and replaying the missing moves and it 
still doesn't work.

I think the problem is that when I selected to exchange the 4 for the D, 
it doesn't save the fact into the log or something of what train was 
exchanged so that rails 1.3 knows what was exchanged when you load the 
save game.  It chose which train I wanted to exchange automatically (as 
that was the only train I had to exchange) but as it was automatic, that 
might be causing the bug of not saving which train was exchanged.

Jeff

Stefan Frey wrote:
> To avoid some disappointment with this release I will give some more hints
> what to expect.
>
> There has been some bug-fixes which can cause some save files to be 
> incompatible with the new release. Exchange of trains is one example.
> If such an error occurs either stay with the previous release or start at that 
> point and replay the missing moves.
>
> Another thing to mention is that route and revenue calculation is disabled by 
> default for save files from previous Rails version. This allows pbem users to 
> update to that rails version for bug-fixes who do want to play with automatic 
> game support turned on. For new games the default is to activate them, but 
> each of them can be deactivated under the game options.
>
> And to finish here is that Erik has improved 1835 that it is ready for serious 
> testing, but please do not start long-running pbems yet ;-)
>
> Stefan
>
> On Monday 31 May 2010 16:45:46 Jeff Feuer wrote:
>   
>> I just loaded up an 1830 save file in which I ended the previous OR by
>> exchanging a 4 train for a D.  When I make the move and save the file
>> (using either Rails 1.2.2 or Rails 1.3), Rails 1.3 says it's an illegal
>> move and rewinds the game back to the buy train step.  It's definitely
>> legal, and Rails 1.3 lets me do it, but it won't let me load up a save
>> containing the move.
>>
>> Jeff
>>
>> brett lentz wrote:
>>     
>>> I'm pleased to announce that Rails 1.3 is now available.
>>>
>>> This release adds an initial implementation of automated route and
>>> revenue calculation as well as bug fixes for 1830, 1856, 1889. Also in
>>> this release is revised documentation on how well-supported each game
>>> is.
>>>
>>> Download the new release at http://rails.sourceforge.net/
>>>
>>> ---Brett.
>>>
>>> -------------------------------------------------------------------------
>>> -----
>>>
>>> _______________________________________________
>>> Rails-announce mailing list
>>> Rai...@li...
>>> https://lists.sourceforge.net/lists/listinfo/rails-announce
>>>       
>> ---------------------------------------------------------------------------
>> ---
>>
>> _______________________________________________
>> Rails-users mailing list
>> Rai...@li...
>> https://lists.sourceforge.net/lists/listinfo/rails-users
>>     
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Rails-users mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-users
>
>
>   

Re: [Rails-users] [Rails-announce] Rails 1.3 is now available.

[Erik V. <eri...@xs...>]

I have seen cases where saved files would not load because the D-train
exchange was executed (and recorded) incompletely: the D was obtained at the
exchange price, but the 4-(or whatever) train was not turned in. I have seen
this caused by pressing 'Cancel' on the which-train-to-exchange question.
This error has recently been fixed.

I don't know if this might explain your problem; if not, I'm willing to have
a look at your saved file to check why it fails. But I doubt if there is
much chance to rescue it.

Erik

-----Original Message-----
From: Jeff Feuer [mailto:fe...@op...] 
Sent: Monday 31 May 2010 22:37
To: Stefan Frey
Cc: rai...@li...
Subject: Re: [Rails-users] [Rails-announce] Rails 1.3 is now available.

I tried starting at that point and replaying the missing moves and it 
still doesn't work.

I think the problem is that when I selected to exchange the 4 for the D, 
it doesn't save the fact into the log or something of what train was 
exchanged so that rails 1.3 knows what was exchanged when you load the 
save game.  It chose which train I wanted to exchange automatically (as 
that was the only train I had to exchange) but as it was automatic, that 
might be causing the bug of not saving which train was exchanged.

Jeff

Stefan Frey wrote:
> To avoid some disappointment with this release I will give some more hints
> what to expect.
>
> There has been some bug-fixes which can cause some save files to be 
> incompatible with the new release. Exchange of trains is one example.
> If such an error occurs either stay with the previous release or start at
that 
> point and replay the missing moves.
>
> Another thing to mention is that route and revenue calculation is disabled
by 
> default for save files from previous Rails version. This allows pbem users
to 
> update to that rails version for bug-fixes who do want to play with
automatic 
> game support turned on. For new games the default is to activate them, but

> each of them can be deactivated under the game options.
>
> And to finish here is that Erik has improved 1835 that it is ready for
serious 
> testing, but please do not start long-running pbems yet ;-)
>
> Stefan
>
> On Monday 31 May 2010 16:45:46 Jeff Feuer wrote:
>   
>> I just loaded up an 1830 save file in which I ended the previous OR by
>> exchanging a 4 train for a D.  When I make the move and save the file
>> (using either Rails 1.2.2 or Rails 1.3), Rails 1.3 says it's an illegal
>> move and rewinds the game back to the buy train step.  It's definitely
>> legal, and Rails 1.3 lets me do it, but it won't let me load up a save
>> containing the move.
>>
>> Jeff
>>
>> brett lentz wrote:
>>     
>>> I'm pleased to announce that Rails 1.3 is now available.
>>>
>>> This release adds an initial implementation of automated route and
>>> revenue calculation as well as bug fixes for 1830, 1856, 1889. Also in
>>> this release is revised documentation on how well-supported each game
>>> is.
>>>
>>> Download the new release at http://rails.sourceforge.net/
>>>
>>> ---Brett.
>>>
>>>
-------------------------------------------------------------------------
>>> -----
>>>
>>> _______________________________________________
>>> Rails-announce mailing list
>>> Rai...@li...
>>> https://lists.sourceforge.net/lists/listinfo/rails-announce
>>>       
>>
---------------------------------------------------------------------------
>> ---
>>
>> _______________________________________________
>> Rails-users mailing list
>> Rai...@li...
>> https://lists.sourceforge.net/lists/listinfo/rails-users
>>     
>
>
>
>
----------------------------------------------------------------------------
--
>
> _______________________________________________
> Rails-users mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-users
>
>
>   



----------------------------------------------------------------------------
--

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

Re: [Rails-users] Rails 1.3 is now available.

[brett l. <bre...@gm...>]

On Mon, May 31, 2010 at 7:27 AM, brett lentz <bre...@gm...> wrote:
> I'm pleased to announce that Rails 1.3 is now available.
>
> This release adds an initial implementation of automated route and
> revenue calculation as well as bug fixes for 1830, 1856, 1889. Also in
> this release is revised documentation on how well-supported each game
> is.
>
> Download the new release at http://rails.sourceforge.net/
>
> ---Brett.
>

Apologies all around. An issue with my e-mail prevented me from
sending out a proper changelog with my announcement.

So, here is the changelog for 1.3:

* Tile and Token Laying
- Hexes which are eligible for tile and token lays are highlighted
- Only a game hint, not enforced.

* Revenue Calculation
- Maximum revenue for the owned trains is suggested
- Presetting for the revenue entry, has still to be confirmed or can be
adjusted
- Should incorporate all game specific rules, including bonus rules

* Map Correction
- Downgrade of tiles is now possible
- Only tile availability is checked, otherwise no restrictions are applied
- Tile lays that require the re-laying out of tokens are not possible

* General
- Prevent 'foreign' token being layed on reserved home token slots.
- Fixed bugs in OO-tile and token laying.
- Fixed occasional incorrect priority deal assignment after 1830-style auctions.
- Fixed disappearance of last (highest) train bought.
- Added option to fix tile orientation (used for 1835 Hamburg).

* 1830
- Fixed possibility of buying a Diesel at exchange price without an
exchange taking place.

* 1835
- Finished/Fixed Prussian formation
- Allow 100% share ownership and nationalization.
- Bugs in initial round player order (Clemens variant) and BY flotation.
- Added several variant options.

* 1856
- (also for 18EU) added (invisible) City object to Goderich/Hamburg tile to
facilitate revenue calculation.
- Fixed bug in effect of repeated 5% CGR share sales on share price.
- Fixed W&S token lay cost problem.

* 18EU
- Fixes for bankruptcy rules (not yet tested under all possible circumstances).