
Fletcher's Trestle - Archery Mod
Fletcher’s Trestle overhauls Minecraft’s archery by replacing the basic crafting table bow with a modular system. From the raw log to the perfect release, every step of the process is in your hands. Modular bows, crossbows, arrows, in the palm of your hand
Tags
Creators
Details
1.0.0
Compatibility
Changes
Stop "crafting" bows like they’re just wooden pickaxes. Fletcher’s Trestle turns bow-making into a true artisan craft. From the first shave of a log to the final high-tension stringing, your skill determines your power.
🪚 The Artisan's Workflow
Forget the 3x3 grid. This is how a real Bowyer works:
The Shaving Horse: Bolt a raw log onto this workstation and use a Drawknife to carve out the rough shape of your limbs. You’ll see the wood change right in front of you.
The Steam Box: Hardwood doesn't bend easily. Place your limbs over a campfire in the Steam Box to make them pliable. Keep an eye on the water level—steam is the secret to a snap-free draw!
The Assembly: Combine your limbs with a custom Riser (Wood, Copper, or Iron) and a String of your choice.
🎯 66 Ways to Shoot an Arrow
Why settle for one bow when you can have 66?
Modular Limbs: Every wood type matters. Spruce, Dark Oak, Mangrove, and even the twisted woods of the Nether (Crimson/Warped) offer different properties.
Material Tiers: Match your playstyle with Copper or Iron risers and reinforced High-Tension strings.
⚡ The "Sweet Spot" Minigame
Your bow is only as good as its tuning. When you assemble your weapon, you’ll face a high-stakes timing game.
Hit the Notch: Nail the randomized "Sweet Spot" to maximize your bow’s quality.
"Because a weapon you carved with your own hands just hits differently."
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:ltJyhH1n:hYbXgkvN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ltJyhH1n:hYbXgkvN"
}
