HailWall
by Abaraburu
HailWall is a server-side mod whitelist and blacklist that checks the mods a joining player's client has installed and kicks anyone running a disallowed mod.
What it does
Installation goes on both the server and every client, and the mod needs Fabric API. During login the server requests the installed top-level mods from the client, which answers with each mod's id and version under an HMAC signature, and the server then checks that list against its configuration. A player whose list fails the config is disconnected before entering the world. Files are published for Fabric and NeoForge across 16 release versions, 1.16 – 26.1.2, and the code is open source under the MIT License.
The config offers two modes. Whitelist mode blocks everything except the mods listed, with essential loader, Minecraft and Java entries plus HailWall itself always allowed. Blacklist mode allows everything except the listed mods, such as cheat clients or x-ray mods. Required mods can be set so that players missing a mandatory mod are kicked. Server operators are never kicked, even when they run extra mods, and a monitor mode can record every player's mod list without kicking anyone, which lets a server roll the rules out without disrupting its build list.
Key features
Whitelist and blacklist modes
Whitelist mode denies every mod not listed, while blacklist mode permits all mods except the ones named in the config.
Signed login handshake
The client's mod list is signed with HMAC and paired with a per-connection challenge, which blocks trivial packet spoofing.
Monitor mode
An enforcement switch can be set to log only, recording each joining player's mods so rules can be tested before kicks begin.
Operator bypass
Server operators are exempt from the checks, so admins can run extra tools without being removed from the server.
Login-time cost only
The check runs once during login and the log is written off-thread, so HailWall adds no per-tick cost during play.
Gallery
Compatibility
Latest build for each game version and loader.
26.x3 of 3 versions with builds
1.21.x1 of 1 version with builds
1.20.x1 of 1 version with builds
1.19.x2 of 2 versions with builds
1.18.x3 of 3 versions with builds
1.16.x6 of 6 versions with builds
Only full game releases are shown. This mod publishes no snapshot builds.
Requirements
Dependencies declared by the latest file for each loader.
Required 1
How it compares
Zeffut Mod Checker is client-side only, runs on Fabric and NeoForge for 1.21.11 – 26.2, and is not open source under All rights reserved. ChatPurity is server-side only, open source under the MIT License, and published for Fabric for 1.20 – 1.21.11, so it runs without any client install. HailWall needs both sides and covers a wider range of versions on two loaders.
| Mod | Loaders | Game versions | Environment | Updated |
|---|---|---|---|---|
| HailWall | Fabric and NeoForge | 1.16 – 26.1.2 | Client and server | 2026-06-06 |
| Zeffut Mod Checker | Fabric and NeoForge | 1.21.11 – 26.2 | Client-side only | 2026-09-04 |
| ChatPurity | Fabric | 1.20 – 1.21.11 | Server-side only | 2026-03-21 |
Questions
Does HailWall need to be installed on the client?
Does HailWall need Fabric API?
Can HailWall stop a determined player?
In the catalog
HailWall is one of 8,016 Management mods on ModsFinder, and one of 5,930 Management mods for Fabric. 15,189 mods support Minecraft 26.1.2.
Similar mods
What the author says
HailWall checks the mods installed on a player's client when they join, and kicks them if they have disallowed mods (or are missing a required one). It's a modern, lightweight take on the classic Mod Whitelist idea. During the login handshake the server asks the client for its mod list. The client replies with its…
Official listing
- Modrinth page
- modrinth.com/mod/hailwall
- Owner
- Abaraburu
- Published
- 2026-06-02
- Updated on Modrinth
- 2026-06-06
- Facts verified
- 2026-10-15