Tags
Creators
Details
1.2.0
Compatibility
Changes
Release 1.2.0 – Bedrock Breaker Support, Command Whitelist
New Features
- New machine type: Bedrock Breaker (
/bedrockbreaker), with the full command set already available for world eaters and trenchers (create,start,stop,list,delete,settings,discordPings) - Bedrock breaker detection reuses the same explosion-based block-break detection as trenchers (counts blocks actually destroyed, ignores TNT blocks)
- Bedrock breakers default to
minBlocksBroken = 1(vs. 3 for trenchers), fully adjustable via/bedrockbreaker settings setMinBlocksBroken <count> - Command whitelist: op players can always use every command; non-op players can only use
/worldeater,/trencher, and/bedrockbreakerif their name is on the whitelist - Whitelist is shared across all three commands and stored in the same config file
- Only op players can add or remove names from the whitelist (
settings whitelist add|remove <player>); anyone permitted to use the commands can view it (settings whitelist list)
Upgrading from 1.1.0
- Replace the old JAR with the new one.
- Your existing config is untouched. The whitelist starts empty, so only op players can use the commands until you add someone.
- To let non-op players use the commands, run
/worldeater settings whitelist add <player>(or the equivalent/trencher//bedrockbreakercommand — they all share the same whitelist). - Create your first bedrock breaker the same way you'd create a trencher:
/bedrockbreaker create <name> <x1> <y1> <z1> <x2> <y2> <z2>.
Installation
Download the JAR from the assets below, place it in your server's mods folder, and start the server. See the README for full usage details.
Full Changelog: https://github.com/CodeW4VE/WorldEaterNotifier/compare/1.1.0...1.2.0
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:JsGimWih:Lrr18pRN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JsGimWih:Lrr18pRN"
}

