[Tool] GD Console Unlocker - change Ravager, reset Mogdrogen, teleport / warp if stuck etc. in Main Campaign

Grim Dawn Utilities and Resources
1

GDConsoleUnlocker.zip (15.2 KB) for

- GD 64bit
- Grim Internals
- DPYes (unlocking the console enables DPYes to save teleport locations anywhere)

How to run GD Console Unlocker automatically with Steam / GOG

To activate the console press ~ or ’ (depending on your keyboard).

To change Ravager from Flesh to Minds type

character.RevokePlayerToken "AREAE_TYVALDCHOSEN"
character.GrantPlayerToken "AREAE_AURINCHOSEN"

(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.

To reset Mogdrogen type

Character.RevokePlayerToken "MOGDROGENAVATAR_KILLED"

and restart the session. YT video

Some noteworthy commands for testing purposes:

  • character.SetPlayerInvisible true - Makes it so enemies dont see the player and thus dont attack - but you can attack them

  • character.WarpCursor true - Makes it so player always warps to destination

  • game.Give - Creates an object and gives it to the player

  • game.God true - Enables or disables god mode

  • game.Invincible true - Toggles being invincible.

  • game.PlayStats true - Displays a variety of player stats on the screen

  • character.LogData - Shows a variety of data above player, NPCs, monsters

  • game.ShowHud false - Enables or disables the UI, Default key binded to ]

  • game.Spawn - Creates an object at the player’s location (you can summon bosses with it)

  • game.Speed 3.5 - Sets the game speed multiplier to 3.5

  • game.Teleport X Y Z - Teleports the player to the specified world space coordinates

(some arguments might be incorrect, for example there might be a command that doesn’t require true / false but rather takes no arguments)

PS Hopefully it will work for you, I only tested it on my neighbor’s PC.

PS2 If you want to see the source code, open the .exe in DotPeek.

5 Likes
2

Great, this is what I have always wanted. :100: :+1:

May I ask how to use it? Are there any program placement paths and startup order requirements?

1 Like
3

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.

4

image
image1632×918 112 KB

It works well after testing, but it would be even more perfect if it could be started together with GD like DPYes. :wink:

1 Like
5

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)

console_unlock.bat  console_unlock.zip (257 Bytes):

@echo off
start "" "x64\Grim Dawn.exe"
timeout 5 >nul
start /B "" GDConsoleUnlocker.exe
  • type the following in Grim Dawn’s Steam Launch Options:

console_unlock.bat %COMMAND%

steam launch options for GDConsoleUnlocker2
steam launch options for GDConsoleUnlocker2842×601 38.9 KB

  • now the program will be launched 5 seconds (can be lowered) after Steam’s Game Start automatically

PS If you’re a non-Steam user, just modify and use console_unlock.bat to launch GD and unlocker together.

If you want to have console_unlock.bat wherever, not necessary in GD’s directory, you can use full directories.

console_unlock.bat   console_unlock.zip (353 Bytes):

@echo off
start "" "D:\SteamLibrary\steamapps\common\Grim Dawn\x64\Grim Dawn.exe" "/x64"
timeout 10 >nul
start /B "" "D:\SteamLibrary\steamapps\common\Grim Dawn\GDConsoleUnlocker.exe"

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.

1 Like
6

Default key binded to ]

2 Likes
7

I seem to understand it, thank you for your answer. :unlock:

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.

1 Like
8

If you want to have console_unlock.bat wherever, not necessary in GD’s directory, you can use full directories.

console_unlock.bat   console_unlock.zip (353 Bytes):

@echo off
start "" "D:\SteamLibrary\steamapps\common\Grim Dawn\x64\Grim Dawn.exe" "/x64"
timeout 10 >nul
start /B "" "D:\SteamLibrary\steamapps\common\Grim Dawn\GDConsoleUnlocker.exe"

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. 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.