Skip to content

NeoModeration 1.6.1

Choose a tag to compare

@KyTDK KyTDK released this 24 Sep 08:15
· 28 commits to main since this release

NeoModeration 1.6.1 — Block the message, spare the server-wide chat

NeoModeration should be useful from the first minute without punishing a player for one match against an unreviewed starter list. On a new install, local word, URL and anti-spam matches still block immediately, alert staff and log a case. Extra actions are now empty and strike escalation is off: a first match does not clear chat for everyone or mute the player for five minutes. Cloud decisions still start in monitor mode.

Fixed

  • /nmod test <message> now applies the right mode to the deciding engine. A cloud flag in cloud monitor mode previews an alert, even if local rules enforce. The test states that rate, repetition, command and map checks need live context.
  • NSFW map-art cloud verdicts now obey cloud mode. A flagged map alerts staff without confiscation while cloud mode is monitor, even when local word rules enforce.
  • /nmod status now shows cloud MONITOR or ENFORCE when a key is configured, instead of the ambiguous “CONFIGURED.”
  • /nmod action reset returns to block-only extra actions. Strike escalation remains a separate setting.
  • /nmod preset family|community|minimal now tunes cloud thresholds without silently replacing an operator's punishment policy. A key is still required for cloud checks.
  • Startup output and the bundled documentation now state exactly what the new-install policy does.

Verify and upgrade

Run /nmod test badword to preview the bundled local rule without executing actions. Run /nmod mode monitor if you want all local decisions to alert only; /nmod mode enforce restores blocking. Use /nmod cloudmode enforce only after reviewing cloud results.

Existing servers keep their saved config.yml. This release does not rewrite an existing action list, strike ladder, modes, word list or API key. Review /nmod status and /nmod action list after restarting. To adopt the new block-only extra-action default on an existing server, use /nmod action reset and disable moderation.strikes.enabled in config.yml if you previously enabled strikes.

The safer defaults are a product hypothesis. They have not yet been shown to improve install retention or cloud activation; those outcomes will be measured separately.