Turn Combat Configuration
he Combat Config (UACFCombatConfigDataAsset) is the single data asset that defines how a turn-based battle works: turn order strategy, phase pipeline, abilities moveset, cameras, and end-battle UI. Change the asset and you change the entire combat flow — no C++ required.
Flow: Duplicate sample Combat Config → customize your copy → assign on GameState
Before you start
Combat Config is a Primary Data Asset. The sample includes a fully configured one — duplicate it, don't modify the original.
Scheduler = who goes when. Turn Phases = what happens during each turn. They are independent.
Phases are Blueprint subclasses of
UACFTurnPhase. Each phase callsCompletePhase()when done.
Step 1 — Duplicate the sample Combat Config
Content Browser →
/AscentCombatFramework/TurnCombat/Configuration/→ select the preset Combat ConfigDuplicate (Ctrl+D)
Move/rename your copy under your game content, e.g.
Content/YourGame/TurnCombat/DA_CombatConfigOpen your copy and customize scheduler + phases there
Leave the original sample asset untouched — it's your reference if you need to compare after an update.
Step 2 — Assign your copy on the GameState
Open your GameState Blueprint
Select
ACFBattleManagerComponentSet Combat Config Data → your duplicated asset (not the sample under
/AscentCombatFramework/)
At battle start the Battle Manager loads this asset and reads everything from it.
GameState (ACFBattleManagerComponent) DA_CombatConfig (Data Asset)
┌──────────────────────────────┐ ┌─────────────────────────────┐
│ Combat Config Data ──────────┼────────────► │ SchedulerPolicyClass │
│ Initial Slots To Generate │ │ PlayerPhases / EnemyPhases │
└──────────────────────────────┘ │ InitCombatPhase / End... │
└─────────────────────────────┘Initial Slots To Generate (on the Battle Manager, default 60) controls how many turn slots the scheduler pre-builds. Raise it for ATB-style battles with long queues; lower it for simpler initiative sorting.
Step 3 — Configure the Scheduler (who goes when)
Open your Combat Config. Under ACF|Turn Scheduling you'll find two things: the initiative attribute and the scheduler object.
Initiative attribute
Turn Initiative Attribute → the GAS float attribute used to sort turns. Default is UACFTurnAttributeSet::Initiative. Point it at Speed or any other float attribute if your game uses something different.
Pick a scheduler
Scheduler Policy Class is an instanced sub-object inside the asset — not a class reference dropdown. Click the object and set its type:
Option A — UACFTurnScheduler_Default (classic turn-based)
Set Order Mode to choose the algorithm:
Plain Initiative — sort by initiative, one slot per actor. Simplest. Good for classic JRPG.
Alternating Teams — interleave party and enemy turns. Needs team labels (see note below).
Proportional (extra slots) — faster actors get multiple turns per cycle. Tune with Max Slots Per Actor, Cluster Extra Turns, Prefer Team Alternation, Max Same Team Run.
You can also call SetOrderMode at runtime to switch mid-battle.
Option B — UACFTurnScheduler_ATB (Active Time Battle)
Simulates gauge fill — initiative acts as speed. Tune:
Turn Gauge Required — how much gauge before a turn fires (default 100)
Initial Turn Queue Size — pre-generated slots at battle start (default 30)
Initial Gauge Randomness — 0 = predictable start, 1 = fully random gauges
Enforce Team Alternation / Max Consecutive Team Turns — prevent one team from dominating
Option C — Custom scheduler
Subclass UACFTurnScheduler in Blueprint or C++ and override BuildInitialTurnOrder. Assign your subclass as the instanced scheduler object. Full control over turn order logic.
Team-aware schedulers
Alternating Teams and ATB alternation need to know which actors are party vs enemy. The scheduler exposes TagCombatSides(PartyActors, EnemyActors) — call it from your Init Combat Phase (or any early phase) with the battle's party and enemy arrays. If you skip this, team-aware modes fall back to plain initiative sort.
Step 4 — Configure Turn Phases (what happens each turn)
Turn phases define the step-by-step pipeline that runs during combat. They are the main flexibility lever — reorder them, add new ones, give player and enemy completely different flows.
Open your Combat Config. There are four phase slots:
One-shot phases
Init Combat Phase — runs once when battle starts (intro camera, spawn FX, UI setup). Must eventually call FinalizeBattleStart() on the Battle Manager to enter the turn loop.
End Combat Phase — runs on player victory (rewards, victory UI). Expected to call ApplyReward(), show the widget, then FinalizeBattleEnd().
Defeat skips End Combat Phase and goes straight to the defeat widget.
Per-turn phase arrays
Player Phases — ordered list executed every player turn, top to bottom.
Enemy Phases — ordered list executed every enemy turn, top to bottom.
Player and enemy can have completely different pipelines. Example:
Player Phases: Enemy Phases:
1. Show Action Menu 1. AI Decision
2. Wait For Selection 2. Execute AI Ability
3. Execute Selected Ability 3. End Turn Cleanup
4. End Turn CleanupCreating a phase
The sample Combat Config already references preset phase Blueprints under /AscentCombatFramework/TurnCombat/. Duplicate those too — never edit the originals.
To add a custom step:
Duplicate an existing phase Blueprint from that folder into your
Content/YourGame/pathOverride
Event On Phase Starton your copyWhen done, call
Complete PhaseAdd your duplicated phase as an inline instance in Player Phases or Enemy Phases on your Combat Config copy
Each phase has access to:
Get Turn Owner— the pawn whose turn it isGet Battle Manager— the Battle Manager componentGet Turn Owner Ability Comp— the pawn's turn ability system component
Set Phase Name for UI display.
How the phase loop works
Battle starts
→ Init Combat Phase
→ ... → FinalizeBattleStart()
Turn loop:
→ AdvanceToNextTurn (picks next actor from scheduler)
→ Player Phases[] or Enemy Phases[] (based on who owns the turn)
→ Phase 0 OnPhaseStart → CompletePhase
→ Phase 1 OnPhaseStart → CompletePhase
→ ... last phase CompletePhase
→ AdvanceToNextTurn (next actor)
→ repeat
Victory → End Combat Phase → FinalizeBattleEnd()CompletePhase() on the last phase in the array automatically advances to the next turn. You don't call AdvanceToNextTurn manually from phases unless you have a special case.
The Battle Manager also exposes ReturnToPreviousPhase() and AdvanceToSpecificPhase(Phase) if you need to jump around (e.g. cancel an action and go back to the action menu).
Step 5 — Other Combat Config settings
While you're in the asset, set the remaining fields:
ACF|Turn Scheduling
Turn Initiative Attribute — already covered in Step 3
ACF|Default Camera Tags
Default Character Camera Tag — camera when focusing a combatant
Default Battle Zone Camera Tag — wide battle overview camera
ACF
Turn Abilities Moveset Tag — gameplay tag of the moveset applied to all combatants at battle start (attack, defend, items, etc.)
ACF|Turn System|End Battle
Victory End Battle Widget / Defeat End Battle Widget — UI shown when combat ends