Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 2 days ago
All versions
How It Works
1.1.0
Release
ExcaMate 1.1.03 months ago 13
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client and server
Changes
Added
- Added configurable extra block allowlists and blocklists for ExcaMate mining.
- Added configurable extra block allowlists and blocklists for auto-pickup.
- Added support for user-defined block IDs, such as:
minecraft:hay_blockminecraft:oak_leavesminecraft:obsidianminecraft:sand
New Config Options (Example)
{
"extraVeinMineAllowList": [
"minecraft:obsidian"
],
"veinMineBlockList": [
"minecraft:glass",
"minecraft:glass_pane"
],
"extraAutoPickupAllowList": [
"minecraft:obsidian"
],
"autoPickupBlockList": [
"minecraft:gravel"
]
}
How It Works
- extraVeinMineAllowList adds extra blocks that ExcaMate can mass-mine on top of its normal supported blocks.
- ExcaMate’s default supported blocks still work as normal, including ores, logs, stone-type blocks, and shovel blocks.
- veinMineBlockList prevents specific blocks from being mass-mined.
- extraAutoPickupAllowList adds extra blocks whose drops can be auto-picked up on top of normal ExcaMate behaviour.
- ExcaMate’s normal auto-pickup still works for its default supported blocks when auto-pickup is enabled.
- autoPickupBlockList prevents drops from specific blocks from being auto-picked up.
- Empty extra allowlists keep ExcaMate’s normal default behaviour.
- Blocklists always override extra allowlists.
Safety and Balance
- Allowlisting a block does not bypass tool rules.
- Players must still use the correct tool for the block.
- Vanilla harvest rules, Silk Touch, Fortune, XP, durability, and drops are preserved.
- Protected blocks and container/block-entity blocks remain blocked for safety.
Applies To
- These rules apply across all ExcaMate modes.
Technical
- Invalid block IDs no longer crash the game.
- Invalid or unknown block IDs are logged as warnings.
- Configured block IDs are cached after loading for better performance.
- Existing behaviour remains unchanged when the new lists are empty.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:HtZJrAVB:gs62LOlx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HtZJrAVB:gs62LOlx"
}

