From: Aliza P. <ali...@gm...> - 2010-08-13 17:42:16
|
I did not see a bug filed on this in SourceForge so I filed bug 3044491on it with a savefile. (I also note that a more critical bug affecting 18AL, ID: 3026083, has been marked as fixed but there's nothing in Sourceforge to tell me what Rails release, if any, contains the fix.) If the bug has been fixed, when can we expect to see a new version of Rails published with the fix? Is there a way to set up Sourceforge so people can see what published version contains the fix for each bug, or at least add a "released" status after "fixed"? Peter, Brad, Joshua, this involves a play-ahead of our game based on my guessing what people would do, please do not look at the savefile (though you can probably guess.) - Aliza On Sun, Jul 4, 2010 at 1:57 PM, Erik Vos <eri...@xs...> wrote: > > (Switching to the proper group) > This has been fixed now - in Subversion! > > Erik. > > ________________________________ > From: 18...@ya... [mailto:18...@ya...] On Behalf Of John A. Tamplin > Sent: Friday 02 July 2010 00:17 > To: 18...@ya... > Subject: Re: [18xx] par value marker movement > > > > On Thu, Jul 1, 2010 at 3:43 PM, Erik Vos <eri...@xs...> wrote: > > > At the end of the SR, the companies are scanned for being sold out in the > > order in which they appear in the Game Status window. Any upward token > > moves > > are then executed in that order and follow the normal move rules. So I > > suspect that the token order gets reversed only if a 'lower' company token > > is on top of a 'higher' one. Or it could be the reverse...:-) Indeed we > > need > > a saved file to prove that. > > In any case, I would encourage to file it as a bug, so it will get proper > > attention at some point. > > The tokens are supposed to be processed in market order, which winds up > preserving the same stacking. > > -- > John A. Tamplin > |