Finish an AI roleplay story and write its epilogue

Find the story's central question

In our example, you play volunteer coordinator Nia. The AI portrays gardener Omar and community-trust representative Eve. A storm damaged the shared garden. Six weeks of work lead to a Friday inspection that decides whether it can reopen under the trust's lease.

The central question is whether Nia and the neighbors can restore a usable garden without promising more work than they can sustain. The story's repeated concern has been shared responsibility. An ending where a wealthy stranger suddenly buys everything would bypass those choices.

Writing Excuses: Writing the End discusses endings that fulfill a character's journey and earlier narrative promises. The hosts also distinguish a satisfying ending from a happy one. Use that fiction-writing advice to check which promises your ending resolves.

List concrete promises the story made. Here, the garden must receive an inspection decision, the saved seed collection must have a destination, and Nia must settle the maintenance burden with Omar. A decorative subplot about the color of the shed can stay small. The inspection cannot remain unresolved while the epilogue calls the restoration complete.

Fill a closing card from accepted earlier events

This card describes the bittersweet version that we will play in full. The facts should come from the story you actually wrote. If a needed earlier decision never occurred, play it before the ending or acknowledge that you are proposing a revision.

Blank closing card

• Whole-story question: [ ]
• Promises requiring answers: [ ]
• Earlier choices accepted: [ ]
• Established final constraints: [ ]
• Last decision left to Nia: [ ]
• Consequence if accepted: [ ]
• Relationship resolution: [ ]
• Epilogue scope: [ ]
• Limited epilogue actions and retained reader control: [ ]

Filled bittersweet closing card

• Whole-story question: Can the neighbors reopen a usable garden with a sustainable rota?
• Promises requiring answers: Inspection, seed collection, Nia and Omar's workload
• Earlier choices accepted: Nia saved seeds first, sought repair quotes late, and published a two-day volunteer rota
• Established final constraints: West beds and gate pass; east irrigation is unfinished; trust offers a west-only lease at Friday inspection
• Last decision left to Nia: Accept west-only reopening or decline the reduced lease
• Consequence if accepted: Garden reopens partly; east beds remain closed, repairs deferred
• Relationship resolution: Omar accepts two days a week; Nia stops asking him to cover every gap
• Epilogue scope: One month later, ordinary work in west beds and saved seeds; no new crisis
• Limited epilogue permission, requested after the lease decision: sorting seed labels at the west workbench, closing the tool box, and leaving the rota on the board, for this epilogue only. New decisions, dialogue and feelings remain with the reader.

The card separates a decision from a consequence. Before Nia accepts the reduced lease, the AI can explain the offer and show reactions. It should stop before choosing for her. Once you write the decision, the ending can settle its stated effects.

For this scene, send an ordinary OOC message:

Check the next reply against the closing card. The OOC guide explains how to keep writing instructions separate from the scene.

Three outcomes earned by three earlier paths

A happy, bittersweet and unsuccessful ending can all answer the same question. They need different accepted histories. Do not label the same result three ways, and do not change past choices after seeing which ending you prefer.

Happy path. In the earlier scenes, Nia asked for irrigation quotes in week one, secured materials within the story's approved budget, and recruited a four-person rota before the inspection. The repairs and gate passed on Thursday. On Friday she accepts the full garden lease and shares the signed rota with Omar. A month later, all beds are in use; Omar tends his two shifts and spends the other evenings at home. The seed collection is planted in a labeled communal row. Success follows preparation and shared labor, not a last-minute reward.

Bittersweet path. Nia protected the seeds before seeking quotes and organized a limited rota. The east work did not finish by Friday. Accepting a west-only lease keeps a garden open but closes the east beds for now. The epilogue can show the saved varieties growing in a smaller space and Omar keeping his agreed hours. The loss remains visible. Do not reopen the east section in the epilogue without a new decision and the missing work.

Unsuccessful path. Earlier, Nia postponed the quotes and left the rota as verbal promises. The east repair is unfinished, and no one has accepted recurring maintenance shifts by Friday. In this version, the trust's established condition is a written rota for any renewed lease. Nia decides not to sign a rota she cannot honestly staff. Eve declines renewal; the garden closes. Nia and Omar move the saved seed trays to an already agreed community-center storage space and mark them for next season's distribution. Their restoration goal failed. The epilogue records the closure and the kept promise to save the seeds, without presenting storage as a secretly reopened garden.

These alternatives are separate illustrative branches. The trust's rules and offers should be established before the decision in each branch. If your story has different conditions, use those rather than borrowing an outcome it has not earned.

Play one full ending before the epilogue

Here is the bittersweet branch over several turns. The final choice is still open at the beginning.

Nia sorts the seed labels at the west workbench. The unused east beds are visible beyond the fence, but the west path is open and the week's shifts are covered. Omar heads home at the agreed time. Nia closes the tool box and leaves the rota on the board for Saturday's volunteers.

The garden reopens, but only in the west section. It gives the seeds a home, confirms the reduced lease and shows shared work rather than merely declaring that the characters have learned something. The epilogue leaves a possible future repair outside this finished story's scope.

Remove a cliffhanger that reopens the story

An unsuitable final line would be:

Illustrative scene excerpt: As Nia locks the tool box, a stranger hands her a map to a hidden garden beneath the city. Everything they knew is about to change.

That launches another plot unrelated to the restoration's promises. If it appears, correct the scope rather than arguing with the stranger in character:

A corrected illustrative last beat is:

Illustrative scene excerpt: Nia closes the tool box and leaves the rota on the board. Omar has already left for home. Saturday's names remain on the rota, and the east-closure notice stays beside the gate.

The OOC correction does not erase the unwanted line from chat history. Read the next continuation and keep only the accepted ending in your own story note. If the reply introduces another plot again, restate the exact last accepted beat and scope, or stop generating after the ending you already accept.

Leave a finished record

Save the final decision, consequence and epilogue in your own notes. For the played branch, record "west-only lease signed; east closed; seeds in west; Omar Tuesday/Saturday." That lets a later story begin from an honest state if you choose to write one.

The continue-roleplay guide helps resume after a real pause. Once the narrative is closed, you can stop sending messages or leave the conversation manually. You can adapt and send the closing message in roleplay AI chat and keep the final state in your own notes.

Copy a starter or worksheet

Choose one starter or form to copy. Keep the planning record in your own notes and check the next chat reply against it.