Pitchfork
Pitchfork
Intro to PitchforkQuick Start Guide
ProhibitionDreamBotTRiBotInuBotRuneLiteStormClientOSBot
GlossaryFAQ
Client Support

DreamBot

Pitchfork support for DreamBot

DreamBot

Official site

DreamBot is the most thoroughly integrated client in Pitchfork. We ship a custom Java wrapper that exposes account credentials, script selection, breaks, world hopping, mouse speed, proxy injection, and the full set of DreamBot CLI flags through the Pitchfork UI.

Support Status

Fully supported. Both DreamBot 3 (dreambot) and DreamBot 4 (dreambot4) client types are recognized.

How to use

  1. Install DreamBot from dreambot.org on the machine that will run your agent. The Pitchfork wrapper finds the JAR by convention — no path field to fill in.
  2. Make sure your DreamBot account is set up and verified (login at least once on that machine).
  3. In Pitchfork, go to Clients → Client Types tab → click Create Instance on the DreamBot tile.
  4. Set:
    • Instance Name — anything memorable
    • Memory (MB) — heap for the JVM (default 512 is fine for one client; bump to 1024–2048 for memory-hungry scripts)
    • (Optional) DreamBot-specific settings under Advanced Configuration — see Configuration for JVM args vs Client args
  5. Save, then launch a script from Accounts with this client selected. Pitchfork's wrapper handles login, script selection, and lifecycle.

The Create Client Instance modal looks like this with DreamBot selected:

Create Client Instance modal — DreamBot selected

Configuration

Pitchfork understands the full DreamBot CLI surface. Defaults are sane; the most commonly tuned options are:

FieldTypeDefaultNotes
fpsint (1–50)15Cap render rate to reduce CPU/GPU load
mouseSpeedint (1–100)50Higher = faster mouse
breaksstring""DreamBot break-pattern string (e.g. 45-60,5-10)
covertModeboolfalseHides DreamBot from common detection vectors
freshStartboolfalseClears cached state on launch
shareCachebooltrueReuse the OSRS cache across instances
lowDetail / disableAnimations / disableModels / disableSoundsboolfalseReduce client resource use
noClickWalk / menuManipulation / noInputLoginboolvariesBehavioural anti-ban toggles
worldHopOnLoginErrorboolfalseAuto-hop on login failure
worldHopOnLoginErrorMaxint5Max hops before giving up
worldHopOnLoginErrorWorlds / WorldsBlacklistcsv""World allow/deny lists
dismissRandomEventsbooltrueAuto-dismiss random events
deleteAccountOnBanboolfalseRemove the account from Pitchfork on ban

Proxy

Set the proxy fields on the Client Instance and Pitchfork passes -proxy host:port (or user:pass@host:port if credentials are provided) to DreamBot automatically.

Webhooks

DreamBot ban/death/level/script-event webhooks are wired through the standard Pitchfork notification fields (webhookUrl, notifyOnBan, notifyOnDeath, etc.) — no client-side configuration needed.

Was this page helpful?

Prohibition

Pitchfork support for the Prohibition OSRS client

TRiBot

Pitchfork support for TRiBot and TRiBot X

On this page

DreamBotSupport StatusHow to useConfigurationProxyWebhooks