Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated last month
All versions
1.1.3
Release
Who Stopped The Music 1.1.3last month 559
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Changes
Who Stopped The Music 1.1.3
Official Minecraft 26.2 Fabric release for the new music controller.
What it does
- Removes long vanilla silence gaps between music tracks.
- Prevents songs from being cut short mid-track.
- Shows a compact top-of-screen Now Playing toast with readable official song names.
- Adds a pause-menu cassette with current-song display, Previous, Next, and click-to-open settings.
- Adds Music Settings with search, selected-song checkboxes, Play/Stop, Previous/Next, Shuffle, Select All, Deselect All, and vertical Music Volume control.
- Keeps Controls off by default so vanilla still chooses music normally unless the player turns the controller on.
Deterministic shuffle
- Shuffle now builds a predetermined cycle from selected songs when it turns on.
- Next and Previous move through that cycle instead of rolling a fresh random song.
- Songs do not repeat until every selected song in the current cycle has played.
- After the cycle is exhausted, the mod reshuffles the selected songs and starts the next cycle.
Docs and metadata
- README now explains the actual current behavior.
- Added
docs/HOW_IT_WORKS.mdwith exact rules for Controls, deterministic shuffle, Stop/silence behavior, persistence, and UI surfaces. - Updated Fabric metadata description for launchers and mod platforms.
Compatibility
- Minecraft 26.2
- Fabric Loader 0.19.3+
- Java 21+
- Client-side only, no server install required.
Verification
git diff --check./gradlew clean build --no-daemon --stacktrace- Inspected
build/libs/whostoppedthemusic-1.1.3.jarmetadata for version1.1.3and updated description.
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:VL8PQQj1:MEQVMOQ0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VL8PQQj1:MEQVMOQ0"
}

