NeoModeration 1.6.2 — First-run status and cloud coverage corrections

This release corrects what a new server owner sees after installing 1.6.1. The intentional block-only policy no longer appears broken in /nmod doctor. Startup, status, doctor and privacy now use the same configured-coverage check, so they do not describe disabled checks as active. These are reporting corrections; they do not change an existing server's saved policy.

Fixed

• /nmod doctor treats an empty extra-action list as healthy: local rules can still block a matched message without muting or clearing chat. It names local and cloud modes separately.
• /nmod status, startup output and /nmod privacy describe only checks that are configured to run. bStats coverage charts use the same calculation; cloud account health remains a separate question from configured coverage.
• With all cloud text categories disabled, chat no longer sends a cloud text request. Key-gated map scanning is independent and unchanged.
• /nmod test <message> respects disabled chat scanning and correctly previews local censoring. The command now explains that rate, caps, repetition, command and map checks need live context; a one-message cloud preview cannot demonstrate conversation context.

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.

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.