Okay, so I think I finally managed to nail what was going on with a few things. I’m going to go a bit more in-depth here in case anybody is curious what’s going on backstage.

Fixed bug where verbcoin would crash game in odd clicking scenarios

This was causing a lot of crashes for players, and had to do with some dead spots on the GUI that weren’t passing values. The edge of the screen pushed the GUI around, resulting in NULL being where the game expected [something]. So it took some carefully placed null catches, but I think this bug might finally be fully squashed.

I’m pretty confident saying that because I explicitly broke the gui to create these errors more frequently, then protected against the crashes in the code. Then I put the gui back together properly, and for good measure added some additional coverage.

Part of why this took so long to figure out is that it’s simply a bug I had trouble reproducing. It involves a sort of large amount of clicks (or: a few amount of clicks per a large number of players) for it to happen.

If it happens again, please let me know.

Fixed exits from garden, shed, and cellar, which due to a regression could halt player progress.

So, while I was quickly finishing up some parts of the game towards the finish line, I hadn’t noticed that some of my room edges got mis-aligned, or my room entry points were outside the walkable areas. This made it so that when you exited the cellar, for example, you’d be stuck, unable to move. If you try to enter the shed while stuck, the player will successfully transition, but that’s sort of an unworkable solution. I managed to play around with some object properties to remove some collisions, and fix those entry points. Likewise, the edges for several rooms are closer inward.

Another issue is that I think screen DPI may be affecting the precision of the input mouse, so people on lower-DPI inputs (trackpads) may not be able to click as far over as they think they are, which also wouldn’t let them transition properly. Hopefully that’s fixed now.

Any further bugs?

This being a #AdvJam2016 game, it’s gonna be janky in a few ways. But if there’s any more crashes, I’ll do my best to fix them. If an error message pops up, you can press Ctrl+C to copy it in plain text. I’d appreciate any of these messages you may come across. Feel free to tweet me as well at @ShadeJackrabbit if that works more easily or directly or whatever.

Thanks for reading this far, and I hope you enjoy!