Skip to content

A party that splits up stays split: who is where is kept, and each group gets its own passage - #1075

Open
Lebbitheplow wants to merge 1 commit into
mainfrom
party-split-state
Open

Lebbitheplow wants to merge 1 commit into
mainfrom
party-split-state

Conversation

@Lebbitheplow

Copy link
Copy Markdown
Owner

Fixes #951.

A table split up and the GM folded both groups into one passage. A split existed only as a moment (issue 563): one sentence in move_party's result, after which nothing knew who stood where, so the next turn read every player's line as one scene. This keeps the split as state and has the story follow one group at a time, the way a GM cuts between rooms.

What changes at the table

  • The split is kept. move_party naming who goes leaves the rest as a group elsewhere, on the party record (party.away). It ends when nobody is elsewhere: going where the others wait joins them.
  • One passage a group. A turn answers the lines of those in the scene. A move by someone elsewhere is held out of that prompt, and once those the scene is with have had their reply the server cuts to the group that has waited longest, with a line the table reads ("Meanwhile, at The Docks: Bram and Tovin."). A group whose move has already sat through one reply goes next, so one busy room does not starve the other.
  • A call reaches only who is in the scene. A call that names someone elsewhere is refused with the way through, at the door the fight's own "not at this fight" rule uses. Bookkeeping that reaches nowhere (awards, the sheet, a whisper, a question to a player) is exempt.
  • "Everyone" is everyone here. A fight leaves those elsewhere out, as absent does, and an initiative roll still brings one in. A rest, a group check, what there is to notice, a hoard, a road and a scene board take the characters in the scene. Whoever travels with the party stays with whoever is left where they were.
  • A night is one night. A rest that fits in the time the scene was away from a group was taken then, and moves no clock.
  • Players see it. The scene line names who the story is with, the party panel and the rail mark who is elsewhere and where, a player whose own character is elsewhere reads why the story did not answer at once, and the console's "Who goes" says what naming someone elsewhere does. French strings included.

Small narrators

A 20B local model rarely says who goes. In twelve live plays where one character slipped off alone it passed characterIds once, and in four it called no move_party at all. Saying the rule again in the tool's result changed nothing.

So the players' own words are read once as the turn opens, by the utility model: who does not go, and where the others are going. Each name comes with the words that say so, and those words must be in what the players wrote. Then:

  • the storyteller is told in GAME STATE, with the exact call;
  • its move_party of "everyone" is read as a move of those who go;
  • a turn that still records nothing is put right by the server, at the place the players named.

With it, three of three full plays of the new split scenario passed every step on that model (the split recorded, a passage for each group, the party together again), and a play of the town scenario split nobody.

The read is asked only where it can matter: the table's outcome check on, the built-in storyteller (an agent program names who goes itself), no fight, two or more of the party in the scene, and a line that is not only speech.

What it costs

  • Tools: nothing. No new tool, and the one description that changed got shorter (the 64K tool budget has no room).
  • GAME STATE: about 80 to 100 tokens while the party is split (a test holds it under 110), none while it is together.
  • Time: the read took about 1 to 2 seconds a turn on the test model, on the turns it is asked. Two groups acting in one beat are two storyteller turns.

Limits

  • A fight holds the scene: those elsewhere wait for it to end, or roll initiative to arrive.
  • Players who part ways without naming a place, with a narrator that records nothing, stay together on the record.
  • The clock is shared. Only rests are counted as taken "meanwhile"; a journey one group makes still passes time for everyone.

How it was checked

  • scripts/test-party-split.mjs (30, pure): the moves, the lines a turn reads, when the scene cuts, what is said, what a call may reach, the read's prompt and its parsing.
  • scripts/test-enforce-party-split.mjs (13, through the engine with a scripted model): the stored split, a prompt with none of the other group's lines, the follow-up passage after a cut, the refusal, fights, rests, followers, the read and the server's own move.
  • The older split checks in test-enforce-conscience-563 pass unchanged.
  • scripts/browser/scenarios/100-party-split.mjs now reads the scene line and the marks, in both themes, on the website and in the app shell, desktop and phone.
  • scripts/smoke-local.mjs --scenario split is the live check, five beats: arrive, part ways, act alone, both act at once, come back together.

Screenshots

Night Day
Website, desktop
App, desktop
Website, phone
App, phone

Checks

  • npm run lint, npm test and npm run build pass, and the change has a test that fails without it.
  • Anything a player sees has screenshots below: the website and the app, day and night themes, phone width.
  • No hostnames, IP addresses, logs, keys, .env files or players' names in the code, the tests or this description.

Settings, options and controls

  • This adds no new setting, toggle, option or other control.

No client change is needed: the apps compile these screens from the server.

🤖 Generated with Claude Code

…e story follows one group at a time with a passage for each, and the players' own words are read for who stays behind

A table split up and the GM folded both groups into one passage (issue 951). The split was one sentence in move_party's result: the next turn knew nothing of it.

The party record now keeps the groups that are not in the scene. A turn answers the lines of those in the scene; a move by someone elsewhere waits, and the scene cuts to them once those it is with have had their reply, with a line the table reads ("Meanwhile, at The Docks: Bram and Tovin."). A call reaches only who is in the scene; a fight, a rest, a group check, a hoard and a road are the scene's; going where the others wait ends the split; and a rest taken while the scene was elsewhere passes no more time.

A 20B narrator rarely says who goes, so the players' words are read once as the turn opens, by the utility model, for who stays behind: the narrator is told, its move of "everyone" is read as a move of those who go, and the server records the parting itself when the narrator records nothing.

The party panel, the rail and the scene line say who is where, and scripts/smoke-local.mjs gains a split scenario.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make Splitting Up an Option in Campaigns

1 participant