Hey there @H4x03D! I plan to a look into the source a bit, but I’m not likely able to make a PR to correct this issue unless it’s a relatively unconnected component (and considering it’s part of the base of the plugin, probably not). Though more reporting on the matter could help it get resolved earlier!