Help
Baritone not working? Common fixes
Most problems come from a mismatched loader or Minecraft version, or chat settings changed by another client.
Baritone doesn't load at all
- Check that your Minecraft folder now contains a baritone folder — Baritone creates it on first launch.
- Make sure the jar matches your loader: a Fabric build won't load on Forge or NeoForge, and the reverse.
- Make sure the jar matches your exact Minecraft version, and that the loader itself is installed for that version.
- Put the jar in the mods folder of the launcher profile you actually start.
Chat commands don't respond
- Use the # prefix, e.g. #help. Typing without a prefix only works while the chatControl setting is on.
- Some clients, such as Impact, turn chatControl off, and that change is saved. Use # or remove the line 'chatControl false' from baritone/settings.txt, then restart.
- If # does nothing, check that the prefixControl setting hasn't been turned off.
A command from another client doesn't work
- Commands like .goto in Impact or -path in other clients were added by those clients, not by Baritone. The Baritone equivalent is #goto x z.
The game crashes on start
- Remove other copies of Baritone — some clients and modpacks already include it.
- Use the Java version Minecraft recommends for your version.
- When reporting a crash, include your Minecraft version, loader and loader version, Baritone version and the crash log.
Baritone won't stop
- Type #stop (or #cancel). If that doesn't work, use #forcecancel.
It breaks or places blocks I don't want
- Toggle #allowBreak or #allowPlace to turn breaking or placing off.
- Add blocks to the blocksToAvoidBreaking setting to protect them.
Paths look wrong or chunks render strangely
- #repack re-caches nearby chunks and #render fixes glitched chunk rendering.
Still stuck? Re-download the right build for your version, check the commands list or read the FAQ.