Tags
Creators
Details
v2.2.2
Compatibility
Required content
Changes
📦 Mixer v2.2.2 Changelog
✨ New Features
- bStats Metrics: Added support for anonymous statistics collection via bStats. This can be toggled via the
metrics: trueparameter in theconfig.ymlfile.
⚡ Improvements & Optimization
- Cobalt API Integration: Significantly improved Cobalt URL handling. Updated requests to use API v7 with an automatic fallback to v6, ensuring more stable media loading.
- Async Handling: Refactored asynchronous processes, improved thread management and overall server & music stability (will be most noticeable when there are 3+ players on the server playing music).
- Code & Dependencies Cleanup: Optimized dependencies (switched the
:apidependency toimplementation) and removed redundantStandardCharsetsconversions in the TTS URL generator.
🐞 Bug Fixes
- Cobalt Error Messages: Fixed and simplified Cobalt API error messages in-game. If an HTTP 403 error occurs, the plugin now directly warns the user about potential hosting blocks by Cloudflare.
- Data Access Safety: Fixed potential NullPointerExceptions in
RedstoneListenerandPlayerInteractListenerwhen interacting with discs. Added proper safety checks forItemMetaandPersistentDataContainerkeys. - Playback Stability: Improved track completion handling and queue loading. Fixed the state management of the
playbackStartedvariable, preventing playback hangs when processing playlists.
Note: I tried to add an easier YouTube support, but it didn't work out the way I'd planned, so I kinda scrapped all of the progress and might start over from scratch (or maybe I will just ignore that feature entirely)
Full Changelog: https://github.com/Andromedov/Mixer/compare/v2.2.1...v2.2.2
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:XwsCahfD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:94MyQ3m6:XwsCahfD"
}

