CrimsonInput · Lesson 4 of 8
Use the Crimson Input Component
Before you start
- Completed: Create Actions & a Mapping Context
Chapters
Why a custom component
CrimsonInputComponent extends Enhanced Input's component with the tag-based binders (BindNativeAction, BindAbilityActions) you'll use two lessons from now. Make it the project default in Config/DefaultInput.ini:
[/Script/EnhancedInput.EnhancedInputDeveloperSettings]DefaultInputComponentClass=/Script/CrimsonInput.CrimsonInputComponent
Or set it per-pawn instead of project-wide:
// In your pawn's constructorInputComponentClass = UCrimsonInputComponent::StaticClass();
Blueprint projects
Blueprint-only projects still set the ini line (or ask a teammate to) — but they bind input with regular Enhanced Input Action events, so nothing else changes for them.