Mining Efficency

Mining Efficiency

Mining Efficiency is a lightweight, client-side HUD mod that tracks how efficiently you’re mining, in real time.

Instead of counting diamond drops (which Fortune inflates), it counts diamond ore blocks broken — Diamond Ore and Deepslate Diamond Ore each count as exactly 1, regardless of enchantments. This makes it ideal for mining challenges where you need to break a specific number of ores.

Features

• Live HUD showing total blocks broken, total diamond ore broken, blocks/hour, and diamond ore/hour

• Session tracking separate from lifetime totals — a session starts when you join a world and resets when you leave; it automatically pauses when the game is paused

• Custom mining goals with a progress bar, percentage, remaining ores, and an estimated time to completion (shows “Calculating…” until there’s enough data to be meaningful)

• Configurable HUD — toggle on/off, reposition (4 corners), and rescale

• Optional on-screen notification (“+1 Diamond Ore”) when you break an ore

• Persistent stats saved to disk (.minecraft/config/mining-efficiency/), safe across restarts and crashes

Commands

/miningefficiency goal <amount>      – set a diamond ore goal

/miningefficiency goal               – show current goal and progress

/miningefficiency goal clear         – remove the goal

/miningefficiency reset stats        – reset lifetime totals

/miningefficiency reset session      – reset the current session

/miningefficiency hud toggle         – show/hide the HUD

/miningefficiency hud scale <value>  – resize the HUD

/miningefficiency hud position <top-left|top-right|bottom-left|bottom-right>

Requirements

• Minecraft 26.3

• Fabric Loader 0.19.5+

• Fabric API (required dependency)

• Java 25

Known limitation

This mod is 100% client-side and works by just dropping it into any world’s mods folder — no server install needed. It fully tracks mining in singleplayer and hosted LAN worlds. On a remote multiplayer server where the mod isn’t installed server-side, block-break counting won’t register, since the detection hook only fires on the logical server. This is a Fabric API limitation, not a bug — a future update may add client-side detection via Mixins to support arbitrary servers as well.