Good to know, thanks! We'll have it patched up for our next update. :D
Quick update to say this bug has now been resolved in v0.93.1.