Skip to content

Replay settings

Mint has a modern UI and an older card UI. They are two views of the same saved settings: changing a value in either UI changes the value Mint uses, and switching UI should show the same value. Settings are saved separately for each Minecraft version and synchronized with your OriginMint account.

Recording settings

These settings decide what a new recording contains. Turning one off does not remove that data from recordings you already made.

SettingWhat it does and when to use it
Record movementRecords movement keys such as forward, jump, sneak, and sprint. Turn it off only when the replay should not move the player.
Record clicksRecords mouse clicks and held mouse buttons. Use it for attacks, block interactions, and other click-driven actions.
Record cameraRecords where you look. Enable it when direction or aim matters.
Record chatRecords messages you send so the replay can send them again. Leave it off if a recording may contain private or one-time messages.
Record inventoryRecords inventory and container actions. Use it when the replay must select, move, or use items.
Start positionDraws a marker where the current recording began. Draw overlay in Settings must also be on.
BreadcrumbsDraws a trail behind you while recording. Draw overlay in Settings must also be on.

For example, a movement-only route normally needs Record movement and may need Record camera, but can leave clicks, chat, and inventory off.

Play settings

These settings decide which parts of a saved recording the replay uses. A play setting cannot recreate data that was not recorded.

SettingWhat it does and when to use it
Play movementsUses the recorded movement keys.
Play clicksUses recorded mouse clicks and held mouse buttons.
Play cameraUses the recorded view direction.
Play chatSends chat messages stored in the replay.
Play inventoryUses recorded inventory and container actions.
Show start ESPDraws a box where the replay starts. Draw overlay in Settings must also be on.
BreadcrumbsDraws the replay route. Green is already walked and red is still ahead. Draw overlay in Settings must also be on.

You can reuse one recording in different ways. For example, turn off Play clicks, Play chat, and Play inventory to inspect its route without performing those actions.

Camera settings

SettingWhat it does and what it requires
Camera alertBeeps three times, about 0.75 s apart, when a camera check stops the replay. It has no effect unless Sync camera or Lock camera detects a problem.
Sync cameraStops when your view no longer follows the recorded camera. Use this to catch drift during a replay.
Sync thresholdMaximum allowed camera difference in degrees. Only used by Sync camera. For example, 3 allows about three degrees of difference.
Lock cameraStops when the server unexpectedly turns your view away from the recorded camera.
Lock thresholdHow many degrees the server may turn your view before stopping. Only used by Lock camera.
Smooth cameraTurns smoothly to the recorded view when a replay starts or resumes instead of snapping. Only affects Play camera.
Skip camera startDoes not apply the camera angle or mouse buttons that were already held when recording began. Use it when the replay should begin from your current view/input state.

Sync camera watches whether the replay is following its recorded route. Lock camera watches unexpected server corrections. They can be used together.

Loop settings

SettingWhat it does and what it requires
Loop replayStarts the replay again after it finishes. Test one complete run before enabling it.
Loop amountTotal number of runs, including the first. Only used by Loop replay. 0 repeats until you stop it; 3 runs three times.
Loop delaySeconds to wait before the next run. Only used by Loop replay. 0 restarts immediately. Add a delay when the server or inventory needs time to settle.

Position settings

SettingWhat it does and what it requires
Position alertBeeps three times, about 0.75 s apart, when a position check stops the replay. It has no effect unless Sync position or Lock position detects a problem.
Sync positionStops when you move too far from the recorded route.
Sync thresholdAllowed route difference in blocks. Only used by Sync position. For example, 1 allows about one block of difference.
Lock positionStops when the server unexpectedly teleports or pushes you too far.
Lock thresholdHow many blocks the server may move you before stopping. Only used by Lock position.
Skip position startDoes not apply movement keys that were already held when recording began.

As with camera checks, Sync position watches route drift and Lock position watches server movement. Increase thresholds gradually on a laggy server instead of disabling the checks immediately.

Entity settings

These checks are part of paid Mint Client features. Player checks and non-player entity checks are configured separately.

SettingWhat it does and what it requires
Entity alertBeeps three times, about 0.75 s apart, when a nearby entity or player stops the replay. Requires Nearby entities or Nearby players.
Nearby entitiesStops when a selected living non-player entity is close enough.
Lock threshold (nearby entities)Distance in blocks. Requires Nearby entities.
Nearby entities listEntity identifiers used by the whitelist setting. Requires Nearby entities. The values are Minecraft/Mint internal identifiers such as the identifiers shown in the UI.
Nearby entities whitelistRequires Nearby entities. On: only listed identifiers can stop the replay. Off: listed identifiers are ignored and every other type can stop it. An empty list checks every type in either mode.
Nearby playersStops when a selected player is close enough.
Lock threshold (nearby players)Distance in blocks. Requires Nearby players.
Nearby players listExact player names used by the whitelist setting. Requires Nearby players.
Nearby players whitelistRequires Nearby players. On: only listed players can stop the replay. Off: listed players are ignored and everyone else can stop it. An empty list checks everyone.

