Tags
Creators
Details
1.2.0
Compatibility
Required content
Changes
Iustitia v1.2.0 — Modern Checks, Global PlayClip, Presets and Config Saving.
A read-only, client-sided moderator toolkit layered on top of the detection core.
What's new
🧾 Presets — /ius preset [debug|moderation|lenient|standart|strict|(custom)] /ius createpreset [name]
You can now save your presets and scroll through which one to use. I've added 5 different in-built presets that should work well for general use. If the user wants to create their own preset, they can just do /ius createpreset. This was requested by multiple people, so there it is. You can still find first launch setups by doing /ius wizard .
📦 Modern Clips: Freecam & Map Sync — /ius clip, /ius playclip, /ius clips /ius delclip
I've updated clips into downloading the maps and putting the user into freecam whenever the user runs /ius playclip . To access this feature, go to /ius config and change the clip's config into Modern from the standart legacy. You can now delete clips without going into iustitia folder by doing /ius delclip [clipname].
🚫 5 Different New Checks. — /ius config,
5 Different 1.21.11 Checks added, that improves support to modern versions too. Iustitia can now be called a proper Hybrid Anti-Cheat; Which both goes in depth with 1.8.9 and 1.21.11 checks.
Other
- Docs + website refreshed to v1.2.0 and their location changed to https://thoria.fyi/iustitia .
Install
Drop iustitia-1.2.0.jar into your mods/ folder alongside Fabric API, fabric-language-kotlin, and YACL. Requires Minecraft 1.21.11 + Fabric Loader 0.19.3+. Install ViaFabricPlus to also detect on 1.8-era servers.
Full changelog: https://github.com/ThoriaDevelopment/Iustitia/commits/main
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:W3HOLfeH:bupJUUDV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:W3HOLfeH:bupJUUDV"
}



