Skip to content
Create

Generate Poetry and Lore

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

Use Poetry and Lore for a song, poem or setting text that needs a deliberate voice and cultural purpose. This walkthrough creates The Ballad of the Last Beacon, a public expedition song for the Glasswake crews.

Write for a purpose and an audience

1. Open Fantasy Lore Workshop

Start in RPG Workshop, then open the Poetry and Lore generator. This is the dedicated creative-writing route rather than a standard registry generator form.

Desktop Fantasy Lore Workshop showing its live content type, theme, mood and length controls.

Describe who performs the piece, why it exists and what must recur.

Live Fantasy Lore Workshop explanation of its iterative refinement feature.

The live product explains its Iterative Refinement feature here. The exact owner input and harbor correction are receipt-backed and are not visible in this crop.

Mobile Fantasy Lore Workshop showing the responsive title and initial controls.

Review content type, mood, theme and structural request together on mobile.

2. Specify voice, structure and public purpose

Ask for concrete maritime imagery, plain language, titled verses and a repeated chorus. The ending should honour rescue work rather than conquest. Use the system-agnostic lore control and choose a ballad or song format. Avoid secret lore when the piece is intended to be sung openly in play.

3. Keep the brief independent of campaign recording

The retained Poetry run submitted no explicit entity context. The Glasswake names and values came from the frozen brief. A thematically consistent song is not proof that the result was recorded into campaign state.

Follow the asynchronous result into the legacy page

4. Submit once and keep the job identity

Poetry completes asynchronously. Retain the original job, then verify the legacy inline result and its dedicated detail route. Do not assume the standard registry loading, export or relationship controls will appear.

5. Read content and usage together

Open The Ballad of the Last Beacon. Review content type, mood, theme, the full text, interpretation, cultural context and usage notes. Confirm that the refrain is memorable, the imagery stays maritime and the public song reveals no hidden campaign material.

Private legacy Poetry result for the Ballad of the Last Beacon showing the song and owner controls.

The legacy result is complete even though it does not use the standard registry entity layout.

6. Refine narrowly and attach owned artwork

The bespoke refine instruction changed only harbor to British English harbour, kept every other word and completed synchronously at 0 Gold. Poetry has no native automatic art, so the owned Last Beacon artwork was uploaded and associated separately. A false-negative uploader message did not justify a duplicate upload after refresh showed the Private image.

Approved owned artwork for the Ballad of the Last Beacon showing crews restoring a coastal light.

The manual image association and the bespoke text refinement are separate post-generation actions.

Use the actual sharing boundary

Poetry exposes URL copy only. It has no generic export, no Workshop Share Card, no standard relationships and no generic reroll. Copying and opening the canonical URL proves only that the route is usable under its current visibility. It does not produce a JSON file or make private material suitable for publication.

Checkpoint

Check your result

  • The legacy detail route shows The Ballad of the Last Beacon with its content, context and usage notes.
  • The bespoke refine changed only harbor to harbour and settled at 0 Gold.
  • The owned artwork is attached once to the exact Poetry result and remains Private after refresh.
  • URL copy only is verified without claiming a generic export, Share Card, relationship control or section reroll.

If something looks wrong

Troubleshooting

Symptom
The result does not look like a standard Workshop entity page.
Likely cause
Poetry uses a legacy detail and refine surface.
Next safe action
Use the controls that are mounted on the Poetry owner route rather than borrowing another entity workflow.
Symptom
The refinement changes too much.
Likely cause
The instruction may describe a general rewrite instead of one exact correction.
Next safe action
Name the exact token to change and state what must remain unchanged.
Symptom
No JSON export appears.
Likely cause
Poetry exposes URL copy only and has no generic export.
Next safe action
Verify the canonical URL and visibility boundary without claiming a downloadable file exists.