Openbullet 2 Plugins Install Guide

1. Obtain the plugin .dll
   Download from a trusted source (e.g., a GitHub release). Never run untrusted plugins—they have full file system and network access.

2. Stop OpenBullet 2 (if running). Plugins are loaded at startup; hot-loading is not supported.

3. Place the .dll in the correct folder:

   # For a system-wide install (Linux example)
   cp MyCustomBlock.dll /opt/OpenBullet2/Plugins/
   Plugins have full access to your system – they can read files, send HTTP requests, and execute commands. Treat them like any executable.
   When a plugin author only provides source code (.csproj), you must compile it yourself. This is also the safest method. openbullet 2 plugins install
   
   
   Security Note: Building from source allows you to audit the code. Look for suspicious System.IO.File.Delete, Process.Start, or WebClient.DownloadString calls before compiling.
   
   
   I can’t stress this enough: A plugin has the same privileges as your user account.
   A malicious plugin can:
   
   Defense measures:
   
   If a plugin author refuses to share source code and only distributes obfuscated .dlls, do not install it.
   
   Before you can install OpenBullet 2 plugins, you need to ensure that you have the following:
   Q: Can I install multiple versions of the same plugin?
   
   A: No. Overwrite or uninstall the old version first.
   Q: Do I need to reinstall plugins after updating OpenBullet 2?
   
   A: Usually yes, if the plugin API changed. Check the changelog. Obtain the plugin
   Q: My antivirus quarantines a plugin – is it a false positive?
   
   A: Possibly, but never assume. Upload the plugin to VirusTotal. If only 1-2 generic detections (e.g., "HackTool"), it might be safe. If many advanced detections, avoid.
   Q: Where are plugin settings stored?
   
   A: In OpenBullet2/Data/settings.json. You can manually edit JSON there, but use the UI to avoid corruption.
   
   Final Tip: Join the official OpenBullet 2 Discord or subreddit for plugin announcements. The community often shares pre-built .ob2 files for niche providers (like custom 3rd-party proxy APIs) not found on GitHub. Always check the hash signature if provided.
   Before installing any plugin, verify your setup. Most plugin failures stem from environment mismatches. Stop OpenBullet 2  (if running)
   | Component | Requirement | Check Command |
   | :--- | :--- | :--- |
   | OpenBullet 2 | v2.0.0 or higher | Check version.txt in root dir |
   | .NET Runtime | .NET 6.0 or .NET 8.0 | dotnet --list-runtimes |
   | Plugin Format | .dll compiled for AnyCPU/x64 | Use file command on Linux or check PE headers |
   
   Critical: OB2 plugins are not cross-version compatible. A plugin built for OB2 v2.1.3 may crash on v2.3.0 if the RuriLib API changed.