Mizan vs Trinity Anti-Cheat

Trinity Anti-Cheat is a free, open-source anti-cheat for Garry's Mod, first released on GitHub in September 2026 and still in development. It runs entirely on your server and on players' games, as plain Lua. Mizan is a server-side anti-cheat and ban registry: it judges how players aim, move and time their commands, with the judging done on Mizan's own service.

This page is written by Mizan, so read it with that in mind. Every fact about Trinity comes from its own README, documentation and source code on its dev branch, linked at the end. If something here is wrong or out of date, email contact@mizan.ac and we will correct it.

How each one catches cheats

Trinity is a set of rules, each with its own threshold, and a set of scans. On the server, its aim rules flag view angles outside what the engine allows, a snap onto another player in a single tick, angles that change without any mouse movement, a shaky aim on a target, and clicking as fast as the engine allows (modules/aimbot). Its movement rules look at bunny hopping and auto strafing, and its exploit rules at speed hacks, tick counts and simulation time (modules/movement, modules/exploits). On the player's game, it scans for the traces of known Lua cheats: globals, hooks, console commands, detoured functions and loaded binaries (modules/scans, modules/detours).

Its own config is honest about the trade-off of a rule like these. Of the angle check, it says: "Depending on the addons you have, this can false flag quite a bit."

Mizan judges behaviour and never looks for a cheat's files. AI models score each fight by how the view moves against its target before, during and after the shot; algorithmic detectors test what a hand on a mouse can and can't do, and whether the numbers the game sends add up. No single reading acts alone. A case opens only when two independent kinds of measurement agree, unless an exact check of the game's own numbers fails, and each detector alarms only at 10,000 to 1 odds against normal play.

The difference: a single rule with a threshold is simple and you can read it, but it has to be set loose enough not to catch good players, and a cheat can be tuned to stay just under it. Two kinds of evidence that must agree is slower to open a case, and far less likely to open one on someone who wasn't cheating.

Wallhacks and ESP

Both try to stop a wallhack having anything to draw, by not sending a player the positions of enemies they can't see.

Trinity's main wallhack breaker traces lines from points around the player to each enemy (modules/breakers/sv_pvs.lua). It is off by default. Its config warns that it "may come with a moderate to severe performance impact depending on the size of the server", and switches it off above 16 players unless you change that. Its other breakers, for players far away and for view angles, are on.

Mizan's fog of war is fed by what its module already measures on your server and goes into the engine's own visibility, the way VALORANT and Rust hold back an enemy until you could see them. It is on for every server Mizan protects. Anyone you could already see or hear is still sent, so a wallhack can still show those.

What each one covers

Where Trinity is ahead

• Free and open source. Its GPL-3.0 code, with a Commons Clause that stops anyone selling it, is on GitHub for anyone to read and change.
• Everything stays on your server. It needs no outside service; nothing leaves your server unless you set a Discord webhook.
• No binary module. It is plain Lua, so it runs on hosts that don't allow binary modules.
• Client-side scans. It catches known Lua cheats the moment they load. Mizan doesn't look on the player's game at all.
• Under active development. Its dev branch had new commits through October 2026.

Where Mizan is ahead

• An evidence rule, not one threshold per check. Two independent kinds of measurement must agree, at 10,000:1 odds against normal play, and every false flag we've found is listed with its fix.
• Fog of war on every server, at any player count, inside the engine's own visibility rather than traced per player in Lua.
• Nothing on the player's PC to defeat. Trinity's client-side scans run on the cheater's own computer, in code anyone can read. Mizan's judgement runs on its own service.
• Bans beyond your server. Mizan reads hundreds of public ban lists, so a player banned on other communities' servers is known when they join.
• Replays and a dashboard. Each case comes with a 3D replay and its findings, on a web dashboard with roles for your staff.

Both ban through your admin mod. Trinity has cores for ULX, SAM, ServerGuard and xAdmin; Mizan supports nine admin mods or a ban command of your own.

Running Trinity beside other anti-cheats

Trinity says it can run beside QAC, MAC and SimpLAC. Its compatibility page warns that SwiftAC flags Trinity as a cheat, and that LSAC's own anti-ESP module conflicts with Trinity's.

Which one fits your server

Choose Trinity if you want a free, open-source anti-cheat you can read and change, with everything kept on your server, and you're comfortable tuning thresholds while it matures.

Choose Mizan if you want behaviour judged on a published evidence rule, wallhacks cut off by fog of war at any player count, replays for your staff, and the public ban lists in the same place, and you can run a native module.

The best Garry's Mod anti-cheats in 2026 covers every other option.

Sources

• Trinity Anti-Cheat: GitHub repository and README, its default server configuration (lua/tac/config/server.lua) and modules on the dev branch, and its compatibility page, read on 5 November 2026 at the dev branch's commit of 23 October 2026.
• Mizan: anti-cheat, comparison and false flags.