Tags
Creators
Details
2.1.3-26.2-hotfix
Compatibility
Required content
Changes
geez i never thought this would need a hotfix but was i wrong
hello my fellow idiots once again who use dedicated servers
lets just get to the point
hotfix
fixed:
- moved client command registration out of common entrypoint so dedicated servers don't crash trying to load client classes
- wrapped reader in try-with-resources in static log loader to fix stream leaks
- fixed song commands calling play twice on the same input stream causing audio to immediately stop
added:
- added missing song command registration in client initializer
- added empty check when fetching random log messages to avoid crashes on launch if logs are missing
credits: it wouldnt have been fixed if it wasnt for Spagles on github to use it on a dedicated server (why tho? i get it if its only you on it but if theres other players... please stay off my issues page if someone uses a tnt stick to carpet bomb your house)
Optional dependencies
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:luTYqvyT:1WHlf34d"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:luTYqvyT:1WHlf34d"
}

