Dependencies and Conflicts

Macros can be made to depend on other macros, whether they're local or remote (see GitHub Integration). They can also be made to depend on other plugins. If specified in the metadata, the framework will check for all the dependencies and fail to run/report in chat if any of the dependencies are not met.

On the other side, sometimes plugins may conflict with scripts. Common examples are YesAlready and TextAdvance, since they skip addons you might want to interact with. Plugins may also be set to conflict with those plugins, and if they are detected, they will be disabled during the run time of the script and re-enabled afterwards. Since there is no generic way to turn another plugin on and off, support for this is added on a per-plugin basis and requires that plugin to have an IPC capable of controlling the plugin's state.