Classify the failure first
A bad tactical choice is not a system error. A transcript that says “attack” when the player said “back away” is. Canon contradiction, speech recognition error, technical interruption and player regret need different recovery paths.
Clear categories prevent correction tools from becoming consequence-free rewinds.
Correct before the checkpoint
For high-consequence actions, show what the system understood before sealing the result. The player can correct wording or flag a canon issue, then the Game Master resolves the repaired action.
Once a legitimate outcome is checkpointed, it should remain part of the campaign unless a later system audit finds an actual violation.
Technical failures should pause the table
Connection loss, Bluetooth changes or an incoming call should not consume playable time or commit a partial action. The app needs an explicit paused state and a reliable resume point.
If a paid service fails after charging, entitlement and usage reconciliation should happen automatically or through a visible support path.
Repair should remain in character when possible
After the mechanical correction, the scene can resume naturally without forcing the player to reread debug details. A short statement of what was restored is enough.
Living Party separates transcript correction, canon recovery and ordinary consequences, using checkpoints to protect both fairness and the permanence that makes a campaign meaningful.
Frequently asked questions
Can I undo a bad roll?
Ordinary bad outcomes should remain consequential. Correction is for misheard input, canon violations or technical errors, not simple regret.
What happens if voice recognition is wrong?
The transcript should be reviewable and correctable before a consequential action is committed.
Should connection time be billed?
Technical waiting and recovery should not consume playable time in a time-metered voice RPG.