Stagecoach

A Lumiverse Spindle extension that treats a character card's greetings (first_mes plus alternate_greetings) as an ordered sequence of story stages and soft-steers a roleplay through them.

Mechanically it is an Author's Note with a moving pointer: a single scene-change note, injected once when you advance, describing only the new stage. The value of the extension is what it withholds. A static scenario field shows the model the entire arc on every turn, so the arc is either ignored (it sits far from the generation point) or speedrun (everything in context reads as relevant now). This extension shows the model only the current stage, and reveals the next one in controlled steps.

Many cards write their alternate greetings as sequels ("two weeks later…") rather than alternatives. Picking one means a fresh chat with none of the history. Stagecoach lets you play them in any order, in one chat.

• A drawer tab with a per-chat enable toggle.

• A route builder: pick which greetings count as stages, and in what order.

• A stage-card editor (label, scene, mood) with a token count, a live preview of the injected text, and a Distill button that drafts the fields with one LLM call (model selectable).

• The standing instructions after scene and mood ("Keep the story inside this scene…") are editable from the preview, with a reset to the original wording, so you can tune them for your model.

• A current-stage selector with Advance and Back.

• Two injection modes: appended to the last user message wrapped as (OOC: …) (default; steered reliably in testing), or a system message at a chosen depth from the end of history (visible as its own Prompt Breakdown block, but some models ignore it).

• One note per stage: the first reply after you press Advance gets a scene-change note, and nothing else is injected. Stage 1 never gets a note, since the chat opened with that greeting.

• A per-stage Way in choice that shapes the arrival wording: skip time and narrate the gap (default), hard cut, or develop the transition in-scene. Models differ in how they bridge scenes; pick per transition.

• Group chats (new, please report oddities): greetings from every member are pooled in the panel, with a badge showing whose card each is. {{char}} on a card means that card's owner, regardless of the speaking card. Each card has a "Scene is with" field (blank = you) with the other members as quick picks. The scene-change note rides on the first reply after you Advance, whoever gives it; if a member speaks without a fresh message from you, the note goes in as a system message at the fallback depth instead of being appended.

1. Enable the extension for the chat.

2. Add greetings to the route in story order. Cards that write alternate greetings as "later chapters" work well; parallel alternate greetings may have a janky transition without extra prompt customization.

3. Edit each stage and press Distill (or fill the fields in by hand), then Save. Aim for about 50 tokens per card, hard cap 90. Keep {{char}} and {{user}} literal; names are substituted at injection time.

4. For each stage after the first, pick a Way in in the route list. It shapes the one note sent when you advance into that stage.

5. Play. When a scene feels finished, press Advance. The next reply opens the new stage the way you chose. Back moves without sending anything. The note button beside them shows what the next reply will get and offers the opposite: Skip this note to move on silently, or Send scene note to set the current scene up again.

Check the result in Prompt Breakdown (Extras -> Dry Run): in append mode the directive will send at the end of your latest user message; in system mode it is its own block. Either way it contains only the current stage's scene and mood.

Does not write to your character cards.

How this was made / Future Updates
Vibecoded. A human did the wanting, the design decisions, and the testing; Claude wrote the code. It was built to scratch one specific itch, and it scratches it.

Maintenance
Best-effort, no promised turnaround. Open an issue and I'll look when I can. If you want to fork it, fold it into something bigger, or take it over outright, go for it: it's MIT, and if you tell me, I'll link your fork from here or transfer the repo.

Feature requests/More Information
For the full readme, see the repository.
If you have a feature request - open an issue. Requests may be considered based on ease of implementation and my current sanity levels.