Tags
Creators
Details
Licensed CC-BY-NC-SA-4.0
Published 4 months ago
Updated last month
All versions
1.1.0
Release
(MDR) Music Delay Reducer 1.1.03 months ago 24
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Changes
New Features:
- Custom track support: play your own music files (WAV, MP3, OGG, FLAC) alongside or instead of vanilla music.
- Three playback modes: Vanilla only, Custom only, or Both mixed together.
- Automatic volume normalization for custom tracks, so quiet and loud files sound consistent.
- Smooth crossfade between tracks - toggleable, with adjustable duration (0.1–3 sec).
- Startup fade-in - music stays silent for a moment after launching the game, then fades in smoothly. Toggleable, with adjustable delay (1-5 sec).
- Music restarts fresh when joining a world instead of continuing whatever was already playing (toggleable).
- Three track order modes for custom tracks: In Order, Random (No Repeat), and fully Random.
- Volume Up/Down keybinds (default: Up/Down arrows) to adjust music volume in 5% steps, with acceleration on hold.
- "Now Playing" toast for custom tracks, matching vanilla's own now-playing notification.
- Tooltips added to every setting in Mod Menu, explaining what each option does.
- Scrollable settings screen with mouse wheel support, adapting to window size.
Improvements:
- Replaced the file picker with a native dialog for better cross-platform reliability.
- Fixed a rare audio hitch when preloading tracks was interrupted by playback.
- Switched to the public Fabric key mapping API for better long-term compatibility.
Known Issues:
- Switching your system's audio output device while playing vanilla music can cause an unwanted track skip. A proper fix (seamless device switching) is planned for a future update.
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:mdwsolmY:mzApNL0y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mdwsolmY:mzApNL0y"
}