Example: to ignore a friend, add their exact name to Nearby players list, turn Nearby players whitelist off, and enable Nearby players. To stop only for that friend, use the same list but turn the whitelist on.

Area settings

These checks are part of paid Mint Client features.

SettingWhat it does and what it requires
Area alertBeeps three times, about 0.75 s apart, when a block change stops the replay. Requires Lock area.
Lock areaRemembers blocks around the replay start and stops if watched blocks change.
Lock thresholdSize of the watched area in blocks. Only used by Lock area. For example, 5 watches for nearby changes within about five blocks.

Use Lock area when a route is only safe while nearby doors, blocks, or other terrain remain unchanged.

Inventory settings

These checks are part of paid Mint Client features. Sync inventory is the master switch for every setting in this section through Check stack size.

What to watch

SettingWhat it does and what it requires
Inventory alertBeeps three times, about 0.75 s apart, when an inventory check stops the replay. Requires Sync inventory.
Sync inventoryEnables the inventory checks below and compares watched items with the state at the start of the replay.
Sync inventory open inventoryStops when your inventory screen opens. Requires Sync inventory.
Sync inventory open containerStops when a chest or other container opens. Requires Sync inventory.
Lock slotChecks the item in your currently selected hotbar slot. Requires Sync inventory. You may select another slot if the item in that slot matches the expected item.
Lock slot changeStops if the server tells the client to change its selected hotbar slot. Requires Sync inventory. This is different from checking the item with Lock slot.
Lock hotbarChecks all hotbar slots. Requires Sync inventory.
Lock inventoryChecks the main inventory and hotbar. Requires Sync inventory. Armor is separate.
Lock armorChecks armor slots. Requires Sync inventory.

Lock slot change works across supported Minecraft versions. It watches a server-requested selected-slot change; it is not a general ban on you selecting a different slot yourself.

Which item differences matter

Each setting below requires Sync inventory and at least one of Lock slot, Lock hotbar, Lock inventory, or Lock armor.

SettingWhat counts as a difference
Check display nameA changed item display name.
Check IDA different item type, such as dirt instead of stone. This is the best basic check to enable first.
Check NBTChanged extra item data such as enchantments and custom properties. Use it when items must match exactly.
Check metadataChanged legacy item variant or damage metadata on Minecraft versions that use it.
Check durabilityDurability below Durability percentage.
Durability percentageMinimum durability remaining. Requires Check durability; for example, 20 stops below 20%.
Check stack sizeA changed number of items in a stack.

For many replays, start with Check ID and Check stack size. Add NBT, metadata, or durability only when that exact property matters; otherwise harmless item differences may stop the replay.

Containers during a replay

These four settings do not require Sync inventory. They decide which recorded actions continue while a container owns the screen, and only matter when the matching Play setting is on.

SettingOnOff
Check container clicksContinue replaying clicks.Wait to replay clicks until the container closes.
Check container chatContinue replaying chat.Wait to replay chat until the container closes.
Check container movementContinue replaying movement.Leave movement under the container’s control.
Check container cameraContinue replaying the camera.Do not move the camera while it is open.

General settings

Logging

Setting or actionWhat it does
Dump classesWrites transformed Minecraft classes to disk for advanced troubleshooting.
Trace pathingDevelopment builds only: writes detailed path ticks to mint/path-trace.log.
ScreenShows Mint log messages on screen.
ChatShows Mint log messages in Minecraft chat.
Message boxShows recent logs in Mint’s overlay message box.
Status panelShows an on-screen panel while you record or replay: time elapsed and left, which loop you are on, and how far you currently are from the recorded position and camera. Drag it, or resize it from its bottom-right corner, while Mint’s UI is open.
Draw overlayMaster switch for recording/replay world markers and breadcrumbs. The individual marker or breadcrumb setting must also be on.
Debug loggingLogs key, mouse, and character input events for troubleshooting. Leave it off for normal use.

Keybinds

SettingWhat it controls
GUIOpens or closes Mint’s UI.
RecordingStarts or stops recording.
Replay playStarts a replay, or toggles its current play/pause state.
Replay pausePauses or resumes a replay.
ResetRestores all settings to their defaults.

Other settings

Setting or actionWhat it does
AutosprintAutomatically sprints while normal movement conditions allow it.
Reset layoutRestores Mint’s window, navigation, and card positions without resetting replay settings.

Practical starting profiles

  • For a new route, enable the recorded/action groups it needs, start ESP, breadcrumbs, position sync, camera sync, and the relevant beeps. Run it once before enabling a loop.
  • For inventory automation, enable Sync inventory, choose the slots to watch, begin with Check ID and Check stack size, and add a loop delay if server updates need time.
  • On a laggy server, keep safety checks enabled but increase camera/position thresholds in small steps and use a loop delay.
  • If an old and modern UI ever show different values after switching, close and reopen the settings page and report it; they are expected to use the same saved value immediately.