The Tag-Driven Layer

The idea

CrimsonInput is a thin, tag-driven layer over Enhanced Input. One CrimsonInputConfig data asset pairs each InputAction with a gameplay tag; your code then binds tags to callbacks or GAS abilities instead of referencing action assets directly. Swap the config and the whole control scheme swaps with it.

On top of that it adds what Enhanced Input leaves out: settings-driven modifiers (deadzone, gamepad sensitivity, aim inversion), rebindable modifier-key chords, a press-and-hold trigger, and CommonUI action wiring.

Dependencies

Needs CrimsonCommon plus engine plugins EnhancedInput, GameplayAbilities, and CommonUI. Notably it has no CrimsonAbilitySystem dependency — GAS input goes through Epic's IAbilitySystemInterface, so it works with any ability system.

What we'll build

1. Enable the plugin
2. Create actions and a mapping context
3. Switch to the Crimson Input Component
4. Author the input config with your InputTag hierarchy
5. Bind the actions and apply the context
6. Add chords and user settings