在 UE5 中构建 C++ 优先的输入管线：从 Enhanced Input 到 Gameplay Intent

动作游戏里，输入是一切手感的起点。UE5 的 Enhanced Input 已经很好用，但如果把所有逻辑都堆在角色蓝图的 IA_Jump、IA_Attack 事件里，很快会遇到两个问题：跨角色复用困难、以及输入与 gameplay 逻辑强耦合。我的做法是让 C++ 承担「解析」，蓝图只做「绑定映射」。

分层：Raw Input → Intent → Ability

核心思想是引入一个中间概念 —— Gameplay Intent。玩家按下的不是「按键」，而是表达一个意图（想跳、想攻击、想闪避）。管线分三层：

Enhanced Input 负责设备无关的 Input Action 触发；
自定义 UInputComponent 子类把 InputAction 分类成 Intent，并做缓冲 / 优先级处理；
薄蓝图层把 Intent 翻译成具体角色的 ability 调用，保持每角色绑定「数据驱动」。

自定义 InputComponent 子类

UCLASS()
class UIntentInputComponent : public UEnhancedInputComponent
{
    GENERATED_BODY()
public:
    void BindIntent(const UInputAction* Action,
                    EGameplayIntent Intent,
                    ETriggerEvent Event);
    DECLARE_MULTICAST_DELEGATE_OneParam(FOnIntent, FIntentPayload);
    FOnIntent OnIntentTriggered;
};

输入缓冲：意图带时间戳，攻击/闪避可以在一小段窗口内被「记住」；
优先级仲裁：同一帧内多个意图冲突时，在 C++ 里集中裁决；
可测试：意图是纯数据，脱离渲染也能跑单元测试。

薄蓝图层不是坏事 —— 它让策划/动画同学在不碰 C++ 的情况下重新映射每角色的「意图到技能」绑定。关键是让蓝图做配置，而不是逻辑。

小结

「C++ 优先」是把稳定、性能敏感、需要复用的解析沉到 C++，把易变、数据驱动的绑定留给蓝图。

In action games, input is where all of game feel begins. UE5's Enhanced Input is already solid, but if you pile every bit of logic into the character Blueprint's IA_Jump / IA_Attack events, you hit two problems fast: reuse across characters is painful, and input becomes tightly coupled to gameplay logic. My approach: let C++ own the parsing, and let Blueprint only do the binding.

Layering: Raw Input → Intent → Ability

The core idea is a middle concept — the Gameplay Intent. The player doesn't press a "key", they express an intent (to jump, attack, dodge). Three layers:

Enhanced Input handles device-agnostic Input Action triggers;
a custom UInputComponent subclass classifies InputActions into Intents, with buffering / priority;
a thin Blueprint layer translates Intents into a character's ability calls, keeping per-character bindings data-driven.

The custom InputComponent subclass

UCLASS()
class UIntentInputComponent : public UEnhancedInputComponent
{
    GENERATED_BODY()
public:
    void BindIntent(const UInputAction* Action,
                    EGameplayIntent Intent,
                    ETriggerEvent Event);
    DECLARE_MULTICAST_DELEGATE_OneParam(FOnIntent, FIntentPayload);
    FOnIntent OnIntentTriggered;
};

Input buffering: intents carry timestamps, so an attack/dodge can be "remembered" within a small window;
Priority arbitration: conflicting intents in one frame are resolved centrally in C++;
Testable: intents are pure data, so they run in unit tests without rendering.

The thin Blueprint layer is a feature — it lets designers re-map "intent → ability" per character without touching C++. Let Blueprint do configuration, not logic.

Takeaway

"C++-first" sinks the stable, performance-sensitive, reusable parsing into C++, and leaves the volatile, data-driven bindings to Blueprint.