Actions Reference

All built-in actions for scenes and choices.

Core Actions

property Examples

// String format (= set, > add, < subtract)
{ property: "gold>100" }           // add 100 to gold
{ property: "score=0, lives<1" }   // set score to 0, subtract 1 from lives

// Object format (for setting complex values)
{ property: { settings: { volume: 80, theme: "dark" } } }

Dungeon Actions

Scene Params

intro

Add {intro: true} to the first paragraph of a scene. On the first visit, column 1 plays normally. On any subsequent visit, the engine skips column 1 and plays column 2 instead.

Example (DryadScript):

#npc~talk{intro: true}
1
%
The old man looks up from his desk.

old_man: Ah, a visitor. I am Gareth, the keeper of this archive.

old_man: What brings you here?
%
Gareth nods as you approach.

old_man: Back again? What do you need?

Column 1 (before %) plays on first visit. Column 2 (after %) plays on every subsequent visit. Both share the same choices below.

Note: Column 2 must exist. If missing, the engine logs an error.

Character Actions

Targeted-spec syntax (status, skin_layer, item_slot, ability)

Each action takes a string of the form targetId->item & item & ..., targetId->!item, ...:

• Comma separates per-target groups.
• Within a group, & separates items.
• Items prefixed with ! are removed; bare items are added.

{ status: "alice->blessed & focused, bob->!cursed" }
{ skin_layer: "mc->armor_dirty, mc->!armor_clean" }
{ item_slot: "alice->extra_ring, bob->!ring_3" }

Item Actions

equip

Equip and unequip items using real character ids and item template ids (no uids). Comma separates specs; two spec shapes:

• Targeted (char -> payload & payload): & separates payloads; a payload is itemId to equip or !itemId to unequip. char.slot_type targets a specific slot type (an equip fills its first empty slot, else the first; an !itemId is restricted to that type).
• Clear (!char / !char.slot_type, no arrow): !char.slot_type unequips every occupied slot of that type; !char clears all of the character's equipment.

slot_type is the slot's id from Item Slots (e.g. outfit_ordelia), not a per-character instance name. On equip, if no matching instance exists in the character's inventory one is created from the template and the item.added flash shows (same as add_item); equipping an instance already in inventory stays silent. Invalid ids/slots log a console warning and skip that spec — the scene continues.

{ equip: "ordelia -> armor1 & ring1" }        // equip both (auto slot)
{ equip: "ordelia.trinket_ordelia -> ring1" } // equip into a slot type
{ equip: "ordelia -> !armor1" }               // unequip by item id
{ equip: "!ordelia.outfit_ordelia" }          // clear a slot type
{ equip: "!ordelia" }                         // clear all equipment

equip vs equip_item/unequip_item: prefer equip for scripting — it uses stable ids. equip_item/unequip_item act on the active item (its uid) and are mostly internal UI plumbing; { equip_item: true } / { unequip_item: true } stay useful inside active-item flows (e.g. the tutorial's equip/unequip cancel handling).