# No Chat Reports on your server

One jar in the server's `mods` folder protects everyone on it. Signatures get stripped before messages are relayed, so chat reporting stops working for every player who joins — vanilla clients included.

First, the naming confusion, because it costs server owners real time: there is no official No Chat Reports *plugin*. The Paper and Spigot plugins wearing the name and icon weren't written by Aizistral, and nobody can vouch for them. The original runs on Fabric, Forge, NeoForge and Quilt servers — [grab the build for your loader here](/download/).

Setup is the same as any server mod: drop the jar in `mods`, restart. Config files appear in the `NoChatReports` folder. From there you can convert player messages to system messages so vanilla clients don't see "Not Secure" flags, or flip the option that requires joining clients to run the mod too. Since 1.20.2 one thing is out of the server's hands: the client-side "unsigned messages" warning only disappears for players who install the mod themselves.

Three references worth knowing: [the wiki](https://github.com/Aizistral-Studios/No-Chat-Reports/wiki) documents every config option, including "Protecting Server Players" and "How to Get Safe Server Status" — that's what earns your server the green check in players' chat screens. Behind a Velocity proxy, set `force-key-authentication = false` in `velocity.toml` (thanks MrMelon54). And if you build server software of your own, there's a developer article on making the mod recognize it as safe.

The green check: what your players see once the server is recognized as safe.

## Every server platform, covered

What actually protects players depends on what you run. Follow every step that matches your stack, not just one.

### Fabric / Forge / NeoForge

Install [this mod](/download/) on the server. Players with it client-side see the green check. Since 1.20.2, vanilla players still get the "messages not signed" warning — removing it server-side would clash with Minecraft's usage guidelines, so only a client-side install hides it.

### Paper / Purpur / Folia

Install [FreedomChat](https://github.com/e-im/FreedomChat) with `rewrite-chat` and `send-prevents-chat-reports-to-client` both true. That earns the green check. On the Leaves fork it's built in: set `settings.misc.no-chat-sign` to true in `leaves.yml`. Plain Spigot is a rougher story — the wiki points to Liberated Chat there.

### Proxies

Velocity: `force-key-authentication = false` in `velocity.toml`. BungeeCord and Waterfall: `enforce_secure_profile: false` in `config.yml`. Either lets modded clients through unsigned; it doesn't by itself protect vanilla players, so pair it with a backend measure above.

### Vanilla & edge cases

Pure vanilla: set `enforce-secure-profile=false` in `server.properties` — modded clients are then safe, vanilla ones aren't, and nothing server-side can fix that without software. Pre-1.19 backends need nothing; reporting doesn't exist there. Quilt servers are a known no since Minecraft 1.20 ([#423](https://github.com/Aizistral-Studios/No-Chat-Reports/issues/423)) — use Fabric instead. LAN worlds: host from a client running the mod. Offline mode technically stops signing but lets anyone impersonate anyone, so the wiki doesn't recommend it. And [Realms](/realms/) is its own, worse, story.

Condensed from the wiki's [Protecting Server Players](https://github.com/Aizistral-Studios/No-Chat-Reports/wiki/Protecting-Server-Players) article, which tracks platform changes and stays the canonical reference. Building server software of your own? See [how to earn the safe status](/safe-server-status/).

- [ Get the server build ](/download/)

Fabric, Forge, NeoForge and Quilt. Every version, hosted here.

---

Canonical: https://nochatreports.com/server/
Catalog: https://nochatreports.com/api/mod/catalog
Download a row: `GET /api/mod/download?versionId={id}&loader={loader}`
Full catalog UI: https://nochatreports.com/download/