This issue has been fixed in the latest version of the plugin.
Thanks again @Dylan-Brotherston for your report!