Camera Abilities

CrimsonCore exposes the CrimsonCamera features - shoulder swap, zoom, aim/ADS, recenter, and lock-on - as input-driven Gameplay Abilities. They are granted and bound through the normal UCrimsonAbilitySet + UCrimsonInputConfig path, exactly like Jump, Sprint, and Crouch.

What ships

Seven abilities, all deriving from UCrimsonCoreGameplayAbility (or its UCrimsonGameplayAbility_BindNativeInput axis subclass). Camera is a per-player concern, so they run on the owning client only - nothing replicates except Aim's Status.Aiming activation tag.

"Active mode" means whatever camera mode is currently driving the view - third-person, aim, or lock-on, all of which derive from UCrimsonCameraMode_ThirdPerson. Shoulder and zoom are shared on UCrimsonCameraComponent, so those abilities set them once on the component and every mode reflects them. Recenter is per-mode, so it acts on GetActiveCameraMode() and no-ops gracefully when the active mode is not a third-person subclass (e.g. a pure top-down mode).

Shoulder & zoom carry-over

Shoulder and zoom live on UCrimsonCameraComponent as a single shared value, not on each mode instance - so switching modes carries your framing automatically. Releasing Aim (or breaking Lock-On) keeps your current shoulder and zoom with no save/restore. See CrimsonCamera -> Concept: Shared Camera State.

Driving the camera mode from your own ability

UCrimsonCoreGameplayAbility exposes two BlueprintCallable ways to set a camera mode while an ability is active - usable from a C++ override or a Blueprint ability graph:

void UMyAimAbility::ActivateAbility(...)
{
    Super::ActivateAbility(...);
    // Composes with the override stack; auto-popped on EndAbility.
    PushOverrideCameraMode(AimCameraMode, CrimsonGameplayTags::Camera_Mode_Aim);
}

In Blueprint, the same two pairs are nodes on any ability deriving from Crimson Core Gameplay Ability: Push Override Camera Mode / Pop Override Camera Mode and Set Camera Mode / Clear Camera Mode. Get Camera Component From Actor Info returns the avatar's camera component, and Get Active Camera Mode (on it) returns the mode currently driving the view.

Setup

• Create a data-only Blueprint subclass of each ability you want (e.g. GA_CameraAim). For Aim, set AimCameraMode to a UCrimsonCameraMode_ThirdPerson subclass with aim framing (tighter FOV / fixed shoulder); for Zoom, tune ZoomSpeed; for Shoulder, choose bToggle or a fixed TargetShoulder.
• Add them to a `UCrimsonAbilitySet` referenced by your UCrimsonPawnData::AbilitySets - the same set that grants Jump / Sprint.
• Map input in your UCrimsonInputConfig: add an AbilityInputActions row binding an IA_* to each camera input tag. Zoom expects a 1D Axis action and Switch-Target a 2D Axis action; the rest are digital.
• Add the lock-on components for the lock-on abilities: the player needs a UCrimsonLockOnComponent with a UCrimsonLockOnConfig assigned, and lockable actors need a lock-on target component. ACrimsonCharacter already carries a lock-on component plus a lockable target component (PvP); ACrimsonNPCBase carries a lockable target component. See the CrimsonCamera docs for the targeting preset + config setup.

Behavior notes