Thread: [Rails-devel] Bugs

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Found and fixed two bugs introduced by the recent updates.

Erik Vos

I have added a confirmation question on closing the main (Status) window.
This was a request in the bug list.

I have put several other bug reports to pending or closed status. These bugs
I could not reproduce, and no clear examples had been provided. Unless
counterexamples are provided, I consider these bugs as either previously
fixed or non-existing.
I will continue going through the bugs list in the coming days.

Erik 

Recently I found some Rails bug reports in the Sourceforge tracking
database.
Some (or perhaps all) of these had been reported by Chris Fawcett.

Only one of these bugs I have been able to reproduce: the initial number of
start items buyable in 1835 standard version. Indeed this was a bug in the
latest released version 1.0.6, but it had already been fixed in the current
working version.

The other reported bugs (regarding 18EU and 18AL) I could not reproduce in
v1.0.6 either. I will not research these bugs any further unless I receive a
save file, from which the problem can be shown with v1.0.6 or later.

Erik.

Fixed several bugs, including:

- #2989355 1856 W&S token not free 
  (caused by too early closing of W&S)

- #2989440 1899 Priority deal not in right place after auction 
  (affects all 1830-style auctions). Fix may cause old saved files fail to
reload.

- #2990120 1856 No Token placed when THB floated.
  (fixed before).

- #2990413 1851 Train disappears. This related to the *last* 8-train; buying
it surfaced an error.
  I have also added an "unlimited trains" option to 1851. Although
Blackwater Station says that 8-trains are unlimited, the rules I have are
silent on this matter.

- 1835 Bayern incorrectly floated if not all blue privates have been sold
(reported by JDG). 
  This fix triggered some reorganization of the float detection code.
  The problems still aren't over: in such a case the game now hangs at the
start of OR1. I think this is caused by the (very old) 1835 start round
code, which does follow the processing pattern that has evolved since for
stock and operating rounds. Fixing that will need more time. For now I would
urge 1835 playtesters to make sure that the whole start package is sold
before OR1.

Erik

...
start of OR1. I think this is caused by the (very old) 1835 start round
code, which does follow the processing pattern that has evolved since for
               ^^^
Should of course be: does *not* follow.

Thread: [Rails-devel] Bugs

rails-devel