You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using scenario files' initializePlugin action it would be possible to load multiple plugins and test them together (allowing testing the inter-plugin calls).
However, it should still be possible to use the Checker in the classic single-plugin way, using the -p parameter.
The text was updated successfully, but these errors were encountered:
Note: The simulator currently has a single sandbox for the plugin; this will need extending, so that separate plugins don't overwrite each other's globals.
The Simulator contains everything - hook registrations, command handlers, worlds, players etc., so it'd be easier to have multiple sandboxes in a single Simulator. And yes, making cPluginManager:CallPlugin() work is the main intent of this issue.
I see it as low priority, though. First we want to be able to test plugins as best as we can.
Using scenario files'
initializePlugin
action it would be possible to load multiple plugins and test them together (allowing testing the inter-plugin calls).However, it should still be possible to use the Checker in the classic single-plugin way, using the
-p
parameter.The text was updated successfully, but these errors were encountered: