Tags
Creators
Details
1.6.3
Compatibility
Changes
NeoModeration 1.6.3 — Minecraft Threat Intelligence and Instant Evaluation Trial
This release introduces direct server-side threat detection for obfuscated IP addresses and advertising patterns, along with a zero-friction evaluation bridge for Neomechanical cloud moderation. Server administrators can now activate a 14-day trial of cloud scanning directly with /nmod trial.
New and Improved
- Instant Evaluation Trial (
/nmod trial): Server owners can test context-aware cloud moderation immediately without leaving Minecraft or manually generating credentials upfront. Evaluation activations are authenticated via signed plugin handshakes with server-side expiry. - Obfuscated Advertising and IP Filtering: Enhanced detection for evasive server IP formats, disguised dots, spaced digits, and port evasion in chat and signs.
- Trial Status and Expiration Reporting:
/nmod trial statusand/nmod doctordisplay remaining trial days, credit quotas, and direct links to claim or extend workspace keys. - Hardened Handshake: All evaluation requests use tamper-resistant install identities and timestamped HMAC verification to protect trial access.
Verify and upgrade
Run /nmod test badword to preview the bundled local rule without executing actions. Run /nmod status and /nmod doctor to inspect configured checks and cloud health. Local matches block on a new install; /nmod mode monitor previews them through alerts, while /nmod mode enforce restores blocking. Cloud decisions start in monitor mode and only block after /nmod cloudmode enforce.
Run /nmod trial to begin a 14-day evaluation trial of context-aware cloud protection.
Existing servers keep their saved config.yml, including action lists, strike settings, modes, category toggles, word rules and API keys. Review the starter English list for your server. This release has no measured effect yet on installations, repeat use, cloud activation, sign-ups or revenue.
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:Jk42eW1W"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:b3WivO4t:Jk42eW1W"
}

