NEW V4 - AGS Actions & Conditions
AGS Actions & Conditions
The AGS Action & Condition system allows you to attach custom gameplay logic and validation rules to any Graph Node inside the Ascent Graph System (AGS).
It provides a modular way to define what happens when a node is executed and whether that node can be executed at all — all directly in Blueprint.
Actions and Conditions are fully data-driven and reusable across any type of graph:
dialogues, quests, decision trees, event flows, AI behaviors, or custom logic graphs.
1. Overview
Type | Purpose |
|---|---|
Action ( | Executes when the node activates — defines what happens. |
Condition ( | Evaluates before node activation — defines if it can happen. |
Both can be attached to any UAGSGraphNode.
Each node can have multiple Actions and multiple Conditions, making the system extremely flexible and designer-friendly.
2. Actions
What They Are
An Action is a Blueprintable object derived from UAGSAction.
It represents a single executable task triggered when its owning node becomes active.
Execution Flow
When a node starts running:
The system loops through all Actions attached to it.
For each Action, it calls the Blueprint event
ExecuteAction.The Action performs its logic — for example:
Give or remove items.
Trigger a quest update.
Play an animation, cinematic, or sound.
Set a variable or fire a custom event.
Blueprint Implementation
Create a new Blueprint class derived from
AGSAction.Override the
ExecuteActionevent.Add your gameplay logic inside that event.

You can then add this Action to any node in the graph via the details panel.
3. Conditions
What They Are
A Condition is a logic check derived from UAGSCondition.
It determines whether a node (or a transition leading to it) can execute.
Evaluation Flow
Before the system activates a node:
It iterates through all attached Conditions.
Calls
VerifyCondition()on each.If all return true, the node can run.
If any return false, the node is skipped or delayed until valid.
This makes it ideal for quest prerequisites, branching logic, or gated gameplay events.
Blueprint Implementation
Create a new Blueprint class derived from
AGSCondition.Override
VerifyConditionin Blueprint.Implement your logic — check quest states, player inventory, flags, or tags.
Example:
Event VerifyCondition
→ Check if Player has “KeyItem”
→ Return True if yes, False otherwise
If false is returned, the node’s actions will not execute.
4. Combining Conditions
AGS supports composite conditions, allowing you to combine multiple checks:
Class | Description |
|---|---|
| Returns true only if all sub-conditions are true. |
| Returns true if any sub-condition is true. |
You can nest them to create advanced logic trees such as:
“Player completed Quest A AND (has Key OR has Access Code)”
These are evaluated recursively before node execution.
5. Attaching Actions & Conditions to Nodes
All Actions and Conditions are stored as Instanced Subobjects inside the node asset.
That means no external references — everything is saved directly with the node.
In the editor:
Select a node in your AGS graph.
In the Details panel, expand Actions or Conditions.
Add new elements to the array.
Assign your Blueprint classes (created from
AGSActionorAGSCondition).Configure any exposed variables.
You can stack multiple logic layers — e.g., a node that checks multiple requirements and triggers multiple effects.