I replied to your email just now. For everyone else running into this same issue: this is a bug that has snuck into the plugin at some point and has only now been discovered due to limited testing suite that I utilize. Big thank you to @ifrait for reporting it! It will be fixed in the next update.