unreal-enhanced-input Checked

Set up player input in Unreal Engine 5 with Enhanced Input: Input Actions, Input Mapping Contexts, modifiers and triggers, adding the mapping context, and binding actions by ETriggerEvent. Use when wiring movement/look/jump input, creating IA_/IMC_ assets, binding in C++ or Blueprints, or when the user mentions Enhanced Input, Input Mapping Context, Input Action, IA_/IMC_, or ETriggerEvent.

Unreal Enhanced Input

Wire player input the modern UE5 way with the **Enhanced Input** system: data-driven Input

Actions and Mapping Contexts instead of the legacy Project Settings axis/action mappings.

Targets **UE 5.8** (Enhanced Input is the default; legacy input is deprecated).

Set up player input in Unreal Engine 5 with Enhanced Input: Input Actions, Input Mapping Contexts, modifiers and triggers, adding the mapping context, and binding actions by ETriggerEvent. Use when wiring movement/look/jump input, creating IA_/IMC_ assets, binding in C++ or Blueprints, or when the user mentions Enhanced Input, Input Mapping Context, Input Action, IA_/IMC_, or ETriggerEvent.

Unreal Enhanced Input

Wire player input the modern UE5 way with the **Enhanced Input** system: data-driven Input

Actions and Mapping Contexts instead of the legacy Project Settings axis/action mappings.

Targets **UE 5.8** (Enhanced Input is the default; legacy input is deprecated).

When to use

• Use when adding movement/look/jump/fire input, creating Input Action (IA_) and Input

Mapping Context (IMC_) assets, applying modifiers/triggers, adding a mapping context to a

player, or binding actions in C++ or Blueprints.

• Use when the project has IA_*/IMC_* assets or references EnhancedInput.

**When *not* to use:** engine-agnostic input *architecture* (rebinding strategy, buffering,

multi-device design) → input-systems. The Pawn/Character C++ those bindings live in →

unreal-cpp-gameplay.

Core workflow

1. **Enable the module/plugin.** Enhanced Input is on by default in UE5; for C++ binding add

"EnhancedInput" to PublicDependencyModuleNames in *.Build.cs.

2. **Create Input Actions (IA_).** Each has a **Value Type**: Digital (bool) for buttons,

Axis1D (float) for triggers, Axis2D (Vector2D) for movement/look.

3. **Create an Input Mapping Context (IMC_)** that maps keys/buttons to those actions. Use

**Modifiers** to shape raw input (Negate, Swizzle Input Axis Values, Dead Zone) — e.g. WASD

into one Axis2D needs Negate on A/S and a Swizzle on W/S. Use **Triggers** (Pressed, Hold,

Tap) to decide *when* an action fires.

4. **Add the mapping context to the player** via the EnhancedInputLocalPlayerSubsystem

(AddMappingContext(IMC, Priority)), usually in BeginPlay/possession.

5. **Bind actions** to handlers by ETriggerEvent (Triggered, Started, Completed, …) on

the EnhancedInputComponent, and read the FInputActionValue in the handler.

6. **Verify** in PIE; the Enhanced Input debugging console commands

(showdebug enhancedinput) show which actions trigger and their values.

Patterns

### 1. Add the mapping context (C++ Character)

void AMyCharacter::BeginPlay()
{
    Super::BeginPlay();
    if (APlayerController* PC = Cast<APlayerController>(GetController()))
        if (ULocalPlayer* LP = PC->GetLocalPlayer())
            if (auto* Subsystem = LP->GetSubsystem<UEnhancedInputLocalPlayerSubsystem>())
                Subsystem->AddMappingContext(DefaultMappingContext, /*Priority*/ 0);
}
// DefaultMappingContext is a UPROPERTY(EditAnywhere) TObjectPtr<UInputMappingContext>.

### 2. Bind actions and read values