Oops! — Misclick Undo for Minecraft

Oops! is a server-side Fabric utility mod for Minecraft 1.20.1 that fixes one of the oldest frustrations in the game: there is no undo. One misclick can break a rare block, place a block in the wrong spot, or cost you a stack you spent an hour gathering. Admin tools like CoreProtect can restore a server, but normal players have no way to fix their own small mistakes.

Oops! gives them exactly that — a short, personal, duplication-proof undo window for their own recent block actions, with none of the power of an admin rollback tool.

The Problem

Minecraft is unforgiving about accidents. Break the wrong block while building, and it's gone. Misplace a block in a redstone circuit, and you have to rebuild. There's no "wait, no" button. Existing solutions are either too heavy (full world backups and admin logs) or too powerful (creative mode). Nothing sits in the middle for the everyday player.

The Solution

Oops! quietly records each player's recent block breaks and block placements in a private journal. For a short window — 15 seconds by default — the player can run /undo to reverse their most recent action, or /redo to reapply it. After the window closes, the action is permanent, exactly as vanilla intended.

The journal is per-player. You can only undo your own actions, never another player's, and never a mob's or the environment's. Oops! is a personal safety net, not a griefing tool.

Built to Be Duplication-Proof

The obvious danger with an undo mod is item duplication: break four dirt, get four dirt, run /undo, and suddenly you have four dirt and four dirt blocks. Oops! is designed from the ground up to make that impossible.

Every undo is an atomic, two-sided transaction:

1. Verify the exact items from the original action are still in the player's inventory (matched by item ID, count, and full NBT/component data).

2. Remove those exact items.

3. Restore the block — all in the same server tick.

If the items are missing — dropped, stored in a chest, used in crafting, or lost on death — the undo is denied with a clear message explaining why. The rule is simple and strict: if the mod cannot prove an undo is safe, it refuses. No duplication, no silent failures, no half-applied transactions.

What Oops! Will Never Do

• ❌ Revive you after death

• ❌ Restore your health or hunger

• ❌ Recover items you dropped or lost on death

• ❌ Roll back PvP damage or mob kills

• ❌ Undo another player's actions

• ❌ Undo commands or environmental changes

The journal is cleared on death, logout, and server restart by default. Oops! is a misclick fixer, not a second life.

Safety Features

• Combat lock — no undoing while you're in a fight (10s by default)

• Dimension check — no cross-dimension undos

• Rate limiting — one undo per second

• Creative/Adventure gate — denied by default

• Multiblock handling — doors, beds, and tall plants are handled or refused cleanly

• Suffocation guard — refuses to place a block inside an entity

• Claim-mod integration — respects protection mods when present

• Transaction locks — double-submits and command spam are no-ops

Fully Configurable

Every behavior is tunable in config/oops.json: undo window length, journal depth, creative mode, combat lock, death/logout clearing, dimension rules, feedback style, and more. A built-in strict survival preset sets a 5-second window, combat lock, and aggressive journal clearing for servers that want the feature to feel as vanilla as possible.

Commands & Permissions

Permissions default to all players, with /oops reload restricted to operators. Works with any standard permission mod.

Server-Side and Client-Friendly

Oops! is server-side only. Install it on the server and vanilla clients can use it immediately — no client mod, no custom packets, no downloads for players. An optional client-side keybind can be added later, but it's never required.

Compatibility

• Minecraft: 1.20.1

• Loader: Fabric (Fabric API required)

• Java: 17

• Environment: Server-side; client optional

• Soft dependencies: claim/protection mods (optional integration)

Why Oops! Belongs on Your Server

• Reduces support tickets — players fix their own misclicks instead of pinging admins.

• Protects progress — a lost diamond ore or misplaced redstone component isn't a rage-quit moment anymore.

• Stays fair — short window, own actions only, no death recovery, no duplication.

• Costs nothing to try — drop it in, leave defaults, and it just works.

FAQ

Can I use this to recover items after death?
No. The journal clears on death. Oops! will never bring you back or return your gear.

Can I undo another player's block break?
No. You can only undo your own actions.

Won't this let players duplicate items?
No. Undo removes the exact items before restoring the block, in the same tick, and refuses if they're missing.

Do players need to install anything?
No. It's fully server-side; vanilla clients work out of the box.

Is it cheating?
That's a server-rule question. Oops! ships with a strict survival preset and is designed to feel like a quality-of-life safety net, not a rollback tool. Admins decide whether to enable it.