Thanks for the report, and the kind words!

I couldn't reproduce the bug on three different browsers, so there's probably some kind of an additional constraint for just what triggers the bug. Based on the description there should be an exception printed in the the JS console. If this happens again, I'd appreciate seeing the top of the stacktrace.

(And in the meanwhile, this is is an object lesson that exception reporting to the server has to be included even in an MVP. Anything that one player reports, dozens of others must have seen and not reported.)