You can download SONiVOX installers below and if you have any questions please contact customer support here.
We thank our loyal customers for their valued support.
The SONiVOX team
I can, however, provide one of the following safe, legal alternatives — pick one:
Which option do you want?
By following these steps, you can easily install and manage OpenBullet 2 plugins to enhance the functionality of the tool.
How to Install Plugins in OpenBullet 2: A Quick Guide OpenBullet 2 is a powerhouse for web automation and penetration testing. While it comes packed with native features, its true flexibility shines through plugins and external libraries. Whether you're adding custom blocks for complex math or integrating third-party APIs, knowing how to properly set up these add-ons is essential.
Here is a straightforward guide to getting your OpenBullet 2 plugins up and running. 1. Locate Your UserData Folder
The directory structure in OpenBullet 2 is modular. All custom content lives in the UserData folder within your main application directory. Navigate to your OpenBullet 2 installation folder. Open the UserData folder.
Look for the Plugins subfolder. If it doesn't exist, you can manually create it. 2. Prepare the Plugin Files
Most OpenBullet 2 plugins or external libraries are distributed as .dll files.
For Pre-built Plugins: Simply download the .dll from a trusted source, such as the official OpenBullet GitHub.
For Custom External Libraries: If you want to use a standard .NET library (like Humanizer or a custom JSON parser), you must build it as a .NET 8 console app first to generate the necessary .dll and its dependencies. 3. Move and Restart Once you have your files ready:
Copy the .dll file (and any required dependency files) into UserData/Plugins.
Restart the OpenBullet 2 application. The software scans this folder on startup to register new blocks and extensions. 4. Verify the Installation After restarting, check that your plugin is active:
For Block Plugins: Open the Config Studio (Stacker). Search for the new block names in the block selector. Custom blocks often appear under a specific category defined by the plugin creator.
For External Libraries: These can be called directly within LoliCode using standard C# syntax once the library is recognized by the environment. Pro-Tip: Building Your Own
If you're a developer looking to extend OpenBullet 2 yourself, check out the OB2PluginSample repository. It provides a well-commented template for creating custom blocks with parameters and dropdown lists.
Need help with a specific plugin? Let me know the name of the plugin or what functionality you're trying to add!
openbullet/OB2PluginSample: Sample plugin for OB2 ... - GitHub
Sample plugin for OB2 with a dependency. Please refer to this guide to understand how to use this.
Sample plugins for OpenBullet with well-commented code. - GitHub
OpenBullet Plugins * Resources. Readme. * License. MIT license. * Stars. 37 stars. * Watchers. 5 watching. * Forks. 13 forks. openbullet - GitHub
How to Install and Manage Plugins in OpenBullet 2: A Complete Guide
OpenBullet 2 is a powerful, flexible automation suite used for everything from web scraping to penetration testing. One of its greatest strengths is its modularity. Through the use of plugins, you can extend the core functionality of the software, adding new blocks, custom parsing methods, or unique integrations that aren’t available out of the box.
If you’re looking to supercharge your setup, here is a straightforward guide on how to install and manage OpenBullet 2 plugins. What are OpenBullet 2 Plugins?
Plugins are .dll files specifically compiled for OpenBullet 2. They allow developers to add "Blocks"—the building blocks of a configuration—that perform specialized tasks. For example, a plugin might add a block for solving a specific type of captcha, interacting with a unique database, or handling advanced encryption. Step-by-Step: How to Install Plugins
Installing a plugin in OpenBullet 2 is a manual process, but it’s very simple once you know where the files go. 1. Download the Plugin
First, you need the plugin file. Most reputable plugins are shared on GitHub or specialized automation forums. Ensure you are downloading a .dll file that is compatible with OpenBullet 2 (original OpenBullet plugins will not work). 2. Locate Your OpenBullet 2 Folder
Navigate to the directory where your OpenBullet 2 executable is located. If you are running the software via Docker, you will need to access the mapped volume on your host machine. 3. Move the DLL to the Plugins Folder
Inside the main OpenBullet 2 folder, you will see a subfolder named Plugins. Open the Plugins folder. Drop your downloaded .dll file directly into this folder. openbullet 2 plugins install
Note: Do not put the DLL inside a sub-folder within the Plugins directory; it must be in the root of the Plugins folder for the software to "see" it. 4. Restart OpenBullet 2
OpenBullet 2 scans the plugins folder only during the startup sequence. If the software is currently running: Save any ongoing work.
Close the application (or stop the dotnet process/Docker container). Restart OpenBullet 2. 5. Verify the Installation
Once the software has reloaded, navigate to the Config Developer or Stacker tab. Look through the available blocks list. You should now see new categories or blocks associated with the plugin you just installed. Important Safety Tips
Because plugins are executable code (.dll), they can pose a security risk. Only install plugins from trusted sources. A malicious plugin could potentially steal your configurations, proxies, or even infect your system. Always check for open-source versions where you can inspect the code before compiling it yourself. Troubleshooting Common Issues
Plugin not appearing: Ensure you are using the correct version of OpenBullet 2 (e.g., the .NET version vs. the older framework version).
Crashing on startup: If OpenBullet 2 fails to launch after adding a plugin, the DLL is likely corrupted or incompatible. Remove it from the Plugins folder and try restarting.
Missing Dependencies: Some advanced plugins require additional libraries or runtimes installed on your OS (like specific .NET SDKs). Check the plugin's documentation for requirements. Conclusion
Adding plugins to OpenBullet 2 opens up a world of automation possibilities. By following the simple "Download, Drop, Restart" method, you can keep your toolkit updated with the latest community-driven features.
Do you have a specific plugin you're trying to get working, or
Installing plugins in OpenBullet 2 (OB2) is a straightforward process that allows you to extend the software's functionality with custom blocks and external C# libraries. Whether you are using the Native or Web client, the installation method remains largely the same. 1. Locate the Plugins Folder
To install a plugin, you must first find your UserData folder. OpenBullet 2 stores all user-specific data, including plugins, in this directory.
Default Path: Look for a folder named UserData inside your main OpenBullet 2 installation directory.
Plugins Subfolder: Inside UserData, there is a dedicated Plugins folder. If it doesn’t exist, you can manually create it. 2. Download and Prepare the Plugin
Plugins for OpenBullet 2 typically come as .dll files. These files may be standalone or bundled with other dependencies.
Trusted Sources: Only download plugins from reputable developers or the official OpenBullet GitHub.
External Libraries: If you want to use a NuGet package or an external library in your LoliCode scripts, you will also need its .dll file. 3. Move the Files Once you have the .dll file:
Close OpenBullet 2 to ensure the software can scan for new files on startup.
Copy and paste the .dll file (and any required dependencies) into the UserData/Plugins folder.
Avoid Conflicts: Do not add libraries that OpenBullet 2 already uses (like Newtonsoft.Json), as this can cause the program to crash. 4. Verify the Installation After moving the files, restart OpenBullet 2.
New Blocks: If the plugin adds custom blocks, they should now appear in the Stacker under a new category.
LoliCode Usage: To use an external library in a script, you may need to add a using statement at the top of your LoliCode, such as using YourPluginNamespace;. Troubleshooting Common Issues
Missing .NET Runtime: OpenBullet 2 and its plugins require the .NET Desktop Runtime to function. Ensure you have the latest version (currently .NET 8 for recent builds).
Plugin Not Loading: Double-check that you placed the files in the UserData/Plugins folder and not just the root Plugins folder if you have one.
Immediate Crashing: This often happens if you have added a conflicting library or if the .dll is corrupted. Try removing the recently added plugin to see if the software stabilizes.
Do you need help finding specific plugins for a particular task, or openbullet/OB2PluginSample: Sample plugin for ... - GitHub
GitHub - openbullet/OB2PluginSample: Sample plugin for OB2 with a dependency · GitHub. Plugins - OpenBullet 2 I can, however, provide one of the following
OpenBullet 2's plugin installation system is a straightforward, folder-based process designed to easily extend the tool's core web-scraping and automation capabilities. Ease of Installation
Installing plugins is highly accessible even for beginners, as it avoids complex installers or command-line requirements:
Simple File Transfer: To install a plugin, you simply place its .dll file and any necessary dependencies into the Plugins folder within the OpenBullet 2 directory.
Automatic Integration: The software automatically detects and loads these libraries upon startup.
Dependency Management: Standard libraries (like Newtonsoft.Json) already used by OpenBullet 2 do not need to be added manually; doing so can actually cause software conflicts. Functional Impact
The plugin system significantly enhances OpenBullet 2's versatility as an automation suite:
Custom Block Support: Plugins allow users to create and use custom logic blocks within their configurations, which is vital for complex scraping or parsing tasks.
Community Resources: Being open-source, there is a wealth of community-created plugins and sample code on GitHub that users can adapt for their own needs.
Advanced Features: Plugins often support sophisticated features like CAPTCHA solving, multithreading, and custom request manipulation, making automated tasks appear like legitimate user activity. Usage Considerations
While the installation is easy, users should be mindful of the following:
Source Trust: Since plugins use .dll files that execute code, only download them from reputable community forums or verified GitHub repositories to avoid security risks.
Legal Disclaimer: OpenBullet 2 is a powerful tool often used for credential stuffing or DDoS attacks; developers emphasize that performing these actions without permission is illegal.
OpenBullet 2: Overview of the Web Scraping Tool - Proxy-Seller
Installing plugins in OpenBullet 2 (OB2) is a straightforward process that allows you to expand the platform's automation capabilities with custom blocks or external C# libraries. How to Install Plugins
To add a new plugin or external library to your OpenBullet 2 instance, follow these steps:
Locate the Plugins Folder: Navigate to your main OpenBullet 2 directory. Locate the UserData folder, and inside it, find the Plugins folder.
Add the Plugin Files: Copy your plugin's .dll file (and any required dependencies) directly into this folder.
Restart the Application: For the new functionality to be recognized, you must restart OpenBullet 2.
Verify Loading: Upon restart, the program will automatically detect and load the library. You can then manage or use these new blocks within the "Plugins" tab or when creating a new Config. Key Considerations
Conflicts: Do not add libraries that OpenBullet 2 already depends on (such as Newtonsoft.Json). Adding these to the Plugins folder can cause software conflicts.
Building from Source: If you are developing a custom plugin, you must use the .NET 8 SDK to compile your project into a .dll before moving it to the Plugins folder.
Safety: Only install plugins from trusted sources like the OpenBullet GitHub or reputable community members to avoid potential security risks.
For official documentation and sample plugin code, you can refer to the OpenBullet 2 Plugin Guide and the OB2 Plugin Sample Repository. Openbullet 2 Plugins Install [updated]
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. Steps to Install Plugins
Locate your installation folder: Navigate to the directory where you installed OpenBullet 2 (Native or Web version).
Find the Plugins folder: Look for a folder named Plugins. In many installations, this is located inside the UserData directory (e.g., UserData/Plugins).
Add the plugin file: Copy the .dll file of the plugin, along with any of its required dependencies, into this folder. Which option do you want
Restart OpenBullet 2: The program loads plugins during startup. If it is already running, you must close and restart it for the new plugins to appear.
Verify installation: Open the Plugins section in the OpenBullet 2 interface to view and manage active plugins. Important Considerations
Dependency Conflicts: Avoid adding libraries that OpenBullet 2 already depends on (e.g., Newtonsoft.Json), as this can cause version conflicts.
Source Reliability: Only download plugins from trusted sources like the OpenBullet GitHub or verified community members.
Compatibility: Ensure the plugin is designed specifically for OpenBullet 2. Plugins from the original OpenBullet (OB1) are generally not compatible. External Libraries - Introduction | OpenBullet 2
Installing plugins in OpenBullet 2 is a straightforward manual process, but it requires precise placement of files to ensure they load correctly upon startup. Quick Install Guide Locate the Folder: Go to your main OpenBullet 2 directory. Find UserData: Open the UserData folder.
Open Plugins: Navigate to the Plugins subfolder (create it if it does not exist).
Add Files: Place your .dll plugin file and any of its required dependencies into this folder.
Restart: Close and relaunch OpenBullet 2 for the changes to take effect. Key Technical Details
Auto-Loading: The program automatically scans the UserData/Plugins folder on startup. You do not need to "enable" them manually in the UI.
Conflict Prevention: Avoid adding libraries that OpenBullet 2 already uses (e.g., Newtonsoft.Json). Adding duplicate core libraries can cause the program to crash or behave unexpectedly.
LoliCode Integration: Plugins are primarily used to expand the capabilities of LoliCode scripts, allowing you to use external C# libraries for tasks like complex data parsing or custom API interactions.
Dependency Support: If your plugin relies on other files, they must all be in the same Plugins folder. However, certain elements like "enums" in external dependencies may not be supported unless they are included directly in the main plugin project. Troubleshooting Common Issues
Plugin Not Showing: Ensure you are using the correct version for your .NET runtime (OpenBullet 2 typically uses .NET 6 or 8).
Immediate Crashing: This often indicates a missing .NET Desktop Runtime or ASP.NET Core Runtime. Ensure these are updated to the latest versions from Microsoft.
Blocked Files: On Windows, sometimes .dll files downloaded from the internet are "blocked" by security settings. Right-click the file, select Properties, and click Unblock if the option appears.
💡 Pro Tip: If you are developing your own plugins, you can reference the Official OB2 Plugin Sample on GitHub to see the required project structure and how dependencies should be handled. If you'd like, I can help you:
Find a specific plugin for a task (e.g., CAPTCHA solving or database logging).
Debug a specific error message you're seeing when you try to start the app.
Write a basic C# template to start building your own plugin. AI responses may include mistakes. Learn more External Libraries - Introduction | OpenBullet 2
After downloading a plugin (e.g., MyCustomPlugin.dll), ensure it is compiled for the correct .NET version (same as your OB2 version). Some plugins come as .zip archives; extract them.
For specific plugins or detailed installation instructions, the OpenBullet 2 community forums or official documentation are invaluable resources. These platforms often provide insights into how to get the most out of OpenBullet 2, along with troubleshooting tips.
Fix: Disable all other plugins, restart, then enable one by one to find the conflict. Some plugins override the same interface (e.g., two HTTP client plugins).
Here’s where most users stumble. A plugin might depend on a specific version of BouncyCastle, HtmlAgilityPack, or FFMpegCore.
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 version conflict and one plugin will fail.
Installing plugins in OpenBullet 2 is straightforward once you understand the modular system. Use the built-in Plugin Manager for .ob2 files, manually copy .dlls for advanced setups, and always verify the source’s trustworthiness. Restarting the application between install and enable steps is crucial – a forgotten restart is the number one cause of "it didn’t work."
By following this guide, you can now install, configure, and troubleshoot any OpenBullet 2 plugin – from custom captcha solvers to bleeding-edge HTTP/2 runners. Keep your plugins updated, respect ethical boundaries, and you’ll unlock the true power of security automation.