Links
Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated 3 months ago
All versions
1.1.0
Release
ThreeChopper 1.1.03 months ago 7
Compatibility
Minecraft: Java Edition
26.2
Platform
Paper
Changes
ThreeChopper Changelog
1.1.0 - Feature and Reliability Update
Added
- Toggle sounds for enabling and disabling ThreeChopper.
- Optional WorldGuard build protection support.
- Console startup ASCII banner and live configuration reload diff logging.
- Mangrove root scanning and chopping support.
- Detailed administrator inspect diagnostics, including tree type, detection result, leaf metrics, trunk-top canopy connection, horizontal line length and structure score.
Improved
- All runtime permission checks now use the
threechopper.*namespace. - Natural-tree detection now validates vertical trunk height and natural canopy connection near the trunk top, reducing false positives on player-built structures.
- Trees are chopped from the lowest connected block upward.
- Durability now defaults to one point per successfully broken log, while retaining vanilla-style Unbreaking handling.
- Natural leaves are broken through vanilla loot tables, restoring normal sapling, apple and stick drops.
- Giant mushroom caps are included in the connected chop scan; Silk Touch tools return the cap blocks as items.
- Holograms appear above the felled tree and use a reliable marker ArmorStand implementation.
config.ymlnow contains operational comments and safer explanations for the main settings.
Changed
- ActionBar+ and hologram feedback are disabled by default for each new player, but can be enabled from the settings GUI.
- ActionBar completion feedback no longer reports detected leaf counts.
- ActionBar+ no longer includes the warning symbol.
- All player-facing and administrator-facing UI text, diagnostic reasons and tree names are served from
lang_en.ymlandlang_hu.yml.
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:aXpjQG8h:WaJljYl1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aXpjQG8h:WaJljYl1"
}

