
OptiPlus-Anchor
Removes the wait between triggering a charged respawn anchor and the block clearing from the world. The anchor is set to air on the client immediately on interaction, so the slot is ready for the next placement without any server-confirmation lag.
Compatibility
Minecraft: Java Edition
Platforms
Supported environments
Tags
Creators
Details
OptiPlus Anchor
Zero-wait respawn anchor detonations — Minecraft 1.20 through 26.2. One jar, Fabric, fully client-side.
What it does
Blowing up a charged respawn anchor normally leaves a dead moment: the block is already gone, but your client is still waiting on the server's block update before it will let you place again. OptiPlus Anchor clears the anchor to air on your client the instant you interact, so the spot is free immediately and your next placement lands without the stutter.
The server still runs the real detonation. This only removes the empty-frame delay that blocks re-placing at the same spot.
Why you'd want it
- Instant re-placement — no dead frames between the detonation and your next anchor
-
- Works on any server — fully client-side, nothing needed server-side
-
- One jar for every version — it auto-detects your Minecraft version, so there's nothing to match up
-
- Lightweight — around 125 KB, and configuration is optional
Installation
- Install Fabric Loader for your Minecraft version
-
- Drop the jar into your
modsfolder
- Drop the jar into your
-
- Launch the game — the mod detects your version automatically
Supported versions
A single jar runs on Minecraft 1.20, 1.20.1–1.20.6, 1.21–1.21.11, 26.1 and 26.2 (Fabric, client-side).
Settings
Optional. On first launch the mod writes config/optiplus.json in your game folder:
{
"anchor": { "enabled": true, "clientSideExplosion": true, "debug": false }
}
Edit it and restart. Deleting a setting simply restores its default.
## For server admins
OptiPlus can be disabled per player by sending a plugin message on one of these channels when a player joins:
- `optiplus:disable` — disable everything
- `optiplus-anchor:disable` — disable only the anchor optimization
The payload body is ignored; only the channel matters. The flag resets on disconnect, so it needs re-sending on each join.

