Re: [Rails-devel] Possible 1889 tile promotion bug

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

The upgrade chart in my copy of the 1889 rules (version 1.0c) doesn't
specify #39 as a valid upgrade for #28 and #29.  Is that an error?

Erik.

> -----Oorspronkelijk bericht-----
> Van: Justin Rebelo [mailto:jus...@gm...]
> Verzonden: donderdag 17 februari 2011 22:58
> Aan: Development list for Rails: an 18xx game
> Onderwerp: Re: [Rails-devel] Possible 1889 tile promotion bug
> 
> Stefan, if you load this up you should find that hex F5 demonstrates the
bug.
> 
> On Thu, Feb 17, 2011 at 1:55 PM, Justin Rebelo <jus...@gm...>
> wrote:
> > Oh, I actually had assumed that rails wasn't enforcing those types of
> > rules in any game. I will have a look and see if that's it.
> >
> > On Thu, Feb 17, 2011 at 1:05 PM, Stefan Filonardi <jk...@gm...> wrote:
> >> Hello Justin,
> >>
> >> Am 17.02.2011 21:39, schrieb Justin Rebelo:
> >>> I found in 1.4.1 during an 1889 game that I was unable to upgrade a
> >>> tile that seems like a perfectly legal upgrade. It was either a tile
> >>> #28 or #29 which should upgrade to a #39 but this was not offered as
> >>> an option. I imagine this is a really simple thing for developers to
> >>> verify, but if you need a save file, I can provide one.
> >>
> >> Are you sure that the problem is not Rule 6.2 "Upgrading Tiles"?
> >> ".... at least one new track on the new tile must form part of a
> >> legal route of the company ...."
> >>
> >> There is only one new track part going from 28/29 to 39.
> >>
> >> If you are coming from the "united" part of the track, the new track
> >> isn't automatically part of a legal route for the building company.
> >>
> >> Hoping to not have added confusion,
> >> ciao stefan
> >>
> >> ---------------------------------------------------------------------
> >> --------- The ultimate all-in-one performance toolkit: Intel(R)
> >> Parallel Studio XE:
> >> Pinpoint memory and threading errors before they happen.
> >> Find and fix more than 250 security defects in the development cycle.
> >> Locate bottlenecks in serial and parallel code that limit performance.
> >> http://p.sf.net/sfu/intel-dev2devfeb
> >> _______________________________________________
> >> Rails-devel mailing list
> >> Rai...@li...
> >> https://lists.sourceforge.net/lists/listinfo/rails-devel
> >>
> >