Oh damn, ye that is a glaring oversight, I uploaded a fix for that in form of the 1.2 version.
For anyone curious, the 1.1 version is still up and has the described error.
Thank you for the feedback, and bug report ^^
