Tags
Creators
Details
2.0.0
Compatibility
Required content
Changes
Fixed
- Fixed a bug where
F3 + Thad to be pressed twice to take effect.
Added
-
Added support for more game and loader versions:
Loader Game Versions Fabric 1.20.4 NeoForge 26.1.x, 1.21.11, 1.21.5, 1.21.1 Forge 1.20.1 -
Added an automatic recognition mechanism and more preset categories, extending built-in support to cover most common, standardly named modded weapons and tools.
*Non-standard ones can still be configured manually via the mapping feature.
-
Added a Mapping Management feature allowing you to reassign any item's category or create custom categories (with optional material variants) to apply different sounds. Press
V(rebindable) in-world to open the GUI. -
Added the
clangor_config.jsonfile for batch editing mappings and settings.*Using the in-game GUI is highly recommended.
-
Added support for including your mapping configurations upon export in the Resource Pack Exporter.
-
Added compatibility for Better Combat. Dual-wielded weapons now play their respective sounds properly.
*Better Combat's default swing sounds will overlap with this mod. Toggle them in either config screen as you prefer.
-
Added a Pitch Variation configuration option to provide a more dynamic and rich sound experience.
-
Added quick-access buttons in the config screen to instantly open the
soundsfolder, its five core subfolders, and the configuration file for easier management. -
Added a cleanup feature to instantly delete empty category folders no longer referenced by any mappings.
-
Added a Discord server invite link for bug reports, feedback, and sharing sound packs.
Improved
- Changed all toggle buttons in the config screen from tick-boxes to green ✔ / red ✘ indicators.
- Updated
zh_cn.jsonanden_us.jsonlocalization. - Updated the mod icon.
Changed
- Players upgrading from
1.0must move their audio files fromselect/spear/<material/general>/directly intoselect/spear/for them to play properly. This is becauseselect/spearno longer features material variants by default in version2.0. The old material andgeneralfolders can then be safely deleted.
Optional dependencies
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:nkRO5AVS:d9A31ZnO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nkRO5AVS:d9A31ZnO"
}

