File Integrity
Every .pk3, executable, and required asset is MD5-checked against the published whitelist before the game is allowed to launch.
MoH Arena publishes the current launcher policy, runtime whitelist, competitive cvar rules, and bind restrictions here.
The launcher verifies your install, applies the active competitive policy, hands you off to the server with a signed auth token, and maintains a live session with the website while you play.
Major violations: missing auth token on protected servers, unauthorized game files, checksum mismatches, blocked bind/script commands, recoil-style aliases, and tampered launcher heartbeat/session state. Major violations can trigger an automatic kick from protected servers.
Minor violations: plain aliases and competitive cvars outside the published range. Tracked and published in v1 but do not trigger an automatic kick unless the server admin enables stricter policy.
Cheat-ban consequences: players caught cheating are banned and receive a red Cheat Ban badge.
Every .pk3, executable, and required asset is MD5-checked against the published whitelist before the game is allowed to launch.
A background session pings the website every 20 seconds. Tampering, process kills, or missing pings surface as major violations in real time.
Allows normal MoH binds like toggle, togglemenu, model selection, and connect, while flagging aliases, exec, vstr, and recoil-style scripting.
Protected servers render an in-game overlay showing "AC Active · N/M players protected" and flag any joiner who is not running the launcher.
Server admins can enable kicks for major violations, minor violations, or players without the launcher — with no manual intervention needed.
No screenshots, no keylogs, no process spying. Only the game folder, cvar snapshot, and a hashed hardware ID leave your machine — documented in full.