Out of the box, minecraft baritone works. With the right settings, it flies. The default values lean cautious, which is sensible for a first run and frustrating by the third: routes get refused, walls stop the bot cold, and long journeys time out before they begin. This guide covers the settings that actually change how the bot behaves, what each one does in plain words, and a sensible starter setup you can paste in one setting at a time.
Change one thing at a time while you learn. That way you always know which switch caused which improvement.
How to View and Change Settings
Everything happens in chat. Type #settings to list every setting with its current value, and #set followed by the setting name and the new value to change one, like this: #set allowSprint true. Most settings accept true or false, and number settings accept a plain number. There are dozens of entries in the full list, but the handful below account for nearly every “why did it do that” moment you will ever have.
Movement Permissions: The Big Four
These switches decide what Baritone is allowed to do to the world while it paths, and they transform what the bot can achieve:
- allowBreak. When true, Baritone may break blocks that block its route. This single setting is the difference between a bot that digs through a hill and a bot that gives up at the bottom of it. Turn it on for mining and general travel.
- allowPlace. When true, Baritone may place blocks from your inventory to bridge gaps and pillar up. Essential for crossing ravines, rivers of lava and broken terrain. Keep blocks you are happy to spend, like cobblestone or dirt, in your inventory.
- allowSprint. Lets the bot sprint where sprinting helps. Trips get noticeably faster, at the cost of more hunger. Worth it on almost every journey longer than a stroll.
- allowParkour. Permits simple parkour-style jumps across gaps. Support is limited, so treat this as a bonus rather than a promise, and leave it off if the bot starts attempting jumps you would rather it walked around.
Closely related is allowDownward, which governs how willingly Baritone drops down into caves and shafts. If the bot keeps refusing an obvious descent, this is the setting to look at.
Speed of Thinking: Cost Heuristic and Timeouts
Two groups of settings control how hard Baritone thinks, and they matter most on long trips. The costHeuristic setting nudges the balance of the path search. A higher value pushes the search to be greedier and faster, racing toward the goal and sometimes accepting a slightly worse route. A lower value searches more carefully, which can find cleaner routes but takes longer to think. The default suits most trips; nudge it up if planning feels sluggish on huge journeys, and back down if routes look oddly wasteful.
The timeout settings, such as primaryTimeoutMS and the path timeout values, cap how many milliseconds Baritone may spend calculating before it gives up or works with what it has. Long-distance travel across unloaded terrain is where these bite: raise the timeouts and the bot thinks longer and succeeds more often on epic journeys, at the cost of a pause while it plans. If your cross-world trips keep failing with calculation errors, this is the fix to try before anything else.
Protecting Your World: Blocks to Avoid Breaking
Speed means little if the bot eats your base on the way out. The blocksToAvoidBreaking setting holds a list of blocks Baritone must never break, no matter how convenient the shortcut looks. Add the blocks your builds depend on: chests and storage, crafting and enchanting setups, portal frames, beds, and anything decorative you would hate to rebuild.
Set this list once, early, before the first long automated trip anywhere near your base. It takes a minute, it saves real grief, and it lets you leave allowBreak switched on with a clear conscience everywhere else in the world.
Seeing the Plan: renderGoal
The renderGoal setting draws your goal and the planned path in the world, and it is the best learning tool Baritone has. Turn it on while you experiment and you can literally see the route the bot chose, where it plans to dig, and where it intends to bridge. Many confusing behaviours explain themselves the moment you can see the plan: the “random” detour is a cheap route around a cliff, and the pause at a riverbank is the bot lining up its bridge.
Once the settings feel familiar, plenty of players leave renderGoal on permanently for long trips. It turns a black-box bot into a readable one, and it is the fastest way to learn how minecraft baritone thinks, which makes every other setting on this page easier to judge.
A Sensible Starter Setup
If you want a proven starting point for general travel and mining, work through this list in chat, then adjust to taste:
#set allowBreak true#set allowPlace true#set allowSprint true#set renderGoal true- Add your precious blocks to blocksToAvoidBreaking before travelling near your base.
- Raise the path timeout values only if long journeys start failing during calculation.
That combination gives you a bot that digs, bridges, sprints and shows its working, which is the setup most experienced users end up close to.
Write your working values down somewhere outside the game, too. Settings live in your configuration and generally survive restarts, but a fresh install, a new client or a borrowed computer starts from defaults. A thirty-second note with your six favourite values turns a rebuild from an afternoon of rediscovery into a minute of typing.
Settings for Specific Jobs
Once the starter setup feels normal, tune for the task in front of you. Three common jobs pull the settings in different directions:
- Long-distance travel. AllowSprint on, allowPlace on for bridging, and the path timeouts raised so multi-thousand-block journeys can finish calculating. RenderGoal is optional here; on very long trips many players switch it off once the bot is moving well.
- Mining sessions. AllowBreak is essential, allowPlace helps the bot cross the caves it digs into, and blocksToAvoidBreaking should be set before you go anywhere near a mineshaft you care about or a cave beside your base. Keep allowDownward in mind too, because a cautious bot hesitates above every drop shaft between it and the ore.
- Building projects. AllowPlace is the star, since a schematic build is one long sequence of placed blocks. AllowBreak depends on the site: on if the ground needs clearing first, off if the build sits inside a finished area you want untouched. RenderGoal earns its place here, letting you watch the plan while the structure rises.
Notice that no single profile is best at everything. The players who get the most from Baritone keep two or three mental presets and spend ten seconds adjusting before a job, the same way you swap tools before a task in the game itself.
Conclusion
The best minecraft baritone settings are the ones matched to the job: breaking and placing on for real terrain solving, sprinting on for distance, a protected-blocks list guarding your base, enough calculation time for the length of the trip, and renderGoal on while you learn. Start from the starter setup above, change one value at a time, and within a few sessions the bot will move the way you always wished it would.
Read next: