Wine on axiom0x0

Diablo 2: Resurrected | Building a Memory Trainer on Linux from Scratch (Part 3)

Wed, 06 May 2026 00:00:00 +0000

Part 3 of 3. Part 1 covered pointer chains. Part 2 covered pattern scanning and save editing. This is the one where everything shits the bed and elegant solutions are abandoned in favor of the good enough.

Finally, we arrive at Part3 of our D2R trainer series. After Parts 1 and 2, the trainer could read and write stats, freeze values, and edit save files. But the player still died. The freeze thread was writing max HP back to the stat array at 100ms intervals (10 times a second), and that sounds fast until you realize what the game is doing under the hood. The damage function reads HP, subtracts damage, checks for death, and writes the result back in a single frame (~16ms at 60fps). Our thread was racing the game and still losing. The player took a hit, HP dropped, the death check fired, and then our thread wrote max HP back, but unfortunately too late.

Diablo 2: Resurrected | Building a Memory Trainer on Linux from Scratch (Part 2)

Fri, 10 Apr 2026 00:00:00 +0000

Part 2 of 3 — Part 1 covered pointer chains and the building blocks. This is where the plan meets reality.

Part 1 ended with a fairly clean setup. That is, find the process, find the module base, walk a pointer chain, read or write the value. On Windows, that’s a well-established approach. Cheat Engine has built-in pointer scanning, there are community-maintained offset tables, and the technique has been documented for decades.

Diablo 2: Resurrected | Building a Memory Trainer on Linux from Scratch (Part 1)

Sun, 05 Apr 2026 00:00:00 +0000

Diablo 2: Resurrected | Building a Memory Trainer on Linux from Scratch (Part 1)

Part 1 of 3 — scanmem, pointer chains, and the building blocks of a trainer.

If you’ve ever tried to create your own game cheats, you probably started with memory scanning. By far, it’s the most direct path: find a value, narrow it down, change it, done.

I know how to use scanmem or CheatEngine to do that. But every time your game restarts, the addresses are gone and you have to do your scanning all over again. It works, but it’s tedious, and it’s clearly not how real trainer makers do it. Tools created from groups like CheatHappens and WeMod don’t ask you to scan for gold every launch. They somehow just know how to find it.