Hi,
Thanks for reporting that, apparently that glitch still is viable since 0.2.2.8, I'll pass it to the dev to add to the list of things to be fixed.
Cheers
