Links
Tags
Creators
Details
1.2
Compatibility
Changes
This patch is dedicated to reinforcing system stability
- Fixed critical bugs, including channel split issues that caused session desynchronization among users.
- Resolved console errors and warnings that resulted in client-side freezes and unexpected terminations.
- Cleaned up redundant logs and suppressed non-critical console noise to improve performance.
Important: Should you discover any new regressions, replicable glitches, please report them immediately via our issue tracker (or tech-support chat). Be sure to provide clear steps to reproduce — your detailed feedback is essential for the final stabilization of this release.
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:SXMLVhRH:JxWzMolH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SXMLVhRH:JxWzMolH"
}

