Supported Formats
| Format | Extension | Source | Import Quality |
|---|---|---|---|
| SilverBullet / OB1 | .svb | OpenBullet 1.x | 95% |
| OpenBullet 2 Package | .opk | OpenBullet 2.x | 90% |
| LoliCode Script | .loli | OB2 script files | 85% |
| OpenBullet 2 JSON | .json | OB2 exports | 90% |
Prepare Your Config File
Locate your OpenBullet config file. Common locations:OpenBullet 1 (SilverBullet):OpenBullet 2:
.opk files are ZIP archives containing:script.loli- Main LoliCode scriptmetadata.json- Config name, author, etc.settings.json- Runner/proxy/data settings
Import via GUI
Method 1: File Menu
- Click File → Import Config
- Select your
.svb,.opk,.loli, or.jsonfile - Review the import warnings (if any)
- Click Import
- Drag the config file into the IronBullet window
- Confirm import in the dialog
Import via CLI
You can run imported configs directly from the command line:IronBullet auto-detects the format and imports on-the-fly.
Review Import Warnings
After import, check the Warnings panel (bottom of screen).Common warnings:Unsupported Block TypeSome OB2 blocks don’t have IronBullet equivalents. They’re converted to disabled Script blocks with the original code in comments.Variable Reference ConversionOpenBullet uses Advanced string functions may need manual implementation.
<USER> for wordlist variables. IronBullet uses <input.USER> for clarity.Unknown FunctionFix Converted Blocks
Review blocks marked as Script or disabled:IronBullet (CaseSwitch block):
- Open the block settings
- Read the commented code
- Recreate using IronBullet blocks:
Translate→ Use IfElse or CaseSwitchCountOccurrences→ Use ParseRegex with regex groupsSubstring→ Use StringFunction block
Update Variable References
IronBullet uses a different variable namespace:
The importer handles most conversions automatically.
| OpenBullet | IronBullet | Description |
|---|---|---|
<USER> | <input.USER> | Wordlist data slice |
<PASS> | <input.PASS> | Wordlist data slice |
<SOURCE> | <data.SOURCE> | HTTP response body |
<RESPONSECODE> | <data.RESPONSECODE> | HTTP status code |
<ADDRESS> | <data.ADDRESS> | Final URL after redirects |
<COOKIES(name)> | <data.COOKIES["name"]> | Cookie value |
Test the Imported Config
Before running on a full wordlist:
- Press F5 (Debug mode)
- Enter test data:
test@example.com:password123 - Verify all blocks execute correctly
- Check the Variables panel for expected outputs
- Review Request/Response tabs for HTTP calls
Adjust Settings
Review imported settings (footer panels):Data Settings:
- Wordlist type (Credentials, Emails, etc.)
- Separator character
- Slice names (USER, PASS)
- OB1
NeedsProxies: true→ Proxy Mode: Rotate - OB2
UseProxies: true→ Proxy Mode: Rotate - Ban duration (default: 300s)
- Threads (OB1/OB2
SuggestedBots) - Concurrent per proxy
- Continue statuses
Import Code Reference
The importer logic is in~/workspace/source/src/import/:
SVB (SilverBullet) Import
Example .svb structure:- HttpRequest (POST to example.com/login)
- KeyCheck (Success on 200, Fail on 401)
OPK (OpenBullet 2) Import
Archive contents:BLOCK:HttpRequest→BlockType::HttpRequestBLOCK:Parse(MODE:Json) →BlockType::ParseJSONBLOCK:Keycheck→BlockType::KeyCheck=> CAP @VAR→output_var: "VAR", capture: true
Unsupported Features
Some OpenBullet features don’t map directly to IronBullet:| OB Feature | IronBullet Alternative |
|---|---|
| C# code blocks | Rhai Script block (limited) or Plugin |
| LoliScript JUMP/LABEL | Use IfElse/Loop blocks |
| Selenium WebDriver | Browser automation blocks |
| TCP Raw socket | TcpRequest block |
| Custom CaptchaSolver | Plugin or Webhook |
Security Scan
All imported configs are scanned for security issues:Tips
The importer is read-only. Original
.svb/.opk files are never modified.Troubleshooting
Import fails with “No blocks found”- Check file format (must be valid .svb/.opk/.loli)
- Try opening in a text editor to verify it’s not corrupted
- Update
<USER>→<input.USER>references - Check Data Settings separator matches your wordlist
- Review KeyCheck conditions (may need adjustment)
- Check for unsupported string functions
- Test in Debug mode with known-good data