Tags
Creators
Details
Licensed Apache-2.0
Published 2 years ago
Updated 2 days ago
All versions
2.3.1+fabric-1.20.1
Release
2.3.1 · fabric · 1.20.13 weeks ago 30
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Unavailable version
Changes
Fine Tuned Weaponry 2.3.1
Fixed
- Weapons Anvil accepts supported weapons and tools through direct insertion and shift-click on Minecraft 1.21.1 Fabric and NeoForge, with matching eligibility on supported 1.20.1 Fabric and Forge workspaces.
- Restored Minecraft 1.21.1 gem and amplifier tags so upgrade slots accept the intended items.
- Fixed Minecraft 1.21.1 socket occupancy and removal: occupied sockets no longer consume replacement upgrades, and installed gems/amplifiers can be returned. Historical
.0socket keys remain supported. - Release downloads declare Jauml as a required dependency on both platforms, matching the existing mod metadata. Dependency versions are unchanged.
Compatibility and verification
- Weapon eligibility uses the data-pack-extensible
fine_tuned_weaponry:anvil_toolstag, with supported common conventions and optional legacy Forge tags. - Native/headless tests cover insertion, shift-click, socket application/removal, legacy data, custom names, damage, foreign NBT and bound-anvil container serialization/reopening. All supported workspace/loader builds pass.
- Real in-game clients, networking, chunk/region saving and enchantment preservation have not been verified in this release's test session.
Fine Tuned Weaponry 2.3.0
Added
- Research table recipes for base gems: Inferno Core, Frost Rune, and Storm Shard
- Right-click abilities for Earthly, Obsidian, and Rose Gold hammers
- Hollow Man staff Haste ability on right-click
- Jauml config keys for hammer and staff ability tuning
Fixed
- Weapon tooltips now match implemented abilities
- Renamed
charger_amp_reicpe.jsontocharger_amp_recipe.json - Removed orphaned Kurasai Katana lang keys
- Fixed "Weapons Tempate" typo in research table tooltips
Changed
- Project licensed under Apache-2.0 with standard OSS contributor docs
- CI build workflow targets the active
26.2/workspace
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:ENwBoUVH:H02GmlxD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ENwBoUVH:H02GmlxD"
}

