Tags
Creators
Details
Licensed ARR
Published last year
Updated 2 months ago
All versions
1.0.9
Release
TreeCapitator999 1.0.9 The Rollback Update!2 months ago 422
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
New Features
- Felling direction control with visual particle effects showing fall direction based on player look direction
- Tool enchantment integration supporting Fortune (increased drops), Silk Touch (logs only), Unbreaking (reduced durability loss), and Efficiency (faster cascading)
- Undo/rollback command (/treecapitation undo) to restore the last felled tree within 5 minutes
Bug Fixes
- Fixed cooldown calculation displaying incorrect remaining time due to integer division truncation
- Fixed tool breaking not properly clearing the player's main hand slot
- Fixed WorldGuard integration using deprecated API method
- Fixed cascading break potential null pointer when block state changes between scheduling and execution
- Added particle effects and sounds for leaf breaking in cascading mode
- Fixed auto-replant using original log location instead of bottom-most trunk block
- Fixed particle data creation failing for non-block materials
- Fixed break sound playing at player location instead of block location
- Fixed custom drops using incorrect origin location in cascading mode
- Fixed fake vertical log detection incorrectly blocking standalone logs and small trees
- Fixed smart tree recognition grounded check using wrong X/Z coordinates for multi-trunk trees
- Fixed tool list parsing silently ignoring invalid materials without warnings
- Fixed protection hook memory leak on config reload
- Fixed player settings and cooldown bypasses not clearing on config reload
- Fixed fortune enchantment not being applied to tree drops
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:9byUrBEE:Uk1I0OtT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9byUrBEE:Uk1I0OtT"
}

