Getting started
Prerequisites, local setup, and your first build.
For approved script developers
Build scripts for SlugBot.
The compatibility layer, client-side APIs, project conventions, and release path—collected for developers building scripts that will run and ship inside the SlugBot client.
Read the references in your browserBrowse the complete Microbot API and DreamBot shim directly. The archive is still here when you want an offline copy.
Open Microbot API →START HEREChoose a section below, or use the developer docs rail on the left. Porting? Start with the DreamBot shim. Writing new code? Start with Microbot.
Build with SlugBot
Scripter documentation
Porting a DreamBot script? These guides cover the compatibility shim, project layout, local testing, and submission path.
DreamBot shim →
Available APIs and compatibility differences.
Plugin structure
Organize a script plugin the SlugBot way.
Build and test
Compile locally and verify in your client.
The complete references are now browsable: DreamBot shim and Microbot API. Need help? Join the SlugBot Discord.
Compatibility reference
DreamBot shim
The compatibility layer lets approved scripters port common DreamBot code into SlugBot. This reference shows what is implemented, what behaves differently, and when to use the native Microbot API instead.
Loading the shim reference…
The client-side API
Microbot API
The complete queryable API reference is loaded here in place. Queries are built from singleton caches, filtered fluently, and resolved with a terminal operation on the client thread.
Loading the Microbot API reference…
The path to a working script
Build, test, submit.
Build against the shim
Start from the plugin structure guide, keep client APIs on the correct thread, and use the compatibility reference before reaching for workarounds.
Run it in your client
Compile locally, load the readable QA jar, and test the actual task flow before handing anything over.
Make it production-ready
Remove secrets and hardcoded paths, handle user interruption, and keep the script recoverable from live game state.
Send it for release
Submit the source privately. Slug handles obfuscation, compilation, signing, and publication to the client.
Before you hand it over
Submission checklist
Your script is ready when it builds cleanly, runs without your development machine’s private files, and can recover naturally after a bank, dialogue, movement, or login interruption.
RELEASEDo not send a readable release jar or credentials. Follow the submission guide, send the source through the private handoff process, then contact Slug in Discord.