What happened to the steam compatibility?
Trainer #2 in the list supports Steam.
Any idea what this means?
23:37:31: Stellaris, v3.0.1 (STEAM)
23:37:37: Successfully attached to stellaris
23:37:42: Script error in line 1: Cannot find aob for 'Console1'
Please delete the trainer, custom keys, debug folder where the trainer resides and all files in
C:\Users\USERNAMEHERE\AppData\Local\Temp
C:\Users\USERNAMEHERE\Cheathappens\Work
C:\Users\USERNAMEHERE\AppData\Roaming\Cheat Happens\0x90
C:\ProgramData\CheatHappens
Learn how to make your own Trainer Cleaner for the above paths here.
Reboot PC to clear excess memory, get a fresh copy of latest trainer and extract it. Run trainer as admin, read the instructions and try again. At times, a new game may be needed to resolve failed options if the data in your save file was altered. Use on a new game and test the option. If it now works, quit to main menu and load your save and try it again. May also need to run the game without the trainer first and play a bit so the save file gets updated to use possible new values. This typically will resolve the issue.
This cleaner is also part of the new Cheat Happens Trainer Manager 2.0, it is found in the settings and has an easy to use one button click feature.
Since the last update all your new trainers (containing the "mobile" part in their file name) trigger the windows defender.
In the past that didnt use to be a problem. But all your new trainers trigger the windows defender. And yes creating an exception fixed this but in the past your trainers didnt trigger the WD and it feels weird now.
What the "mobile" deal anyways? I have been out of the loop for a while.
Important Board Topics
Trending Topics