I'm sorry to hear that. I discovered that bug just after the submission period of the jam ended so was unable to fix it in time, but it has already been patched in the post jam update I am currently working on.
