#Fallout 4 trainer cheat engine code#
#Fallout 4 trainer cheat engine windows#

But if thereвЂ™s no debugger, the error code will be changed. If a debugger is attached the error code shouldnвЂ™t change during the call to OutputDebugString. The scanning function is mostly nothing out of the ordinary вЂ“ it checks IsDebuggerPresent, CheckRemoteDebuggerPresent, and calls OutputDebugString and checks GetLastError. Each bad window title has its own value thatвЂ™s added to the cheater flag.Д®numToolsTask is created and dispatched in the same way as the EnumWindowsTask. If youвЂ™re lucky enough to get detected by the galaxy brains at Bethesda who donвЂ™t realize people use debuggers and IDA as part of their jobs and might accidentally leave one open when launching Fallout, youвЂ™ll get marked as a cheater. So on top of the previous verboten window titles, you can also get flagged for вЂњIDA вЂ“ вЂќ (the IDA window title if youвЂ™ve got a project active), WInDbg, ењ†4dbg, and x96dbg (which is a launcher for x32dbg/ењ†4dbg, I think). If thereвЂ™s a match, a variable is set that is used later in the function to mark you as a dirty, filthy cheater.ДЄlso, some of the strings are built on the stack instead of going through the encoding/decoding stuff. Instead, the strings are stored in the clear, encoded, then decoded for comparison.Д®ach decoded string is passed through a case insensitive strstr against the title of the window thatвЂ™s been passed by the EnumWindow function. 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:

#Fallout 4 trainer cheat engine windows#

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.