Summary
- No Chat Reports 2.20.2 released 18 August 2026, fixing a server ping crash.
- A 1.20.1 build, v2.2.3, shipped the same day – a version line four years old and still maintained.
- The crash occurred during server list pinging, before joining anything.
A crash on the multiplayer server list is a particular kind of annoying, because it happens before you have done anything. You open the list, the game pings your servers to show their status, and it dies.
What server pinging is
Every entry in your multiplayer list gets a small status request when the screen opens – player count, MOTD, ping time, version. It is a separate, minimal protocol exchange that happens before any real connection.
Mods that add information to that display, as this one does, are operating in a narrow and easily broken part of the code.
Why the 1.20.1 build matters
Because that is where the modpacks are. Large packs settle on a version and stay there for years, and a mod that drops support strands every pack built on it.
Shipping 26.2 and 1.20.1 builds on the same day is a maintenance burden the author has chosen to carry. It is also the reason the mod is in so many packs.
The policy question underneath
This mod exists because of a disagreement about chat reporting that has been running for years, and installing it is a position rather than a convenience. Server owners end up deciding where they stand on it whether they want to or not.
That decision belongs with the rest of the moderation setup, not separately from it – the whitelist, roles and rules you write before anyone joins is the frame that makes the chat question answerable.
For players choosing where to play
Whether a server runs this tells you something about its posture, though not as much as people claim in either direction. What matters more is whether the staff have thought about moderation at all, and that is visible in about ten minutes of reading a server’s own rules.
The signals worth checking before committing time are mostly of that kind – things you can observe rather than things you have to ask.
Version history
- 26.2-v2.20.0 – initial 26.2 port.
- 26.2-v2.20.1, 4 July 2026 – Vulkan crash fix.
- 26.2-v2.20.2 and 1.20.1-v2.2.3, 18 August 2026 – server ping crash fix.
Three releases in six weeks, all fixes. The mod has not gained a feature this year and does not need to.
Why 1.20.1 is still a major version line
Large modpacks take a year or more to build and a further year to stabilise. By the time one is polished, Minecraft has moved two versions on, and moving the pack means re-testing hundreds of mods for no gameplay benefit.
So packs stay. 1.20.1 and 1.21.1 carry an enormous share of modded play, and mods that abandon those lines lose most of their real audience while gaining the newest one.
What maintaining two lines costs
- Two codebases that diverge slowly.
- Every fix applied twice, sometimes differently.
- Two sets of bug reports that look identical and are not.
Most single-author mods cannot sustain this. The ones that do are the ones that end up as pack dependencies, which is a self-reinforcing loop.
Crashes before joining a server
The server list screen does more than it looks like: it opens connections to every saved server, parses responses, decodes a base64 icon, and renders a MOTD that can contain formatting codes. Any of those can fail on a malformed response.
If your game crashes on that screen, the fastest diagnostic is to remove servers from the list one at a time. It is almost always one specific entry.
Chat policy as a server decision
- Decide before you open, not after an incident.
- Write it down where players can see it.
- Be clear about what staff can and cannot see.
- Apply it consistently, which is the only part that matters.
Servers rarely fail because they chose the wrong policy. They fail because they had no policy and improvised one under pressure.
Version summary
26.2-v2.20.2 for the current line, 1.20.1-v2.2.3 for the modpack line, both on 18 August 2026, both on Fabric, Forge and NeoForge.
The wider point about version lines deserves repeating. A large share of modded Minecraft is not played on the newest version and never will be, and the mods that understand this are the ones that end up everywhere. Chasing the release is visible work; maintaining the branch three versions back is not, and it is what the packs people actually play are built on.
Images: No Chat Reports project gallery on Modrinth.