You cannot reliably rebind arrow keys in Witchspire using the in-game settings because many controls are hardcoded and the menus are frequently bugged. The only effective solutions are to either directly edit the game's Input.ini configuration file or use a third-party tool like AutoHotkey to force new key assignments at the system level. This guide will walk you through both methods, providing a permanent fix for one of the game's most frustrating oversights.

Players have reported since Witchspire's Early Access launch that the keybinding options are incomplete. Changes sometimes fail to save, or worse, the keys you want to use (especially arrows) are locked to specific functions like camera movement or UI navigation. This is a massive barrier for left-handed players who use the arrow keys for movement, or anyone using a non-standard keyboard layout. While the developers have acknowledged some issues, waiting for a patch isn't necessary when you can fix it yourself in about ten minutes.

Why Can't I Just Change It In the Menu?

The short answer is developer oversight. In many games, especially those in Early Access, certain fundamental controls are "hardcoded" during development. This means the key assignment isn't read from a settings menu but is baked directly into the game's code. In Witchspire, this primarily affects the arrow keys (locked to camera) and WASD (locked to movement), creating conflicts if you try to reassign one for the other's function.

This isn't just an inconvenience; it's a major accessibility failure. Modern game design standards call for full key remapping to accommodate all players. When a game forces a specific control scheme, it excludes a significant portion of its potential audience. The methods below are workarounds for a problem that shouldn't exist, but they are highly effective.

The Primary Fix: Editing the Input.ini File

This is the most direct and cleanest way to change Witchspire's controls. You'll be telling the game engine itself what the keys should do, overriding the hardcoded defaults. It looks technical, but it's just a matter of finding a text file and changing a few lines.

Step 1: Locate Your Input.ini File

Witchspire, like many games built on Unreal Engine, stores its configuration files in your user AppData folder, not the main installation directory. This is to keep your personal settings separate from the core game files.

  1. Press the Windows Key + R to open the Run dialog.
  2. Copy and paste the following path and press Enter: %LOCALAPPDATA%\Witchspire\Saved\Config\WindowsNoEditor\
  3. This will open a folder containing several configuration files. The one you need is Input.ini.

If you can't find it there, the developers may have changed the path. In that case, you can also try searching your PC for the Witchspire folder within %LOCALAPPDATA% or checking the game's installation folder under steamapps\common.

Step 2: Back Up Your File (Crucial!)

Before you edit anything, create a copy of Input.ini. Right-click the file, select "Copy," then paste it in the same folder. It will be named Input - Copy.ini. If you make a mistake and the game's controls stop working, you can delete your modified file and rename the copy back to Input.ini to restore the defaults.

Step 3: Edit the Key Mappings

Open Input.ini with a simple text editor like Notepad or Notepad++. You will see sections with headers in brackets, like [/Script/Engine.InputSettings]. The two most important sections for rebinding are ActionMappings and AxisMappings.

  • ActionMappings: These are for single-press actions like Jump, Interact, Use Ability, or Open Menu. They follow the format: ActionMappings=(ActionName="<Action>",Key=<KeyName>,bShift=False,bCtrl=False,bAlt=False,bCmd=False).
  • AxisMappings: These are for actions that have a scale, like moving forward/backward or looking up/down. They follow the format: AxisMappings=(AxisName="<Axis>",Key=<KeyName>,Scale=<Value>).

Let's say you want to rebind the "Interact" function from F to RightShift. You would find the line that looks like this:

ActionMappings=(ActionName="Interact",Key=F,bShift=False,bCtrl=False,bAlt=False,bCmd=False)

And change it to:

ActionMappings=(ActionName="Interact",Key=RightShift,bShift=False,bCtrl=False,bAlt=False,bCmd=False)

To remap movement from WASD to the arrow keys, you'll need to edit the AxisMappings. You would look for the MoveForward and MoveRight axes and change the Key values from W, S, A, D to Up, Down, Left, Right respectively. You might also need to find where Up, Down, Left, Right are being used for camera control and swap them or assign them to unused keys.

After making your changes, save the file. Right-click Input.ini, go to Properties, and check the "Read-only" box. This can sometimes prevent the game from overwriting your custom settings when it launches. If a future game patch changes the controls, you may need to uncheck this, let the game update the file, and then re-apply your custom changes.

The Power User's Fix: An AutoHotkey Script

If editing config files feels too risky or you want a solution that works across multiple games, AutoHotkey (AHK) is your best friend. AHK is a free, powerful scripting tool that can remap keys, automate tasks, and create complex macros. For our purposes, we just need a simple script to tell Windows, "When I press this key, pretend I pressed that key instead."

This method is excellent because it doesn't modify any game files, making it immune to being patched over. The script is only active when you run it.

Step 1: Install AutoHotkey

Go to the official AutoHotkey website (autohotkey.com), download the latest version, and install it. It's a lightweight and safe application used by millions.

Step 2: Create Your Remapping Script

Once AHK is installed, right-click on your desktop, go to New, and select "AutoHotkey Script." Name the file something memorable, like WitchspireKeys.ahk.

Right-click the new file and select "Edit Script." This will open it in Notepad. Delete any existing text and paste in the following code. This example script makes the arrow keys behave like WASD:

#NoEnv
SendMode Input
SetWorkingDir %A_ScriptDir%

; Only run this script when Witchspire is the active window.
#IfWinActive, ahk_exe Witchspire.exe

; Remap Arrow Keys to WASD
Up::w
Down::s
Left::a
Right::d

; You can add more remaps here. For example, to make Right Ctrl act as F:
RCtrl::f

; This line is needed to end the context-sensitive section.
#IfWinActive

The syntax is simple: OriginalKey::NewKey. The #IfWinActive line is a useful addition that ensures these key remaps only apply when the Witchspire game window is active. You'll need to confirm the game's process name in Task Manager; it's likely Witchspire.exe or Witchspire-Win64-Shipping.exe.

Step 3: Run the Script

Save the script file. Now, whenever you want to play Witchspire, just double-click the WitchspireKeys.ahk file on your desktop. You'll see a green 'H' icon in your system tray, indicating the script is running. Launch the game, and your keys will be remapped. To stop the script, right-click the icon in the system tray and choose "Exit."

Frequently Asked Questions

Will editing config files or using AHK get me banned?

No. These methods are for client-side control changes only. They don't interact with the game's memory, network traffic, or anything that anti-cheat systems look for. Rebinding keys is a basic accessibility feature, and these methods are simply enabling it where the developers have failed to. You are perfectly safe.

Will game updates break my custom keybinds?

Possibly. If you edited the Input.ini file, a major game update could reset it. This is why you should keep a backup of your customized file. If you set it to "Read-only," it might survive, but sometimes it's better to let the game create a new file and then copy your changes back into it. The AutoHotkey method will not be affected by game updates at all.

Can I use this to remap controller buttons?

Not directly. The Input.ini file is primarily for keyboard and mouse bindings. For remapping a controller, your best bet is to use Steam's own Controller Configuration tool. In your Steam Library, right-click Witchspire, go to Properties > Controller, and you can create a custom layout that remaps any button, stick, or trigger.

A Final Word

Fighting with a game's controls is the fastest way to ruin the experience. While it's disappointing that Witchspire launched without robust keybinding options, the solutions are straightforward. Editing the Input.ini file is the most native and integrated approach, while AutoHotkey offers a more powerful, external solution. Choose the method you're most comfortable with, and you can finally set up your controls in a way that makes sense for you, allowing you to focus on exploring the world of Witchspire instead of fighting your keyboard.