- GD 64bit - Grim Internals - DPYes (unlocking the console enables DPYes to save teleport locations anywhere)
Just run the program while Grim Dawn is running. The program will end instantly and unlock the console for the current launch of Grim Dawn. Doesn’t need to be in any specific location.
(the 3rd one is AREAE_JORDYTHCHOSEN) and restart the session. YT video
Pro tip: these tokens have different priorities, so if you want to test all Ravagers, you can select the 3rd one normally, fight it, then grant yourself the 2nd token, fight 2nd Ravager and finally grant the 1st token to fight the Flesh one all without needing to revoke any tokens (the 1st command). Basically fight all 3 Ravagers with just 2 commands.
Just run the program while Grim Dawn is running. The program will end instantly and unlock the console for the current launch of Grim Dawn. Doesn’t need to be in any specific location.
How to run GD Console Unlocker automatically in Steam
put GDConsoleUnlocker.exe and an additional batch file console_unlock.bat in the game’s main Steam directory (the one you get after clicking to browse local files in Steam)
This worked for me with Steam, might be slightly different for GoG (maybe you’d run Grim Dawn.exe instead of x64\Grim Dawn.exe for example.
I put 10s timeout because Steam asked me additionaly if I want to run GD with x64 custom option before running the game which took more time. Can be 5s or so for GoG.
Also I updated the program in the OP to be theoretically more reliable - I reversed the order I patch two memory regions (GD’s and my own). Before Grim Dawn could theoretically jump to my memory region before it was prepared.
I seem to understand it, thank you for your answer.
Experiments have proved that whether there is Steam or not, just put GDConsoleUnlocker.exe and console_unlock.bat into the GD root directory and run console_unlock.bat to complete it. In addition, this method is not only applicable to Steam, but also GOG.
This worked for me with Steam, might be slightly different for GoG (maybe you’d run Grim Dawn.exe instead of x64\Grim Dawn.exe for example. I should have access to my GoG Grim Dawn soon, then I can test it.
I put 10s timeout because Steam asked me additionaly if I want to run GD with x64 custom option before running the game which took more time. Not necessary for GoG.
Also I updated the program in the OP to be theoretically more reliable - I reversed the order I patch two memory regions (GD’s and my own). Before Grim Dawn could theoretically jump to my memory region before it was prepared.
I don’t know anything about programming, but my initial idea is to add a file like winmm.dll in the x64 directory like DPYes, which can mount DPYes at the same time when starting GD x64 normally, without having to run DPYes.exe separately.
Not sure if I’m getting it… Everything is working for you right? Or do you have problems with something still? (like running DPYes and Unlocker together for example?)
Or are you just mentioning another method of making Unlocker (as a .dll) which could allow running it automatically? I’ve never made a .dll yet so I’m not gonna do it unless it’s necessary but thanks for the information I didn’t know Sleepless had such a variant of DPYes.
No no, I currently run DPYes and Unlocker and everything works fine without any problems.
Just exploring the possibility of another way to make Unlocker (.dll file) so that it can be run automatically with GD like DPYes.
Just now I tried to make x64\winmm.dll start with GD, and found that it works even without DPYes.exe.