Thanks so much Briarios! Yet again, to the rescue with bug reports. The good news is that this bug has been fixed in the upcoming 0.3.3 build, or at least it *should* be, based on my playtesting. If not, it should be a fairly easy patch from here as I have refactored the function responsible for this quite extensively to defend against future issues of this kind. Very appreciative of the message - it's not only great for bug hunting and fixing but also really gives me a kick to see so much interest and love for the game