Tags
Creators
Details
1.2.1
Compatibility
Changes
π Changelog v1.2.1
π Bug Fixes
-
Folia Threading Fix - Fixed
IllegalStateException: Thread failed main thread checkin WorldCleanerModule on Folia servers- Entity state (like
getCustomName()) is now accessed from the correct region thread - Entity processing is dispatched to each chunk's region thread on Folia
- Entity state (like
-
Modrinth Publishing - Fixed version format to comply with Modrinth's semver regex validation
- Changed from
1.x.x [build x]to1.x.x+xformat
- Changed from
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:dYG5aOQk:nKCnYk9s"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dYG5aOQk:nKCnYk9s"
}

