Hello! Yes, this plugin currently gets its plugin name dynamically from the script filename.
It uses this pattern:
const pluginName = document.currentScript.src.match(/([^/]+)\.js$/i)[1];
const raw = PluginManager.parameters(pluginName);
Then the same pluginName is also used for PluginManager.registerCommand(...).
So if Asset Protection / Source Code Protection loads the plugin through an alternate loader, or if document.currentScript.src no longer ends with the original .js filename, the regex match returns null and the plugin fails with:
Cannot read property '1' of null
Do I definitely have to modify it in my plugin? Couldn’t you adapt the program somehow to avoid changing the plugin?Thanks!