CultivatingImmortality_RPGgame
UE 5.8 Project Technical Overview

S0 · Executive summary

5093 files · 20 C++ source files: a cultivation RPG with C++ base classes underneath and Blueprints carrying the presentation layer

A third-person action RPG in the cultivation (xianxia) genre — ground combat is the role's mainstay, and Light Flight (right-click) / Aerial Dash (LeftShift) provide rapid repositioning; all movement is driven by the C++ base classes (TransformCharacter + ChangliCharacter) underneath, with Blueprints carrying the presentation layer.

The project's logical density is highly concentrated on the protagonist BP_Character: 9 graphs, 39 variables, of which the input graph InputEventGraph alone has 333 nodes, and the five-hit combo graph Attack has 290 nodes — the two graphs carry about 80% of the protagonist's logic. The presentation layer is equally substantial: the VFX library Content/Effect alone accounts for 684 files, over 1/7 of the 5093 total assets; of the 421 character files, 153 are character animations alone.

S0.5 · Knowledge map

Collapsible mind map of the ten-chapter content

From the project framework to the analysis method, the skeleton of this whole document can be expanded at once and drilled through layer by layer.

S1 · Project framework

C++ base classes underneath, hair that moves, per-node readability: three decisions that define the project's character

Engine 5.8, 20 C++ source-file base classes (TransformCharacter 3161 lines, ChangliCharacter 7887 lines), legacy input system (ActionMappings, not Enhanced Input) — C++ covers the underlying logic (Light Flight / combat five-hitter / charge / shield / day-night cycle / Six Swords), Blueprints carry the presentation layer (montage / VFX / dynamic materials).

Boot configuration and input mapping

The default map is MMOGameMap_01 (an empty test scene with a directional light + height fog), game mode GameMode (GameModeBase). Input uses the legacy system rather than Enhanced Input:

Enabled plugins: KawaiiPhysics, ModelingToolsEditorMode, GameplayBehaviors, Editor Data Interface plugin (experimental); EditorUIScale is not enabled. The project root also holds a Houdini project HillStone.hip (procedural model source for mountains/rocks).

S2 · Protagonist system

One graph for input, one graph for the combo: the protagonist's two logic peaks

Among the nine graphs of BP_Character, InputEventGraph and Attack total 623 nodes — the remaining seven graphs are all auxiliary.

Parent class chain: TransformCharacter → ChangliCharacter (pure C++ base classes). 9 Blueprint graphs + underlying C++ functions, backed by 20 source files.

— Project Technical Overview · Chapter 2, 2026-10-04

ContextBP_Character covers input, combos, aiming, lightning, camera, and post-processing. Why it mattersLogic concentrated in a single Blueprint means any change must be located within these 9 graphs — the node-density chart is that map.

Five-hit combo: montage selection + state management via notification frames

ComboAttack breaks Combo1~Combo5 into five animation montage segments from the ST_AnimMontage struct and plays them per ComboNumber; an input inside the ReadyToCombo window extends the combo, otherwise ResetAttack zeroes it. Attack state is driven by animation notifications: ComboAttackNotify starts the attack (IsAttacking=true, disables face tracking, speed limit 300), ResetAttackNotify exits and restores HoverFlySpeed. Combos simultaneously generate the BezierBulletEffect Bézier-tracking bullet and the Attack03/05 effects.

Aiming and lightning

Right-click CE_AimStart enters aiming (camera closes in, UW_Aim crosshair shows), CE_AimTrace periodically scans enemies into AimTargetArray and assigns lock targets. Lightning is a charged chain attack: after ChargeCompleted it links across multiple enemies in EnemyArray (branch _Branch / bounce _Bounce), UW_LightningTrace draws the connection line UI, and the post-processing material switches during the skill. The 39 variables are organized in six groups: movement / combo / camera / aim / lightning / post-processing.

S3 · Motion system BPC_MotionComponent

Two flight parameter sets, one lean amount: the motion component does only three things

An ActorComponent attached to BP_Character: 27 variables, 10 functions, managing dual-speed-state flight, Lean tilt, and the camera spring arm.

The dual speed states switch via SetSprintEvent / SetAimingEvent; while IsAiming, aiming flight parameters apply. Tick records the velocity direction of the previous and current frames, and YawVelocityDifference / PitchVelocityDifference compute the Lean tilt in real time, driving body tilt via the animation Blueprint. The camera spring-arm composition graph (61 nodes) smooths interpolation per TargetSocketOffset / TargetLength / InterpSpeed: closing in when aiming, pulling back when sprinting. HitEvent handles interrupting the current motion state on hit.

S4 · Animation system CharacterAnimationBlueprint

Four states, six transitions: a state machine with no "ground" state

