Tags
Creators
Details
1.0.0
Compatibility
Changes
Changelog
All notable changes to AMCTimber. This project adheres to Semantic Versioning and the Keep a Changelog format.
1.0.0 — 2026-06-19
First public release — extracted and generalised from the internal asketmc build.
Added
- Valheim-style tree felling: cut a tree's base and the section above topples in a smooth, client-interpolated fall, leaving a stump; the downed trunk must be re-chopped for its logs.
- Tool-tier scaling — each axe tier (wooden → netherite) caps the tree size it can fell; configurable.
- Configurable axe items —
axes.use-vanilla-tag+axes.extra-itemsdecide what counts as an axe. - Pluggable skill-XP bridge — award XP to any skill plugin via a configurable console command
(
%player%/%skill%/%amount%), no dependency. Examples for AuraSkills & mcMMO included. - Configurable durability cost per fell and per chop.
- Crush damage — a landing tree flattens whatever stands in its path (size-scaled, capped, PvP-safe).
- Treehouse / log-cabin guard and species-aware spreading (no cross-wood-type felling).
- Debug levels —
off/info/full. - Externalised messages —
messages.ymlin EN + RU, MiniMessage-formatted, per-client locale. - Folia support — uses Paper's region/global/entity scheduler API directly (no external lib).
- Wide compatibility — one jar for Paper/Purpur/Pufferfish/Folia, MC 1.20.6 → 1.21.x (version-specific particles/sounds resolved at runtime).
- bStats metrics (opt-in; set the plugin id to enable).
- Self-check —
/amctimber selftest(74 assertions over the pure logic). - Unit test suite — JUnit 5 (
src/test/java), 29 server-free tests run by CI viamvn test.
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:ri1Ibgnf:q637itJU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ri1Ibgnf:q637itJU"
}

