Working on a table rn, will include pointers and scripts Incase u want to use either or.
As far as game auto closing/crashing before you attach cheat engine make sure the debugger settings in cheat engine are using VEH debugger. Changed mine from windows debugger to veh and now game stays open no crash. My table working just fine.
Working on a table rn, will include pointers and scripts Incase u want to use either or.
As far as game auto closing/crashing before you attach cheat engine make sure the debugger settings in cheat engine are using VEH debugger. Changed mine from windows debugger to veh and now game stays open no crash. My table working just fine.
Working on a table rn, will include pointers and scripts Incase u want to use either or.
As far as game auto closing/crashing before you attach cheat engine make sure the debugger settings in cheat engine are using VEH debugger. Changed mine from windows debugger to veh and now game stays open no crash. My table working just fine.
Heard the game's crap, so thought maybe the anti-cheat protection would be a challenge. However, when faced with the possibility of creating/enabling the in-game UConsole, what else is there to achieve? Yeah, anti-cheats usually fuck-up game performance, either doing sequential reads of memory or threading, but then again.. this discussion and the need to defeat some "anti-cheat" is only for those who deal with HOOKS (modifying executable code). Will post shortly a proof of concept of what can be done in-game, without the need to use a trainer.. or tampering memory.
Am using the CODEX release, for obvious reasons (game being crappy, no need to tamper with executable memory, method working even for the official build; lastly, not going to buy it).
Come to think about it, this isn't even a crack. So the CODEX version just bypasses the Windows Store protection to allow you to play the game. That's all. It's a bypass, not a crack:
See the game .exe in that folder? I don't. That's what qualifies as a crack - - seeing the game .exe dumped/rebuilt/cleaned. The scene in 2019 is pure crap. Either that or people really started mangling terminology (pretty much like a modified picture is always "Photoshop-ed").
If someone knows how to fucking disable the narrator, I'd be grateful to them. Might be only in this cracked version...
Meanwhile...
Thanks for the info, Cal! The problem I'm having with the CODEX version is debugging. Either it's the game itself or CODEX added some crap.. VEH debugger crashes the game within 10-15 seconds, if it enables. Else, I just get locked out from DLL injection; using manual mapping myself, but we know the VEH has to be injected by its default method. Tried DBVM + dbk, got a crash there as well. So the bit of room I had to work with the game led to the video above
Given that console key is bitchy (Tilde key is also used for some weapon swapping), I decided to do some digging. All UE4 games store default configuration in %appdata%/Local/. This game stores it here (not sure if the same for the official build): C:\Users\SunBeam\AppData\Local\Packages\Microsoft.48248D2C77101.bef2a05aae_8wekyb3d8bbwe\LocalState\Nimbus\Saved\Config\UWP (replace "SunBeam" with your user). So now:
That should do it Release soon
BR,
Sun
EDIT: Yeah, CODEX uses VMProtect to shield WinStore.Love.Auth.dll and WinStore.Love.dll. In doing so, the retards missed the fact that they might also kill the chance for those playing the game to hack at it
Release soon 