The data flow is unidirectional and clear — BP_Character / BPC compute the state variables, and CharacterAnimationBlueprint reads them every frame to drive the skeleton pose.

AnimGraph 26 nodes + EventGraph 127 nodes. Main pose pipeline: the Default state machine is cached to LocalMotion → gaze blending in HeadLookAtNode (blends in when IsLookAt and InRange) → Montage Slot (combo injection point) → aim pose blending in AimPoseNode (blends in when IsAim) → 6-level KawaiiPhysics chain → output pose. The EventGraph is driven by BlueprintUpdateAnimation, where SetNextSection appears 6 times — the linking of combo montage segments and combo smoothness all rely on it.

Character asset support (CharacterSkeletalMesh, 230 files): skeletal mesh + physics assets, IKRig + IKRetargeter (MagicalAnimSet animations retargeted onto the character's skeleton), 153 animations (Motion / Self / Retargeter ≈100 / UseMontage 13), 5 blending spaces, 15 materials, 48 textures.

S5 · Effects and projectiles

The bullets come in only two varieties: straight, and Bézier trackers that bend three times

Of the 684-file VFX library, the logic that actually "moves" is concentrated in four child classes of the EF_BaseEffect inheritance tree.

BezierBulletEffect is the technical peak of the projectile system: 105-node EventGraph + 3 functions. TraceTarget (27 nodes) searches for enemies into EnemyArray; CE_BezierMove is driven by TimelineHasEnemy and computes Bézier-curve tracking on the target via three control points 3SpotPosition; with no enemy, it degrades to a straight line / scatter. On hit, ApplyDamage (carrying DamageType) → spawn hit effect → stop the dual time axis → destroy.

S6 · Enemy system EnemyBlueprint

Patrol, take damage, explode, respawn: the drone's complete closed loop

EventGraph's 76 nodes manage patrol, the Damage graph's 140 nodes manage being hit and death — the death feedback is twice as thick as the patrol logic.

The patrol AI uses timers to refresh random patrol target points, and TraceLand probes downward for the ground to prevent crashes. Taking hits goes through AnyDamage: record hit direction and position → reduce HP → dynamic material hit-coloring driven by the ColorDamage curve. Death CE_Death is a combination: explosion effect + EnemyBlueprintDestroy debris (GeometryCollection chaotic breakage) + FieldSystem force-field shockwave + EnemyExplosionEffect camera shake, and finally CE_Reborn respawns at the spawn point, completing the loop.

S7 · Damage, camera, UI

One interface unifies hits; four kinds of notifies dispatch the presentation

Attackers carry Sword / Lightning damage types per skill; BPI_Damage delivers them uniformly, and the enemy side responds per type with different hit reactions.

S8 · Full combat chain

Connecting the previous seven chapters: one attack runs the full path from keypress to shatter

The main chain runs every frame; the basic attack / aim / lightning skill chains merge at the damage point, and the hit-reaction chain closes on the enemy side.

Structurally, GameMode hangs only two subtrees: the protagonist BP_Character (with the BPC motion component, animation instance AB, montage struct, combat UI and bullet spawn) and the enemy EnemyBlueprint (patrol AI, Damage graph, death breakage chain). All combat complexity happens between these two trees.

S9 · Assets

The distribution across 5093 files: a sixth in effects, a fifth in characters, a sixth in the animation pack

VFX library 684, characters 421, MagicalAnimSet pack 152, core gameplay Blueprints 32, scene assets 25.

Core gameplay Blueprints number only 32 files, yet they define all the rules; what actually occupies the volume are the "looks and motion" assets — effects, animations, textures. There are only two maps: MMOGameMap_01, the default boot map (directional light + height fog empty scene), and the Showcase demo level that ships with the animation pack.

S10 · Appendix

How this analysis was made

Two data paths: offline binary parsing yields file-level facts; live editor reads yield node-level facts.

S11 · Feature studies: pilot

Character flight and dash: a complete pre-study implementation

The project is not pure Blueprint: the protagonist's base is driven by C++ base classes (TransformCharacter Light Flight, ChangliCharacter combat, TimeOfDayManager day-night, SwordQOrbitManager Six Swords), with much of the presentation-layer logic still living in Blueprint graphs.

The current character (BP_Character) is driven in the base by TransformCharacter (C++, 3161-line .cpp) for form transforms: right-click Light Flight into a translucent high-speed state (MPC dissolve transition), left-click basic-attack five-hitter, hold for a charged sword burst, LeftShift aerial dash, Q-key Six Swords orbit, E-key shield, right-click aiming. Blueprint graphs carry the presentation layer (montage, VFX, dynamic materials); C++ handles the base timing and guards (V171 Light Flight silent-exit triple fix as evidence of the iteration).