Divinity: Original Sin Enhanced Edition added controller support for the game, and with it came a new movement type: Direct control. Problem is, this is limited to gamepad mode. If you're playing with a keyboard and mouse, you're still stuck with the old-fashioned methods of point-and-click, or click-and-drag.

However, all of the new features added to make playing with a controller work is actually possible with the keyboard, and it's supported by the engine. You can bind keys to everything. It's just hidden from the Options menu.

To add WASD-style movement, you will need to configure your settings file manually, outside of the game.

You'll just be editing one config file manually. So, all you really need is a plain text editor.

It doesn't need to be anything complicated, but something with syntax highlighting is a plus.

If you only want WASD movement, that's everything you need. I'll tell you what to add.

If you're a modder, or you want to do something beyond this guide, you need the Export Tool.

The config file that you will edit doesn't show you the keybinds you want, either. To find them, I had to extract the full list of keybinds and default settings from the game data, and enter it manually. The archive to look out for will be Engine.pak .

You can bind any keyboard control to a controller button, and any gamepad control to a keyboard key.

You can find the Export Tool somewhere on the modding forums.

The file you are going to edit will be in your Documents section of your computer, where your mods, saves, and settings are stored:
\\Documents\Larian Studios\Divinity Original Sin Enhanced Edition\PlayerProfiles\<Your Profile Name>\inputconfig_p1.json

However, it may not actually exist yet. There are two ways to create this file:

Start up your game, and edit some of your controls. It doesn't matter what you edit, as long as you have something that's not the default. Simply deleting a key and leaving it blank will not work, as the game will restore it to the default keys if it's blank.

I suggest rebinding the camera control keys to something else, since that's on WASD, by default. Like I said, simply deleting them won't work. I used Shift+WASD.

Once that's done, save your settings and quit. The .json file will now exist.

Create the whole thing from scratch. I'll paste the precise text.

The file is actually just a plain text file, with the file extension changed to JSON. It is a JavaScript data file, so you need to fill the text file in a particular way.

Just create the .txt file and rename it to inputconfig_p1.json , and go to the next step.

Remember that you are changing the file extension. It's not supposed to be "inputconfig_p1.json.txt", and you'll probably get a system warning when you change it properly.

All of your custom keys will be here, so you can already see the JavaScript formatting of the dictionary. Just add this text somewhere in the middle of it all:

Paste this code, in its entirety, into the blank file.


The camera controls have also been changed - rotate with Q and E, and move it independently with Shift+WASD.

Unlike the controller, overlapping the camera control keys doesn't work for the keyboard.

The point-and-click and click-and-drag movement options will still be available in the game. Point-and-click will override anything else, and WASD will override a click-and-drag command.

Since the input on your keyboard is digital, you'll only be able to run at full speed.

You may run into a bug where you go at walking speed if you move diagonally. You can fix this easily by stopping to run in another direction, or just nudging your camera rotation.

When you are in combat, the WASD keys will cease to function. If you were playing with a controller, the analog stick at this point will change to camera control. This isn't possible on the keyboard, so you'll need to use the arrow keys, or Shift+WASD if you followed that suggestion.

This Steam Guide can be used under the Creative Commons BY-NC-SA 4.0 licence.

Please credit me as "Eiri Sanada". In addition, please include a link leading back to this Steam guide.

For a human-readable summary of the licence (which is NOT the actual licence,) go here: https://creativecommons.org/licenses/by-nc-sa/4.0/