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. All Versions
+ Add Version- Fixed: the explosion sound is back.** The predicted explosion was playing its sound through a call that does nothing on the client, and the mod was then silencing the server's sound as a "duplicate" of a sound that never played — so anchor detonations were completely silent. The boom now plays instantly on detonation.
- On 1.20–1.20.6 the sound stays server-timed (there's no injection point to suppress a duplicate on those versions), so it plays slightly later there instead of not at all.
- The sound is also no longer silenced when client-side explosion prediction is turned off.
Same coverage as before: **one jar for Minecraft 1.20 → 26.2**, the right hooks are picked automatically at launch.
- ~3x smaller download** — the jar went from ~335 KB to ~125 KB.
- The anchor jar is now **fully standalone**: it no longer bundles any end-crystal code.
- config/optiplus.json now only contains the section for the OptiPlus mod(s) you actually have installed.
- Safer config editing: deleting a setting from the file now falls back to its default instead of silently disabling the mod, and config writes are crash-safe.
- Same coverage as before: **one jar for Minecraft 1.20 → 26.2**, the right hooks are picked automatically at launch.
- Known issue:** the explosion sound is still missing when an anchor blows up — will be fixed in a future update.
- New: support for 1.20–1.20.6 and 1.21–1.21.4, plus 26.2 (previously 1.21.5–1.21.11 and 26.1)
- Settings now live in config/optiplus.json — toggle them without rebuilding
- Known issue: the explosion sound is currently missing when an anchor blows up; this will be fixed in a future update
- Now supports 1.20, 1.20.1–1.20.6, 1.21–1.21.11, 26.1 and 26.2
- Single Fabric client-side jar; no separate download per version
- On 1.20–1.20.4 the rapid re-placement raycast assist is omitted; the core anchor instant-clear still works
optiplus:disable or optiplus-anchor:disable (payload body is ignored). The flag resets on disconnect. See README for Bukkit / Fabric / Velocity examples.