Converting an OpenBullet 2 plugin into an M2 block

Overview

M2 Pro can turn an OpenBullet 2 plugin (.dll) into a native M2 block that shows up in the Stacker and configures like any built-in block. The conversion runs inside the app and the wrapper is compiled in-process, so the .NET SDK is not required. This guide uses the sample RandGenerator plugin (a simple Random GUID / UUID / DeviceID generator).

What you need

Steps

1. Open the converter

In M2, go to Tools → OB2 Plugin Converter.

2. Select the plugin

Click Select OB2 plugin (.dll) and pick your plugin file — RandGenerator.dll.

3. Convert

Click Convert. The log shows the wrapper being generated and compiled in-process:

Generated wrapper for block 'Generate' (2 params, output String)
Compiling wrapper (Roslyn, in-process)...
Compiled: …\Plugins\RandGenerator.M2.dll
Copied OB2 dll: …\Plugins\OB2\RandGenerator.dll

When it finishes you get “Conversion complete. Restart M2 to see the block in the Stacker (Plugins category).”

4. Check the produced files (optional)

Click Open Plugins folder. You should see:

• Plugins\RandGenerator.M2.dll — the native M2 block (UI + serialization).
• Plugins\OB2\RandGenerator.dll — the original OB2 plugin (holds the logic).

Both are needed: the block delegates execution to the original plugin at runtime.

5. Restart M2

Close and reopen M2 so the new block is loaded.

6. Use the block

Open a config in the Stacker, click Add Block, and open the Plugins category. Your converted block is there (here shown as OB2_Generate). Add it, set its parameters, and Run.

The block configures like any native one — in this example a type dropdown (DEVICEID / UUID / GUID), a KeepDashes option, a Variable Name, and Is Capture. Running it produces the generated value:

Video walkthrough

Watch the full conversion on the Telegram channel: t.me/OBM2pro/669.

The video shows, end to end: opening the converter, selecting RandGenerator.dll, converting (log compiling in-process, no SDK), the “restart M2” dialog, the two produced files, restarting M2, and adding + running the block from the Stacker Plugins category.

Notes & limits

• Re-converting in the same session. If you rebuild the same plugin .dll and convert it again without restarting, M2 may still report the previously loaded block. Restart M2 to pick up the new version.
• Self-contained blocks work best. Parameters go in by value and a single output comes back. Blocks that share state across the pipeline (cookies, a reused HTTP client, custom objects) are not bridged — the converter suits standalone blocks (generators, hashing, transforms, simple HTTP).
• Keep it in the app. A separate command-line converter exists for developers, but end users should always use this Tools page — path handling and compilation are automatic.

Troubleshooting