Sessions, scenes & play actions

Set the play clock

1. As authorized staff, open Chronicle settings → Play & automation → Manage scene & turn, or use /scene.
2. Start a named session. Start a named scene when play begins.
3. Advance the recorded turn when the table moves to a new turn.
4. End the scene and session at the appropriate boundaries.

These are recorded game boundaries, not wall-clock timers. Procedures with once-per-turn or once-per-session restrictions depend on them. Do not create a new session just to repeat a limited action.

For Vampires, Rise for the night records a separate in-game date through Play actions or /play-action. Use a YYYY-MM-DD date for the night, not the current date unless that is your game's date. Blush and nightly aggravated mending use that recorded awakening.

Use the character's Play actions page

1. Open an accepted character sheet and select Play actions.
2. Choose an action available to that character type.
3. Complete the fields relevant to that action. For an Attribute + Skill test, choose both traits, Difficulty and any situational modifier.
4. Choose Private result if appropriate. Use scene confirmations only when the Chronicle authorizes you to confirm them.
5. Resolve the action, or submit it for staff review with the necessary scene facts. Check the result and current character state.

The sheet-based test builds its pool from stored traits and supported modifiers, including applicable impairment and form effects. This differs from /dice, where you enter a final pool. Do not add the same modifier twice.

Supported action families

Tribe Favor use can require confirming the actual situation. A selected Favor is not a universal bonus to unrelated tests. Feeding requires confirming an eligible vessel and consequences; entering an amount does not establish that the vessel was available.

Review requests

1. Players describe what happened and submit a request when they lack authority to confirm the scene fact.
2. Server Staff open Review play requests from the scene tools or use /play-review.
3. Inspect the character, action, submitted inputs and reason, then confirm and resolve or reject with an explanation.
4. If state changed, ask for a current request. A decision must not apply an old cost or effect to a different character state.

The default is staff confirmation. A Chronicle can authorize players to confirm facts for their own characters. Permission is checked when the operation runs.

Older results and new dice embeds

The sheet Play actions history and /test use the existing play-action records. /willpower-reroll takes the numbered dice and result number from that history. The newer /dice system uses its own result embeds, action buttons, and Dice Logs.

Current limits

The system automates implemented calculations, validates current state, applies supported costs, and records outcomes. It cannot infer unstated fiction or execute every published power merely because the description is present. Unsupported exceptions need a clear ruling and an authorized reviewed change or correction.