If you are hosting OpenBullet 2 via Docker, you must map the plugins directory using a volume to ensure your plugins persist across container restarts.
Once the application restarts, you can typically find your new custom blocks or features within the or the specific section for which the plugin was designed. openbullet 2 plugins install
OB2 loads all plugins into the same AssemblyLoadContext . If Plugin A needs Newtonsoft.Json v12.0 and Plugin B needs v13.0 , you get a and one plugin will fail. If you are hosting OpenBullet 2 via Docker,
I can’t stress this enough:
OpenBullet 2 scans the plugins folder only during the startup sequence. If the software is currently running: Save any ongoing work. If Plugin A needs Newtonsoft
To install plugins in OpenBullet 2, you typically need to place the plugin's .dll file into the designated Plugins folder within your OpenBullet 2 directory. This allows the program to automatically load the library and add custom blocks to your configurations.
: Avoid adding libraries that OpenBullet 2 already depends on (e.g., Newtonsoft.Json ), as this can cause version conflicts.