Links
Tags
Creators
Details
Licensed MIT
Published 11 months ago
Updated last month
All versions
1.2.1
Release
LegacyTrack v1.2.1-1.21.811 months ago 127
Compatibility
Minecraft: Java Edition
1.21.8
Platforms
Fabric
Resource Pack
Supported environments
Client-side
Changes
Features
- Compatible with Minecraft Java 1.21.8
- Rebalanced nether music to play all tracks equally in all biomes (including the warped forest).
- Introduced a creative resource pack to only play the exclusive creative tracks when the player is in creative mode. The resource pack will have to be loaded on top of the base resource pack.
Changes
- The underwater sound event has been modified to only play the creative music when the player is in creative mode underwater.
- All biome sound events now reference music.game instead of adding the same C418 music under the sounds list.
Installation
- Download the two .zip files under the files section.
- Move those two .zip files to the minecraft resourcepack folder.
- In the game, load LegacyTrack and when in creative mode, load LegacyTrackC on top of LegacyTrack; when switching gamemode from creative, unload LegacyTrackC.
Design Decisions & Tradeoffs
- The nether music has been adjusted so that the biome exclusive tracks are no longer exclusive. This was done to allow certain biomes to have access to tracks that they otherwise wouldn't.
- The warped forest will now play all the nether sound tracks, this can introduce preference issues since the warped forest does not play any music at all.
- A tradeoff with the creative resource pack involves players having to manually load/unload the resource pack when they switch game modes for the most optimal experience.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| LegacyTrackC.zip | Unknown | 32.61 KiB |
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:6Ptdj5WF:ZqQZ8k7Q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6Ptdj5WF:ZqQZ8k7Q"
}

