1.1.0
Compatibility
Changes
πͺ WoodCutter - The Ultimate Vanilla+ Stonecutter for Wood!
Tired of wasting precious wood blocks just to craft a few trapdoors or stairs? WoodCutter brings the efficiency of the Stonecutter to the lumber world!
This is a lightweight, performance-friendly, and pure Vanilla+ plugin that seamlessly injects custom recipes into the native Minecraft Stonecutter. No custom resource packs required, no commands, and absolutely zero lag!
π Features (v2.0.0 - The Builder Update)
- π 100% Native Integration: Works directly inside the vanilla Stonecutter block. No confusing custom inventory screens or desync glitches.
- π³ Every Wood Type Supported: Fully compatible with all overworld woods, including Cherry and Bamboo!
- π₯ Nether Woods Included: Bring your Crimson and Warped planks to the cutter!
- π Perfect for Builders: Craft everything you need with a 1:1 ratio!
- Stairs & Slabs (Returns 2 slabs per plank!)
- Trapdoors & Doors (No more wasting 6 planks for 2 trapdoors!)
- Fences & Fence Gates
- Buttons & Bamboo Mosaics
- β‘ Highly Optimized: Built using Spigot/Paper native recipes API. It consumes 0ms of server tick time.
π οΈ How it works
- Place a standard Stonecutter down.
- Put any type of Wood Planks in the input slot.
- Select your desired wooden piece (Stairs, Trapdoor, Slab, etc.) and cut it instantly!
π Compatibility & Installation
- Drop and Play: Just drop the
WoodCutter.jarinto your server'spluginsfolder and restart! - Supported Loaders: Paper, Spigot, Purpur.
- Smart Version Control: Safe to use across multiple Minecraft versions. If a wood type doesn't exist in your older server version, the plugin skips it automatically without throwing errors!
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:9rx6zuis:KYMHOihI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9rx6zuis:KYMHOihI"
}

