Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 3 weeks ago
All versions
1.0.4
Release
TreeCapitator 1.0.43 weeks ago 182
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.5
Platforms
Paper
Purpur
Spigot
Changes
Bug Fixes
- Fixed event multipliers being applied more than once, which could cause XP rewards to be higher than intended.
- Fixed event boosts not being removed when an event was stopped and potentially remaining active long after an event ended.
- Fixed event effects depending on the event's name, which prevented some events from applying their intended XP or drop bonuses.
- Fixed players joining during an active event not consistently receiving its effects.
- Fixed oversized trees being partially cut instead of rejected, and improved detection of logs below the block that was broken.
- Fixed automatic data saves running asynchronously while player data could be changing, risking inconsistent saves or concurrent access errors.
- Fixed tree cutting bypassing block-break protection checks from other plugins.
- Fixed tree-cutting tools not losing durability as expected; tool damage now respects durability-related events and the Unbreaking enchantment.
- Fixed configuration reloads not reloading event settings.
PlaceholderAPI Improvements
- Consolidated PlaceholderAPI values into three generic formats for player data, boosts, and events, reducing duplication while keeping all supported values available.
- Added boost status and event-specific XP and drops multipliers.
- Kept the existing player-stat placeholders working for backward compatibility.
- Documented the placeholder formats and examples in the project documentation.
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:IYEAALvT:cVpuqSBn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IYEAALvT:cVpuqSBn"
}

