Implementing Modular Controls with Unreal Engine 5 Enhanced Input

The Problem: Rigid Input Mapping

Legacy input systems in Unreal Engine rely on a global project settings list. This creates a monolithic input map where every possible action from jumping on foot to firing a turret in a vehicle exists in one list. Managing this becomes unsustainable as project complexity grows, leading to conflicts where one key must perform different actions depending on game state.

The Enhanced Input System solves this by decoupling the action what happens from the mapping which key triggers it. By using Input Mapping Contexts, you can swap entire control schemes at runtime based on the player's current state.

Prerequisites

• Unreal Engine 5.1 or later.
• The Enhanced Input plugin enabled in Edit Plugins Search Enhanced Input.
• A Character or Pawn class configured for player control.

Step 1: Defining the Action Assets

First define the Input Action. An Input Action is a data asset that represents a conceptual action without any assigned key.

1. Right click in the Content Browser Input Input Action.
2. Create IA_Move and IA_Jump.
3. Open IA_Move and set the Value Type to Axis2D Vector2D. This allows for X and Y movement.
4. Open IA_Jump and set the Value Type to Digital bool.

Step 2: Creating the Mapping Context

The Input Mapping Context maps raw hardware keys to the Input Actions created above. This is where you define modifiers to handle axis inversion or deadzones.

1. Right click Input Input Mapping Context. Name it IMC_Default.
2. Add a mapping for IA_Jump and assign the Space Bar.
3. Add a mapping for IA_Move. Assign the W key.
4. To handle the S key for backward movement, add another mapping for IA_Move, assign S, and add a Modifier Negate. This flips the axis value from 1.0 to -1.0.
5. To handle D for Right, add IA_Move, assign D, and add the Swizzle Input Axis Values modifier.

Step 3: Binding Logic to the Character

The character must be told which functions to execute when an Input Action is triggered. This is handled in the SetupPlayerInputComponent override.

C++ Implementation

// In your Character.cpp
void AMyCharacter::SetupPlayerInputComponent(UInputComponent* PlayerInputComponent)
{
    Super::SetupPlayerInputComponent(PlayerInputComponent);

    if (UEnhancedInputComponent* EnhancedInputComponent = Cast<UEnhancedInputComponent>(PlayerInputComponent))
    {
        EnhancedInputComponent->BindAction(JumpAction, ETriggerEvent::Started, this, &AMyCharacter::Jump);
        EnhancedInputComponent->BindAction(MoveAction, ETriggerEvent::Triggered, this, &AMyCharacter::Move);
    }
}

Blueprint Implementation

In the Event Graph use the EnhancedActionEvents. Search for the specific IA_Jump event. Connect the Started pin to your jump logic and the Completed pin to stop any sustained actions.

Step 4: Activating the Context at Runtime

Defining the Input Mapping Context is not enough. It must be added to the Local Player Subsystem to become active. This usually happens in BeginPlay.

Execution Location Character Class BeginPlay. Required Permissions Access to Local Player Controller. Risk If the Local Player Subsystem is null e.g. on a dedicated server calling this will cause a crash. Always use a null check.

1. Get the Player Controller.
2. Get the Enhanced Input Local Player Subsystem from the controller.
3. Call AddMappingContext passing in your IMC_Default asset and a priority e.g. 0.

Comparison: Legacy vs Enhanced Input

Feature	Legacy Input	Enhanced Input
Configuration	Project Settings Global	Data Assets Modular
Runtime Swapping	Difficult Manual logic	Native Add Remove IMC
Axis Modification	Hardcoded in logic	Modifiers Negate Swizzle
Trigger Logic	Tick based or Event based	Trigger States Started Triggered Completed

Verification and Diagnostics

To verify the system is functioning use the following checks.

• Log Check Add a UE_LOG or Print String inside the bound function. If the log does not fire verify the Input Mapping Context was added to the Subsystem.
• Input Debugging Use the console command showdebug enhancedinput while the game is running to see which contexts are active and which actions are currently receiving values.

Rollback and State Cleanup

If you switch contexts e.g. exiting a vehicle you must remove the previous context to prevent input overlap.

1. Access the Enhanced Input Local Player Subsystem.
2. Call RemoveMappingContext and pass the Input Mapping Context you wish to deactivate.