Tags
Creators
Details
Licensed GPL-3.0-or-later
Published last year
Updated 4 days ago
All versions
2.7.8+1.21.1
Release
True Adaptive Music 2.7.8 for Minecraft Neoforge 1.21.14 days ago 80
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
True Adaptive Music v2.7.0 - Very Forgey Indeed!
Important Notice!
2.7.0 marks a return to CurseForge. To remain compliant with CurseForge policy, certain functionality has been removed from the CurseForge version of TAM.
This functionality includes FFmpeg (ability to use non-ogg sound files) and the Pack Browser.
New Features:
NeoForge/Forge Support!!!
- TAM now officially supports NeoForge for MC 1.21.1-26.* and up. Forge is supported for 1.20.1.
- If you want support for forge/neoforge to be extended to the other versions, please let me know!
TAM API Embedded
- The True Adaptive Music API is now embedded into the base mod, so no need to download both anymore!
Mega Link Support
- Mega links are now supported for Pack Browser upload!
Node Option: Music Weights
- You can now specify how often certain music within a node should play relative to other music.
- Toggle on "Music Weights" in the node parameter list to use it.
Node Option: Disable Resuming
- Toggle on "Disable Resuming" in the node parameter list to disable resuming when re-entering that node.
Combat/Entity Nearby Mob Count Option
- You can now set a minimum number of mobs to trigger music for the Combat/Entity Nearby predicate types.
Fixes
- Fixed guardians/elder guardians not working for the Combat predicate type on 26.1 and up.
- Unsupported OSs will fall back to non-ffmpeg.
Please also reach out if you would like support to be added for a new language. I am still working on finishing Russian support :)
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:UeDAoEyD:vdKAu9DP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UeDAoEyD:vdKAu9DP"
}

