Tags
Creators
Details
1.2.0
Compatibility
Changes
ExcaMate Config & Settings Update:
ExcaMate now has an in-game settings screen, so players no longer need to edit config/excamate.json manually for common options.
In-Game Settings
Players can configure ExcaMate through Mod Menu using the Configure button.
The settings screen includes:
General
Auto-pickup drops
Direct XP collection
Auto torch placement in Branch mode
Default mining mode
Block Limits
Vein max blocks
Branch max blocks
Excavate max blocks
Block Lists
Extra vein mine allowlist
Vein mine blocklist
Auto-pickup blocklist
Block lists use a searchable block selector, so players can search for blocks like obsidian, hay block, or gravel instead of typing block IDs manually.
Default Block Limits
{
"veinMaxBlocks": 12,
"branchMaxBlocks": 16,
"excaMateMaxBlocks": 27
}
Vein: up to 12 total blocks
Branch: up to 16 total blocks
Excavate: up to 27 total blocks, allowing a full 3x3x3 excavation
The first block mined counts toward the limit.
How It Works
extraVeinMineAllowList adds extra blocks that ExcaMate can mass-mine on top of its normal supported blocks.
ExcaMate’s default supported blocks include ores, logs, stone-type blocks, and shovel blocks.
veinMineBlockList prevents specific blocks from being mass-mined.
When autoPickup is enabled, ExcaMate attempts to auto-pick up drops from every block it successfully mines.
autoPickupBlockList prevents drops from specific source blocks from being auto-picked up.
An empty extraVeinMineAllowList keeps ExcaMate’s normal default mining behaviour.
Blocklists always override extra allowlists and default behaviour.
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:5gdROB0x"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HtZJrAVB:5gdROB0x"
}

