All versions
1.2.0
Release
Advanced TreeCapitator 1.2.08 months ago 20
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Changelog — Advanced TreeCapitator
All notable changes to this project will be documented in this file.
[1.2.0] — 2025-03-10
Added
- Per-player toggle (
/atc toggle) — each player can enable or disable tree felling independently without affecting others - Tab completion for the
/atccommand README.mdwith full installation guide, permissions table, and usage notesCHANGELOG.md(this file)
Fixed
@EventHandlerwas missingignoreCancelled = trueandpriority = EventPriority.HIGH— now correctly respects cancellation from other plugins- Leaf detection upgraded to 26-direction (3×3×3) scan when
break-leaves: true— diagonal leaves on Dark Oak and Jungle trees are now always caught - When a tree exceeded
max-blocks,breakCountwas reset to1but damage was still calculated — now the task returns early with no extra block breaks or damage when the limit is hit - Tool durability now uses
extraBreaks + 1(including the origin block) for an accurate damage total
Changed
- In-game messages translated to English for Modrinth release
- Logger startup message now includes the plugin version
onDisable()clears bothcooldownsanddisabledPlayers- Config comments rewritten in English with explicit Fortune/Silk Touch notes
maven-compiler-pluginbumped to3.13.0- Version:
1.1.0→1.2.0
[1.1.0]
Fixed (internal, per [FIX #x] comments)
[FIX #1]enabledflag is now checked at the top of the event handler[FIX #2]/atc reloadcommand handler registered correctly[FIX #3]Permission checkadvancedtreecapitator.useapplied[FIX #4]break-leavesnow actually breaks leaves[FIX #5]Particle effect now renders correctly[FIX #6]Periodic cooldown map cleanup to prevent memory leak[FIX #8]Cooldown is configurable viacooldown-msinstead of being hardcoded[FIX #9]Unbreaking enchantment respected; Pale Oak, Nether stems, and Bamboo added to default config
[1.0.0]
- Initial release
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:8li9wnIm:91WQRdLp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8li9wnIm:91WQRdLp"
}

