Overview#
Multi Mine, developed by AtomicStryker, is a fundamental utility mod that overhauls the mining mechanics in Minecraft. In the vanilla game, if a player stops hitting a block before it is fully broken, the progress is immediately lost. Multi Mine changes this by saving the damage state of blocks, allowing players to walk away, switch tools, or even have multiple players contribute to breaking a single block simultaneously.
The mod is designed to be lightweight and server-friendly, ensuring that block damage does not bloat save files or interfere with world data. It is fully compatible with both vanilla and modded blocks, making it a staple for large modpacks where mining high-durability blocks can be time-consuming.
Core Mechanics#
The mod introduces several key mechanical changes to how blocks interact with player tools:
Persistent Block Damage
When a player begins mining a block, the 'cracking' animation progresses as usual. However, if the player stops mining, the cracks remain on the block. This allows the player to:
- Pause to fight off a mob and return to the exact same mining progress.
- Switch to a more efficient tool mid-way through mining.
- Move to a different block and return to the previous one later.
Collaborative Mining
One of the most powerful features of Multi Mine is its networked capability. Multiple players can strike the same block at the same time. The damage dealt by each player is cumulative, meaning two players mining a single block of Obsidian will break it twice as fast as a single player. This makes team-based excavation significantly more efficient.
Block Damage Limits
To prevent server lag and memory issues, the mod maintains a 'buffer' of damaged blocks. By default, the mod tracks up to 30 damaged blocks across the entire server. If a 31st block is damaged, the oldest damaged block in the queue will instantly reset to its full health state.
Natural Regeneration
Blocks do not stay damaged forever. After a short initial delay where the block remains at its current damage level, it will begin to 'heal' or regenerate. The cracks will slowly disappear until the block returns to its original, undamaged state. This prevents the world from being permanently covered in 'cracked' textures from abandoned mining attempts.
Configuration#
Multi Mine includes a robust configuration system that allows server administrators and players to fine-tune the mod's behavior. The configuration file is typically found in the /config/ folder of the Minecraft directory.
| Setting | Description | Default Value |
|---|---|---|
| Block Regrow Delay | The time in milliseconds before a damaged block starts to regenerate. | 5000 ms |
| Maximum Damaged Blocks | The total number of blocks that can hold damage data simultaneously. | 30 |
| Excluded Block IDs | A list of specific blocks that Multi Mine should ignore (e.g., blocks that should always break instantly or never save progress). | Empty |
| Excluded Item IDs | A list of tools or items that should not trigger the Multi Mine progress saving. | Empty |
Block Blacklisting
Users can specify certain blocks to be ignored by the mod. This is useful for blocks that have custom breaking logic or for preventing players from 'pre-damaging' certain environmental hazards. The blacklist supports registry names (e.g., minecraft:obsidian).

Technical Details#
Multi Mine operates primarily on the client-server bridge. When a player clicks a block, the client sends the damage data to the server. The server then broadcasts this damage state to all nearby players, ensuring that everyone sees the same cracks on the same blocks.
- Save Game Integrity: Multi Mine does not save block damage to the world's
regionfiles. If a server restarts, all block damage is cleared. This ensures that the mod never corrupts world saves or increases file sizes. - Compatibility: The mod uses standard Forge/Fabric events for block breaking, meaning it is compatible with almost all modded tools (such as those from Tinkers' Construct or Immersive Engineering) and modded blocks.
- Performance: The mod is highly optimized. Tracking 30 blocks requires negligible RAM and CPU cycles, making it suitable for even low-end hardware.
Gallery#
