Wire it into flows and scripts

Beyond the built-in loop, you can drive the game from your flows and scripts. This is how the RPG stops being a separate feature and starts reacting to everything else on your channel.

With nodes

The RPG node family lets a flow roll a loot table, grant or use an item, run an encounter, explore, and read a character. Wire those into any trigger: a channel-point redeem that runs an encounter, a raid that showers the raiders with loot, a subscription that grants an item. Browse the catalog on the nodes page; the RPG nodes appear there once they ship.

With scripts

If you prefer code, the same actions are available through the ctx.Rpg surface in a script, so authors who script get the same reach as authors who wire nodes. See ctx.Rpg in the glossary.

Let an encounter be a flow

The tightest integration is pointing an encounter at a flow, as the encounters step mentioned. The flow becomes the fight, so a boss can send messages, branch on the roll, or trigger overlays, all from one encounter a viewer starts with a single command.