CrimsonInput · Lesson 5 of 8
Author the Input Config
Before you start
- Completed: Use the Crimson Input Component
Chapters
1. Create the asset
Content Browser → right-click → Miscellaneous → Data Asset → pick CrimsonInputConfig. This is the pairing table between actions and tags.
2. Fill the three lists
| List | For | Example entry |
| Native Input Actions | Movement, camera — bound to C++/BP callbacks | IA_Move → InputTag.Move |
| Ability Input Actions | GAS ability activation | IA_Ability1 → InputTag.Ability.1 |
| UI Input Actions | CommonUI actions (confirm/back) | IA_UI_Confirm → InputTag.UI.Confirm |
You own the tag hierarchy
The plugin ships no input tags — define your own
InputTag.* family in Project Settings → Gameplay Tags. That keeps your scheme yours; the plugin only agrees on the pattern.Read-side helpers exist for all three lists — FindNativeInputActionForTag, FindAbilityInputActionForTag, FindUIInputActionForTag — all callable from Blueprint.