Generate an Encounter

Create production-backed encounter for the Glasswake setting, then verify the saved result, artwork and supported actions.

Intermediate
12 min read
Reviewed 11 August 2026

Use the Encounter generator for one playable scene with objectives, terrain, escalation and a clear way out. This walkthrough creates The Bridge of Broken Stars, a rescue on a failing beacon bridge.

Build an encounter around an objective

1. Open the Encounter generator

Choose Encounter in RPG Workshop or open the dedicated Encounter generator. The production capture uses the Workshop form. It does not rely on a separate context-picker variant.

Desktop Encounter generator workbench showing its live brief, mode, system and party controls. — Describe what must be achieved, what changes during the scene and what failure means.

Mobile Encounter generator workbench showing the responsive title and initial controls. — Mobile keeps the same Workshop form in a single vertical sequence.

2. Describe stakes beyond defeating enemies

Ask for stranded surveyors, failing bridge spans, a fast-rising tide and safe-movement choices. Choose D&D 5e and an objective-led rescue format with scene setup, forces, terrain, objectives, escalation and resolution. This gives the generator enough structure to make protection, repair and retreat as important as combat.

3. Do not invent missing context controls

The frozen brief requested Captain Ilyra Venn, The Siltglass Leviathan, Memory Fog and Veyra's Crossing as context. The mounted Workshop form had no context selectors, so none of those were submitted as explicit entity context. Keep the names in the prose brief only when the visible form supports that input.

Follow the job and read the tactical result

4. Submit once and retain the job

Encounter generation is asynchronous. Submit one complete brief and keep its job identity until the terminal result arrives. A stopped local poll is not evidence that the server failed, and it is not permission to create a duplicate encounter.

5. Inspect objectives, terrain, stakes and retreat

Open The Bridge of Broken Stars. Check the battlefield, forces, tactics, complications, scaling, win and loss conditions, treasure hint and Read-aloud section. The retained result has visible stakes, non-combat alternatives and a retreat path, so the scene does not collapse into a single damage race.

Private Bridge of Broken Stars result showing objectives, battlefield, complications and owner controls. — Read the objective and failure state first, then test whether the forces and terrain support them.

6. Review the native scene art separately

The native image completed through its own request and association, then remained Private after refresh. Inspect the collapsing bridge, rescue focus, unwanted text and visual contradictions without treating the image as proof that every result section is correct.

Approved artwork for the Bridge of Broken Stars rescue during a storm-driven tide. — The art supports the rescue objective while the detail page supplies the playable mechanics.

Use the supported owner tools

Encounter supports editing, standard relationship controls, a Workshop Share Card, standard JSON export and generic section rerolls. The retained Read-aloud reroll displayed 1 Gold, settled 1 Gold and survived refresh. This evidence does not turn missing form context selectors into a supported feature.

Checkpoint

Check your result

The detail route shows The Bridge of Broken Stars, not another Encounter result.
Objectives, terrain, stakes and retreat options support a rescue rather than a forced fight.
The native artwork belongs to the exact Encounter and remains Private after refresh.
The Read-aloud reroll, Quest relationship and JSON export are each verified as separate post-generation actions.

If something looks wrong

Troubleshooting

Symptom: The expected campaign entity selectors are absent.
Likely cause: The reviewed Encounter route mounted the Workshop form with no context selectors.
Next safe action: Put essential public context in the brief and do not claim an explicit entity-context join.
Symptom: The result reads like a compulsory battle.
Likely cause: The brief may describe enemies without a rescue objective, alternatives or retreat path.
Next safe action: Edit the public-facing objective and outcomes, or create a distinct Encounter only when you need a new scene.
Symptom: Read-aloud needs replacing.
Likely cause: That section has a mounted paid generic reroll.
Next safe action: Read the 1 Gold quote, use it once, then refresh before accepting the change.