YSN-AC watches two things at once: what the server can prove about your movement and your shots, and what a small client-side module can see about the memory of your own game. Findings from either side are recorded. Only a handful of them are ever enough to ban somebody, and the system is built to keep those two categories apart.
Health the server never gave you, armour that appeared, weapons nobody issued, movement the physics cannot produce, world changes you did not make. These need no threshold and no tuning: the server already knows what it handed out.
The client module reports modules that are mapped but hidden from Windows' own list, threads running from memory that belongs to no file, and jumps patched into those regions. It is the half that finds injected cheats.
The server names random bytes of the anticheat and asks the client to hash exactly those, with a fresh challenge each time. The reference copy is on the server, so a patched client cannot simply claim to be intact.
Shots off the aim vector, snap geometry, fire rate and the shape of a turn. All of it is measured and none of it is a ban reason, because on our own data none of it separates a cheat from our best honest player.
Every finding writes a second-by-second replay of the moment it fired. An accusation you cannot show somebody is an argument, not evidence, so the recording comes with the finding rather than after it.
Six conditions are re-checked every minute and say so when they break. A silent detector and a clean server look identical from the outside, and that has already cost us days.
ysnac.asiGet it from the link an admin gives you, or from the pinned message in our Discord. Do not use a copy from anywhere else — the server checks the bytes, and a different build fails.
The same folder as gta_sa.exe. You need an ASI loader installed already; if SA-MP mods work for you, you have one.
It reads your game's memory, which is exactly what a cheat does, so scanners are suspicious of it. Add an exclusion for the file.
There is nothing to configure and no window to click. If it is loaded, an admin sees your machine reporting in; if it is not, they see that too.
Rebuilt the file yourself? It will fail attestation, and that is the check working rather than a problem with your PC. Use the copy we distribute.
The list of modules loaded into your game process, the protection flags on their memory, which threads are running and where from, and hashes of code the server names. Plus your nickname, your IP as the server already sees it, and an identifier for the Windows install.
Other programs on your PC. Your files, your browser, your keystrokes, your screen. It does not stay running after you close the game, and it has no updater and no network access of its own — it answers the server and nothing else.
Findings are recorded against a Windows installation, not a person. A shared PC looks like one machine, and a reinstall breaks the link. That is a limit of the method and we would rather state it than have it discovered during an argument.