Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated last month
All versions
1.0.1+1.21.11+neoforge
Release
SoundtrackPlayer 1.0.1+1.21.11+neoforgelast month 9
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client-side
Client and server
Changes
- Ported to Fabric 26.2 and NeoForge 1.20.1, 1.20.4, 1.21.1, 1.21.4, 1.21.5, 1.21.8, 1.21.11 and 26.2
- 1.20.x builds run on Java 17 again
/soundtrack play <id> resource <sound>and/soundtrack play <id> url <link>, no quotes needed and resource autocompletes the resource pack sounds- Soundtracks folder:
.oggfiles inassets/<namespace>/soundtracks/of a resource pack work without a sounds.json and show up in tab completion after F3+T - Any link works: plain ogg/mp3/wav files, pages like YouTube or SoundCloud and other media like mp4 or m4a. The tools they need download by themselves the first time
- Playing the same id and sound again changes volume, pitch or fades live without restarting the song
- Local soundtracks keep playing (on the right second) after leaving and joining a world
- The mod only talks in chat when something goes wrong
- Late joiners, rejoins and resource reloads start the song at the same second as everyone else
- F3+T and the pause menu no longer stop soundtracks
stophas an optional fade out that overrides the track's own onefadeloopoption: fade every lap of a loop in and outcategoryoption: play in any vanilla sound category, default is the new SOUNDTRACKS one- "Soundtracks" volume slider in Music & Sounds, translated to 20 languages
/soundtrack listand/soundtrack stop all- Tracks in a category at 0% come back when the slider goes up again
- Tracks from one server no longer keep playing on the next one
- Server side API and client side API
- Forge jars now ship a mixin refmap so they work outside the dev environment
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:h0JupWmV:ylP227i4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:h0JupWmV:ylP227i4"
}

