Selected data stores instances (e.g. combatants, items or objects) and can be used for all kinds of custom systems.
Selected data isn’t saved in save games.
What is Selected Data? #
Selected data is similar to variables – but instead of values, it stores references to instances.
Selected data consists of 2 parts:
- Key
The key (or name) of the data is used to identify it.
This is always a string value (text). - Data
The stored data, this can be a single thing or multiple things.
Data Key #
The data key is a string value (text), each key can have one or more data assigned to it.
You can define a data key at any time and any place in your project. They don’t need to be pre-defined to be available.
Data #
The data stored in a data key can be anything that is an instance of something, e.g.:
- a combatant or multiple combatants
- an item, equipment, etc. or multiple items, equipment, etc.
- an object instance or multiple objects
- a component or multiple components
- a variable handler or multiple variable handlers (a variable handler stores all variables of an origin, e.g. global variables)
- a combination of different things, e.g. a combatant, an object, 2 items and a variable handler
E.g. a combatant, item, equipment and object are stored in the local selected data key list.
Variable nodes using the Selected variable origin will have access to the object variables of the combatant and object (if used) and the item and equipment variables of the item and equipment.
Data Origin #
The origin of selected data defines where it’s stored and how it can be accessed. There are 3 different data origins – when dealing with selected data (e.g. changing it, checking it or using it’s data), you’ll always need to select the origin.
Local #
Local selected data is only available in a local context, e.g. a playing schematic or calculating formula. They’re best used for short lived content, like a combatant needed for later nodes within a running schematic.
A crucial mechanic is sharing local selected data between actions, schematics and formulas (or schematics and other schematics started by them) that are started/used by each other – this allows passing on information and doing different things depending on where they’re started from.
E.g. an ability being animated by schematics will share local selected data with all it’s schematics and all it’s formulas being used for status change calculations.
Changes made in a schematic will be available to any schematic or formula used afterwards.
Additionally, the ability instance itself will be available as local selected data via the data key action.
Global #
Global selected data is available everywhere and at any time – it’s persistent in the running game, i.e. they’ll be available in all machines/schematics, formulas and other parts of ORK.
However, if a referenced content (e.g. an object) has already been destroyed, it’ll no longer be accessible.
Since global selected data is persistent, you can use them to store information that needs to be remembered for longer periods of time, like remembering player group combatants for a custom game mechanic.
Object #
Object selected data is bound to objects in your scene by an Object ID. Like global selected data, it’s available everywhere and at any time.
However, object selected data doesn’t require an object in the scene and can be accessed by their Object ID instead. This e.g. allows to set up scene-based selected data by using the scene name as object ID.
Object selected can be accessed either via an object or the object ID.
Object Variables Component #
Binding object selected data to an object is done by adding an Object Variables component to the object. When objects share the same Object ID in their object variable components, they’ll share the same selected data (alongside variables).
Optionally, the component can be set to be used in a local mode by enabling Local Variables. When used as local selected data, the object selected data is only available as long as the object exists and can’t be shared between objects.
Selecting Data #
Data is selected through the selected data nodes in schematics, formulas or battle AIs.
There are different nodes to select different kinds of data, e.g. combatants (Select Combatant), objects (Select Objects), inventory content (Select Item) or variable handlers (Select Variable Handlers).
Using Selected Data #
Selected data can be used in various other nodes in schematics and formulas.
The Selected variable origin allows using variable handlers that are stored in selected data, e.g. attached to stored combatants or objects (Object Variables component) or directly stored in the data.
Additionally, object selections in schematics can use objects stored in selected data. Objects can come from objects directly, or be the objects of combatants or components.
Action Key #
The data key action used in local selected data will often contain context related data.
E.g. abilities and items using schematics or formulas will automatically be available as local selected data via the data key action.
This allows access to their variables (Selected variable origin) or use them for other things.
Animating UI #
Using schematics to animate opening or closing your UI boxes and HUDs makes use of selected data.
The UI that should be animated is automatically available as local selected data via the data key ui. This can be used in UI nodes to e.g. change it’s color (Change UI Color) or position offset (Change UI Offset).

