Tags
Creators
Details
0.3.2
Compatibility
Changes
Jumped Version 0.3.1 due to number of fixes.
-
Chat Security: Resolved "Scunthorpe Problem" by implementing safe-word lists and context-aware de-spacing analysis.
-
Networking & Auth: Eliminated ghost links and auth loops via granular unlinking and proactive backend vouching.
-
Session Security: Enforced strict 24-hour session expiry and standardized all network logic to Unix timestamps.
-
Admin Tools: Launched the Panopticon dashboard for unified investigations, inventory renders, and activity sparklines.
-
Technical Health: Migrated build system to Maven, upgraded to Java 25, and implemented library shading/relocation for Java 21.
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:kyiSeeUV:CaUybjMv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kyiSeeUV:CaUybjMv"
}

