Eyes on, hands off.

Yes — play on your normal account. The standing, audited statement: the client does not read, write, inject into, hook, or open a memory or module handle to the Day of Defeat / Half-Life game process. It interacts with the game through four channels only — screen capture via the same API OBS and Xbox Game Bar use, passive read-only input observation, read-only file hashing, and process-name enumeration.

That statement is re-verified against every release by two independent whole-codebase audits, run before the build is published, and nothing found contradicts it. VAC's concern is software that opens the game's process and memory; this client structurally never does.

The input hooks are Windows low-level hooks — system-wide by construction — and they are strictly read-only: every event is observed and passed straight through, never blocked, altered, or synthesized. Collection only happens during a session you start; the client's in-app disclosure panel lists exactly what is kept.

Mouse motion is read from the device stream and recorded only while Day of Defeat holds focus, as movement distance per 10 ms — not cursor positions. And the client never produces input of its own: the APIs that would (SendInput and friends) are deny-listed and appear nowhere in the shipped binary — it detects synthesized input, it never makes any.

Capture is aimed at the game window. The client works down a ladder of capture methods, and the window-targeted rungs point at DoD's window specifically; when a whole-monitor method has to be used as a fallback, the client reads the game window's rectangle and crops the frame to it. No capture path injects anything or reads game memory — it's the same out-of-process mechanism screen recorders use.

It's recorded honestly rather than ignored. On legacy exclusive-fullscreen OpenGL setups, every safe capture method can come up blind — since 0.7.8 the client records an honest "no frame captured" for those stretches, and that raises the session's coverage flags: a reviewer sees a gap in the visual evidence instead of a false clean pass. It is a coverage note for a human to weigh, not an accusation — and the file check reads your disk, not your screen, so it works the same in any display mode.

If you want your screenshots to actually land, run DoD borderless-windowed — the capture handles that natively. Add -window -noborder to DoD's launch options in Steam and set the in-game resolution to your desktop's.

Its file access to your game is read-only — hashing, with a share mode chosen so the running game is never blocked — and zero writes, copies, moves, or deletes ever target the game tree. Every write lands in the anti-cheat's own locations: its update directory, its app data, and the session bundle.

It runs as a normal user program: no installer, no kernel driver, no elevation requested, no debug privilege. It never launches or closes the game.

In the game tree: your DoD install is fingerprinted (SHA-256) against the league's known-good list. An unexpected DLL in the game directory gets its version metadata read — the same information Explorer's Details tab shows — and an unexpected or hash-mismatched file may be byte-copied into your session bundle so a human can look at it, rather than the client guessing.

The complete collection inventory — including the peripheral-software config files used to recognize your mouse and keyboard — is in the client's own disclosure panel (the "What we collect" button on the main window), which is corrected in step with every release.

The game server scores some things on its side — for example, aim geometry derived from the ordinary network traffic the engine already requires to play. The client neither produces, reads, nor transports that data; nothing on your machine is touched for it. Server-side measures of that kind run measure-only, carrying no verdict weight, until they've been validated.

A flag is a request for human review, not a verdict. The server re-scores every session from the raw evidence, and a person reads every flagged session before anything happens. Legitimate hardware and setups trip detectors sometimes — Hall-effect keyboards, custom HUDs, sound mods — and the release history is full of exactly those cases being fixed in the detector, not held against the player. If a result looks wrong to you, ping a KTP admin in the Discord and they'll walk through the evidence with you.

Every release is Authenticode-signed with KTP's certificate — thumbprint 6CBE28B800C52073A27A3B6A4B7A2F07A7236A28 (right-click the exe → Properties → Digital Signatures). The root is KTP-issued rather than a commercial CA, so Windows may call the chain untrusted; that's expected. The enforcement is in the client itself: it pins that thumbprint and checks it on every update it installs, so a tampered or unsigned update is refused rather than applied. It does not re-check the copy already sitting on your disk, so on a build you did not get from this page, verify the signature yourself.

Cheat-evasion prevention: public detector code is a study guide for the people it's meant to catch. What's public instead is the part that concerns your machine — the audited interaction statement this page is built on, re-verified every release. And the guarantees aren't just prose: the build gate refuses to compile a deny-listed API, and the client's full native-call inventory is pinned, so the surface can't grow without the change being declared and audited.

No — there is no macOS build to download. The client is published for Windows only; that is what the build and release scripts produce. Some macOS support exists in the source, but nothing is shipped, so there is nothing to install. VAC does not run on macOS either, and modern macOS needs a compatibility layer to run DoD at all. Play on Windows.