Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 3 years ago
All versions
1.6.2
Release
Mixtape 1.6.2 for Minecraft 1.20.3-1.20.43 years ago 1,769
Compatibility
Minecraft: Java Edition
1.20.3–1.20.4
Platforms
Fabric
Quilt
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
- There is now an update badge that will let you know when there is a mixtape update available, and it can be turned off in the settings.
- You can now show the current playing song in either the pause or options screen.
- Music toasts now disappear after their song has finished.
- Music toasts now show one after another, rather than 5 at a time.
- Jukeboxes now stop playing when you return to them if someone stopped them while they were outside your render distance.
- Mixtape is now enabled by default.
- Decreased the range of the mono distance slider for jukeboxes.
- Fixed interacting with jukeboxes crashing the game.
- Fixed jukeboxes not playing at all when mixtape was disabled.
- Fixed noteblocks playing their audio from 0, 0, 0 if mono was enabled for jukeboxes.
- Fixed jukebox volume slider not affecting the volume of jukeboxes.
- Fixed music turning up to max volume when any volume sliders were changed even if it was being turned down by jukeboxes.
- Fixed enabled toggles in music type settings not actually turning off that music type.
- Fixed new minecraft music (1.13+) from playing at a louder volume than old minecraft music when using mixtape resourcepacks.
- Fixed mod features still functioning when mixtape was disabled.
- Fixed mod icon not showing up properly in modmenu.
Optional dependencies
Any compatible version
Known incompatibilities
Any version
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:mTd6rTN3:8PcqY5Jz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mTd6rTN3:8PcqY5Jz"
}

