Tags
Creators
Details
1.6.5
Compatibility
Changes
NeoModeration 1.6.5
Cloud verdicts and player input handling are more reliable. Local word/link and anti-spam checks work without an account; optional cloud evaluation starts with /nmod trial and runs in monitor mode.
- Parse complete JSON scores, including scientific notation. Respect disabled categories and custom thresholds; malformed or missing verdicts count as unavailable.
- Cloud outages and busy workers follow failOpen without issuing strikes, mutes or other player punishments. Cloud monitor mode continues to allow chat. /nmod test shows the same outcome.
- Remove quadratic local matching for long whitespace and repeated separated-letter inputs.
- Scan namespaced forms of configured messaging commands. Block flagged extra-surface content when censoring cannot remove it, including split sign/book content.
- Cache map verdicts by saved image content and cloud settings, so changed artwork is checked again. Limit concurrent map scans and cloud chat work.
- Protect trial activation from duplicate requests and configuration races; apply its key on the global scheduler and start cloud checks in monitor mode. Reject malformed trial status responses.
- Disclose aggregate bStats charts in the public README.
After installing, run /nmod doctor and /nmod test badword. Review your starter word list. /nmod mode enforce controls local rules; /nmod cloudmode enforce controls cloud decisions separately. Optional sign/book/anvil/command surfaces remain configurable.
Automated verification covers Paper 1.18.2, 1.19.4, 1.20.6 and 1.21.11. Current calendar releases need a separate startup check; this release makes no new automated 26.x chat coverage claim.
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:b3WivO4t:nJhVISGu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:b3WivO4t:nJhVISGu"
}

