Tags
Creators
Details
v2.1.0
Compatibility
Required content
Changes
📦 Mixer v2.1.0 Changelog
🎵 New Feature: Portable Speakers
Take your music on the go! The Portable Speaker allows you to play custom discs directly from your inventory, with the sound following your character.
- New Item:
Portable Speaker(obtainable via/mixer speaker). - Easy Control: Right-click the speaker to open a user-friendly GUI.
- Insert a custom disc.
- Use Play (Green) to start playback.
- Use Stop (Red) to stop playback.
- Smart Interaction:
- Music automatically stops if you drop the active speaker item.
- Music stops if you disconnect or die.
- Visual note particles appear above your head while music is playing.
- Configuration:
- Enable/disable the feature in
config.yml. - Customize the speaker item material (default:
NOTE_BLOCK). - Full localization support in
en.ymlanduk.yml.
- Enable/disable the feature in
🛠️ Technical Improvements
- Audio Engine Refactor: The core audio logic has been split into an abstract layer, making the codebase cleaner and easier to maintain.
- Config Auto-Update: The
config.ymlfile now automatically updates with new settings while preserving your existing configuration and comments. - Bug Fixes:
- Fixed an issue where
LocationalAudioChannelwas incorrectly used for portable players (now usesEntityAudioChannel). - Fixed an issue where the GUI would throw errors if the item in hand was swapped while the menu was open.
- Added proper validation for item NBT data to prevent errors with invalid discs.
- Fixed an issue where
📜 Commands
/mixer speaker- Gives the player a Portable Speaker item.
If you have any suggestions or found a bug, please create an issue on GitHub: https://github.com/Andromedov/Mixer/issues
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:94MyQ3m6:HgP4qwWc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:94MyQ3m6:HgP4qwWc"
}

