How it works

A trainer finds a value by its address in memory, and a game update moves everything around. That is why a trainer built for one build often does nothing at all on the next: it is looking in the right place for the wrong version.

Every entry here names the game build it was made against, right under the title, and the date it was last touched. Check it before you download. If your game is newer, the trainer is probably due a rebuild — and the entry will say so once it has had one.

If a game updated overnight and your trainer stopped working, nothing is broken on your machine. It just needs the new version.

Reading and writing another process’s memory is exactly what a trainer does, and it is also exactly what a certain kind of malware does. Antivirus engines cannot tell the two apart from behaviour alone, so trainers are routinely flagged — usually as something generic like HackTool or Win32/Riskware. Packed archives make it more likely, not less.

That is a real trade-off and not something to wave away. What we can do is keep the path short: every file here is served from our own server, with no mirror in between, no wrapper installer and nothing bundled alongside. What you download is the file that was uploaded.

What we will not do is tell you it is safe because a badge says so. Use your own scanner and your own judgement. If a page ever shows a scan result, it will say who ran it and when.

Some options change a number the game then writes to disk — money, levels, unlock flags. Switch the option off and the save keeps the value, because as far as the game is concerned you simply have that much money now.

Copy your save folder before a first run. It costs ten seconds and it is the difference between an experiment and a mess. A few entries here also warn about specific values that overflow if you push them too far — those warnings are in the amber box on the page, and they are not boilerplate.