It *appears* that they meant to store the offending string in an encoded form and decode it at runtime, but they’ve botched it. Get used to this, it happens a lot in the Fallout76 anti-cheat. Well, they’re encoding them so that they can turn around and *decode* them. Which is kind of weird to see in 2019 but whatever.īut you might be asking yourself, “Why are they encoding the strings they’re searching for?”. So the usual suspects – Cheat Engine, IDA, and I think Spiro’s memory hacking thing.

I know it looks weird, IDA didn’t quite realize that those long ass constants are actually pointers. The scanning callback gets the Window Text and converts it to ASCII from widechar. That indirect call lands in a function that calls EnumWindow with the scanning callback On line 12 you can see the indirect call to the EnumWindowsTask object that leads to the actual scan. The scan is started by IOManager::ExecuteIOTask, which looks something like this: Looks for windows with titles that contain ‘bad word’ substringsĮach of the three primary anti-cheat scans are implemented as IOTasks, created, dispatched, and destructed with each iteration of the anti-cheat scanning loop.

But if the new Battle Royale seems attractive to you here are a few easy and simple ways to get caught by their anti-cheat. You probably aren’t hacking Fallout 76 because you probably aren’t playing it at all.

Fallout 4 trainer cheat engine