From: brett l. <bre...@gm...> - 2010-04-17 16:13:03
|
Stefan - Let's go ahead and update the playability scale with your proposal. If it needs future tweaking, we can do that. My best guess for '56 is probably almost a B, but still mostly a C. It's almost fully playable but not quite. Aliza and others are still hitting far too many issues to consider it guaranteed to be able to play a complete game without issue. ---Brett. On Sat, Apr 17, 2010 at 8:03 AM, Stefan Frey <ste...@we...> wrote: > Aliza, > this reminds me of the suggested changes of the implemention levels as > discussed some time ago for the next release. It seems to come close to what > you have in mind. > > So far the opinions for the individual 18xx were: > > 1825: D > 1830: B/A > 1835: D > 1851: B > 1856: > 1870: D > 1889: B > 18AL: B > 18EU: C/B > > With A=mature, B=fully playable, C=almost playable, D=experimental. > (See definitions below) > > There has not been any comment on the level of 1856 with respect to the > scaling above. And keep in mind that even if the individual 18xx might be > stable, Rails itself is still not feature complete, thus even stable 18xx > might be impacted from time to time. > > Stefan > > A) Mature > - Several independent plays until the end reported > - Full implementation of the ruleset > - All possible moves are available > - No illegal move possible (except tile and token lays, revenue calculation) > => Serious ftf play possible > => pbem play possible > > B) Fully Playable > - Full implementation of the ruleset > - All possible moves are available > - Might still allow a few illegal moves (in addition to tile and token lays, > revenue calculation) > => Serious ftf play possible, but bugs are possible > => use with caution for pbem play, version incompatibilities possible > > C) Almost Playable > - Nearly complete implementation of the ruleset > - Not all possible moves are available > - Illegal moves are possible > => Serious testing possible, do not expect to complete a game > => not recommended for pbem play > > D) Experimental > - Rules and components are incomplete > => Some testing possible > > > > On Friday 16 April 2010 22:25:41 Aliza Panitz wrote: >> Is there going to be a Rails release with this bug fix in it? (We're >> trying to decide how/whether to continue the game this bug was >> reported on...) >> >> 1856 has been marked as "fully supported" since Rails 1.0.7 and I'm >> still struggling to complete PbEM games I started in November... >> perhaps there should be another game status, "first release" or >> "playtesting needed" or something, to denote games that are mostly >> complete but for which there has been no extensive playtesting. >> >> - Aliza >> >> On Thu, Mar 25, 2010 at 4:27 PM, Erik Vos <eri...@xs...> wrote: >> > Never mind, I could reproduce the problem as described below, and have >> > fixed it. >> > Can’t upload it now (SVN seems down) so that will be done tomorrow. >> > >> > Erik. >> > >> > -----Original Message----- >> > From: Erik Vos [mailto:eri...@xs...] >> > Sent: Friday 26 March 2010 00:00 >> > To: 'Development list for Rails: an 18xx game'; 'Aliza Panitz' >> > Subject: Re: [Rails-devel] 1856: CGR Bug: selling 5% moves stock price >> > >> > Ah, you mean that sales of 15% and 5% have added up? >> > If that is what has happened, I think I know what has caused this. >> > A saved file would of course help a lot... >> > >> > Erik. >> > >> > >> > >> > -----Original Message----- >> > From: Joshua Gottesman [mailto:jos...@gm...] >> > Sent: Thursday 25 March 2010 22:56 >> > To: Aliza Panitz >> > Cc: Development list for Rails: an 18xx game >> > Subject: Re: [Rails-devel] 1856: CGR Bug: selling 5% moves stock price >> > >> > Yeah, I didn't even notice that. I just expected it to keep the price >> > the same. I suspect what happened is it counted your 15% and held the >> > 1/2 share and then combined that with my 1/2 share for another price >> > drop. Which is incorrect. >> > >> > On Thu, Mar 25, 2010 at 2:54 PM, Aliza Panitz <ali...@gm...> >> > >> > wrote: >> >> Rails 1.2.2 bug: >> >> >> >> Selling a single 5% share of the CGR to the pool should not have >> >> changed the stock >> >> price. >> >> >> >> To quote the rules: >> >> >> >> ============== >> >> The share value tokens move: >> >> >> >> Down one row for each full 10% share sold either during a stock round >> >> or during a forced sale by a company president. The sale of a single >> >> 5% share does not affect the share value token. Sales of multiple 5% >> >> shares move the share value token >> >> ============== >> >> >> >> To quote the game report: >> >> ] Joshua sells a 5% share of CGR to Pool for $90. >> >> ] CGR price goes from $90(E2) to $80(E3). >> >> >> >> >> >> I'll file an official bug later if nobody else gets to it first. >> >> >> >> - Aliza >> >> >> >> 2010/3/25 Joshua Gottesman <jos...@gm...>: >> >> - Hide quoted text - >> >> >> >>> ================== >> >>> Start of Stock Round 6 >> >>> ================== >> >>> Aliza has the Priority Deal >> >>> >> >>> Aliza sells 3 5% shares (15%) of CGR to Pool for $300. >> >>> CGR price goes from $100(E1) to $90(E2). >> >>> Aliza starts GT at $100 and pays $200 for 2 shares (20%) to Bank >> >>> Joshua sells a 5% share of CGR to Pool for $90. >> >>> CGR price goes from $90(E2) to $80(E3). >> >>> Joshua starts TGB at $100 and pays $200 for 2 shares (20%) to Bank >> > >> > ------------------------------------------------------------------------- >> >--- -- >> > Download Intel® Parallel Studio Eval >> > Try the new software tools for yourself. Speed compiling, find bugs >> > proactively, and fine-tune applications for parallel performance. >> > See why Intel Parallel Studio got high marks during beta. >> > http://p.sf.net/sfu/intel-sw-dev >> > _______________________________________________ >> > Rails-devel mailing list >> > Rai...@li... >> > https://lists.sourceforge.net/lists/listinfo/rails-devel >> > >> > >> > ------------------------------------------------------------------------- >> >--- -- >> > Download Intel® Parallel Studio Eval >> > Try the new software tools for yourself. Speed compiling, find bugs >> > proactively, and fine-tune applications for parallel performance. >> > See why Intel Parallel Studio got high marks during beta. >> > http://p.sf.net/sfu/intel-sw-dev >> > _______________________________________________ >> > Rails-devel mailing list >> > Rai...@li... >> > https://lists.sourceforge.net/lists/listinfo/rails-devel >> > >> > >> > ------------------------------------------------------------------------- >> >----- Download Intel® Parallel Studio Eval >> > Try the new software tools for yourself. Speed compiling, find bugs >> > proactively, and fine-tune applications for parallel performance. >> > See why Intel Parallel Studio got high marks during beta. >> > http://p.sf.net/sfu/intel-sw-dev >> > _______________________________________________ >> > Rails-devel mailing list >> > Rai...@li... >> > https://lists.sourceforge.net/lists/listinfo/rails-devel >> >> --------------------------------------------------------------------------- >>--- Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Rails-devel mailing list >> Rai...@li... >> https://lists.sourceforge.net/lists/listinfo/rails-devel > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |