Repository navigation
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
Open
Lebbitheplow wants to merge 1 commit into
Lebbitheplow wants to merge 1 commit into
Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
move_partynaming 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.absentdoes, 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.Small narrators
A 20B local model rarely says who goes. In twelve live plays where one character slipped off alone it passed
characterIdsonce, and in four it called nomove_partyat 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:
move_partyof "everyone" is read as a move of those who go;With it, three of three full plays of the new
splitscenario passed every step on that model (the split recorded, a passage for each group, the party together again), and a play of thetownscenario 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
Limits
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.test-enforce-conscience-563pass unchanged.scripts/browser/scenarios/100-party-split.mjsnow 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 splitis the live check, five beats: arrive, part ways, act alone, both act at once, come back together.Screenshots
Checks
npm run lint,npm testandnpm run buildpass, and the change has a test that fails without it..envfiles or players' names in the code, the tests or this description.Settings, options and controls
No client change is needed: the apps compile these screens from the server.
🤖 Generated with Claude Code