From: Nikolas Co <at...@at...> - 2015-12-24 10:27:35
|
Having never worked with Rails until a couple hours ago, I'm not sure of the accuracy of my diagnosis. That said, I think the problem is that tile 445 should have a Stop associated with its Station but does not; that is the immediate cause of the NPE. The reason it doesn't have the expected Stop is because Rails associates Stops with hexes. If there's a way for a tile lay to create a Stop, tile 445 isn't using it. I don't see how this could have worked in recent history… Searching the mailing list archives turned up a similar from 2011-05-18, subject "18AL - Lumber Terminal Tile lay issue", which makes me think this issue has existed for years. On Mon, Dec 21, 2015 at 3:23 PM Nikolas Co <at...@at...> wrote: > Hm, the web archive is displaying my attached text file instead of my > message. In case the message is mangled elsewhere: > (My understanding is that rails-devel is the venue for detailed bug > reports, so here we go…) > > In a game of 18AL, when a company attempts to use the ability of the > private "Brown & Sons Lumber Co." (B&SLC), namely laying tile #445, it > results in a NullPointerException. This is using Rails 2.0RC1. Save file > and logs attached (rails_out.txt is the stdout+stderr, where the NPE is > logged). > > I've simply confirmed that this is reproducible and haven't investigated > for likely causes. > > On Sun, Dec 20, 2015 at 11:41 PM Nikolas Co <at...@at...> wrote: > >> (My understanding is that rails-devel is the venue for detailed bug >> reports, so here we go…) >> >> In a game of 18AL, when a company attempts to use the ability of the >> private "Brown & Sons Lumber Co." (B&SLC), namely laying tile #445, it >> results in a NullPointerException. This is using Rails 2.0RC1. Save file >> and logs attached (rails_out.txt is the stdout+stderr, where the NPE is >> logged). >> >> I've simply confirmed that this is reproducible and haven't investigated >> for likely causes. >> > |