1.6.2
Compatibility
Changes
SocialCredit v1.6.2 “The State Has Noticed You Not Being Noticed” Edition Citizens,
Following a brief period of administrative confusion (classified), the Ministry is pleased to confirm that enforcement systems are now operating with renewed enthusiasm.
State Enforcement Now Fully Operational Previously, certain high-risk individuals were able to reach concerningly high levels of Heat without… consequences.
This has been corrected.
Players exceeding acceptable behavioural thresholds may now attract active enforcement attention
The State may deploy investigation patrols (also known as “raids”)
These are triggered dynamically based on your Heat level
The higher your Heat, the more likely you are to be… noticed Reminder: Being noticed by the State is not a reward.
Adaptive Suspicion Thresholds The Ministry has refined its detection systems:
Raid trigger thresholds now operate within a configurable range (default: 60–100 Heat)
This ensures enforcement remains: unpredictable
immersive
mildly unsettling You will no longer know exactly when the State decides you are a problem.
This is intentional.
Improved Internal Messaging Stability Certain internal communications previously appeared as:
“§cUnintelligible Ministry Noise”
This has been resolved.
All broadcasts, audits, and warnings now display correctly
The Ministry assures you the previous messages were not errors, but rather “early-stage linguistic optimisation” Visual Clarity Improvements Heat display colours now behave correctly
Citizens can once again clearly see: when they are safe
when they are not
when it is already too late ⚖️ General Administrative Corrections Various behind-the-scenes inconsistencies have been resolved
Systems now behave in a way that more closely aligns with official doctrine
The illusion of control has been restored ️ Final Notice from the Ministry “Compliance is not required. It is simply the most survivable option.”
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:8hfcZ97y:FLqr4qE5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8hfcZ97y:FLqr4qE5"
}

