NeoModeration 1.4.1 — Activation clarity

NeoModeration 1.4.1 makes the first-run and cloud-recovery paths explicit. A fresh install still starts safely in monitor mode: it detects and reports, but does not block or punish until an admin runs /nmod mode enforce.

Improved

• Guided first test. Startup, help, README, and marketplace copy now point to /nmod test badword. It proves the bundled local rule works and states that monitor mode will not execute an action.
• Truthful key setup. Saving a key no longer claims cloud moderation is active before it has been checked. /nmod doctor verifies the account and usage API, latency, and the current credit balance; /nmod test hello verifies the moderation-events path separately.
• Actionable cloud recovery. HTTP 401/403 is reported as a rejected key, while HTTP 402 is reported separately as insufficient credits. Recovery commands provide the matching key or billing link without echoing an API key.
• Honest billing classification. Ordinary Minecraft chat uses the platform's general content class. Only NSFW map-art image scanning declares nsfw.
• Separated cloud health. Chat tests and map-art scans feed the moderation-event circuit/status state. Account checks cannot make a broken events endpoint look healthy.

Compatibility

• No configuration migration is required.
• Existing enforce-mode servers remain in enforce mode. Monitor is only the default for a genuinely new config.
• Supports Minecraft 1.18.2–1.21.11 on Bukkit, Paper, Purpur, and Spigot. Folia is not advertised.
• Local word, URL, and anti-spam rules continue to run when cloud moderation is unavailable or out of credits.

Verified

• Automated regression coverage includes 401/403, 402, other 4xx, transient failures, separated account/event health, recovery routing, locale parity, billing classes, and the guided monitor-mode test path.
• The release matrix checks Paper 1.18.2, 1.19.4, 1.20.6, and 1.21.11.