> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.playability.gg/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Use Mouse and Keyboard Inputs or Remap Keys

In a PlayAbility mapping, the action is what PlayAbility produces and the trigger is the physical input you use. A keyboard key can therefore produce another key, a mouse click, or a gamepad action; a mouse button or movement can do the same where that output is compatible.

## Use a physical keyboard key as a trigger

1. Open the current profile in **Mapping**.
2. Add the gamepad, keyboard, mouse, or PlayAbility action you want to produce.
3. On the action row, select **Select a trigger**.
4. Select **Create a new trigger +**.
5. Under **How do you want to control it?**, select **Keyboard**.
6. Select the input field, then press the physical key you want to use.
7. Confirm the captured key, choose an **Action Mode** if needed, and select **Save**.

To remap one key to another, add the destination key under **Add actions** > **Keyboard**, then use the original physical key as its **Keyboard** trigger. For example, make the physical F key produce R.

For WASD-style gamepad movement, add the four directional stick actions and give each one its corresponding keyboard trigger. This produces digital directional control rather than a continuously variable axis.

## Use a physical mouse button or wheel as a trigger

1. Add the action you want to produce.
2. Select **Select a trigger** and then **Create a new trigger +**.
3. Select **Mouse Button**.
4. Choose **Left Click**, **Right Click**, **Middle Click**, **Side Button 1**, **Side Button 2**, **Scroll Up**, or **Scroll Down**.
5. Choose an **Action Mode** when needed, then select **Save**.

For example, a physical left click can produce the gamepad **A Button**, or a side button can produce a keyboard key.

## Use physical mouse movement as a gamepad stick

1. In **Mapping**, select **Add actions**.
2. Under **Gamepad**, add the horizontal and vertical axes of the stick you want to control.
3. On the horizontal axis, create a **Mouse Motion** trigger.
4. Under **Which mouse axis?**, select the horizontal mouse axis.
5. Invert the direction if needed, then select **Save**.
6. On the vertical stick axis, create another **Mouse Motion** trigger and select the vertical mouse axis.
7. Invert that direction if needed, then select **Save**.
8. Tune the **Global Mouse Settings** shown in the trigger editor:
   - With **Auto Centering** on, mouse movement behaves like a self-centering joystick. Adjust **Auto Centering Sensitivity** to control how quickly it returns.
   - With **Auto Centering** off, the stick follows the mouse position relative to the screen center. Adjust **Sensitivity** to set the distance required for full stick movement.
   - With **Lock on Edge** enabled, reaching a screen edge can hold full movement in that direction.

Global Mouse Settings affect all mouse-motion mappings, so retest every profile that uses mouse movement after changing them.

## Use a mouse movement direction as a trigger

1. Add a compatible button, key, click, scroll, stick-direction, or other discrete action.
2. Create a **Mouse Motion** trigger.
3. Select **Mouse Move Up**, **Mouse Move Down**, **Mouse Move Left**, or **Mouse Move Right**.
4. Set the **Sensitivity Threshold** so ordinary small movements do not activate it accidentally.
5. Choose an **Action Mode** and select **Save**.

This directional setup is different from mapping the horizontal or vertical mouse axis to an analog gamepad stick.

## Verify the mappings

1. Confirm the intended profile says **Current profile**.
2. Make sure **Main Output** is enabled.
3. Press each key or mouse button and watch PlayAbility's live feedback.
4. Move the mouse slowly and quickly to test thresholds, direction, and centering.
5. Confirm the target game or app receives the intended output.
6. Check that the original physical input still behaves as expected.

## Troubleshooting and limitations

### A key is not captured

Select the keyboard input field before pressing the key. If it still is not captured, close software that globally intercepts the key and try another key to isolate the issue.

### A mouse side button does not respond

Confirm the device sends **Side Button 1** or **Side Button 2** to Windows. Mouse-vendor software may remap or suppress those buttons before PlayAbility receives them.

### The mouse-controlled stick drifts or does not return to center

Enable **Auto Centering** and adjust **Auto Centering Sensitivity**. If Auto Centering is off, return the pointer toward the screen center or increase the pixel **Sensitivity** range.

### A directional mouse trigger fires too often

Raise its threshold. Small normal pointer corrections can cross a low threshold, especially at high mouse sensitivity.

### Both the original and mapped input occur

Keyboard and mouse triggers do not suppress their normal Windows input by default. If you need suppression, configure the separate Windows-only **Mute input** feature under **Settings** > **Advanced** and mark only the mappings whose physical inputs should be muted.

### Mute input causes an unexpected lockout

Press **Ctrl+Shift+Alt+F12** to turn input muting off everywhere. Input suppression is a Windows-only opt-in feature and can conflict with security, anti-cheat, remote-desktop, or accessibility software.

### The target app ignores the mapped output

Confirm **Main Output** is enabled and that PlayAbility's live feedback changes. Some games read input only while focused, only detect controllers at launch, or block virtual input.

## Related articles

- [Map Inputs to Keyboard Actions](https://help.playability.gg/en/article/map-inputs-to-keyboard-actions-b9pj1d/)
- [Map Inputs to Mouse Actions](https://help.playability.gg/en/article/map-inputs-to-mouse-actions-1fkp0wl/)
- [Mute Physical Mouse and Keyboard Input on Windows](https://help.playability.gg/en/article/mute-physical-mouse-and-keyboard-input-on-windows-1kzzhxk/)