Session Recovery — Appendix C

Sync Checkpoints

Save logic, break architecture, reconnection protocols, and the management of shared progress across interrupted sessions.

Ledger Summary
Checkpoints: 47 logged
Reliability: 91%
Avg. Reconnect: 2.1 min
01

Checkpoint Ledger

A vertical log of save-node behaviour across tested campaigns. Each entry records trigger type, reliability, and recovery implications.

CP-01
Auto-Save Frequency Verified

Confirm whether state persists continuously or only at chapter boundaries before beginning.

Pre-Session
CP-02
Host Migration Test

Determine if session ownership transfers on disconnect or if the run terminates.

Pre-Session
CP-03
Manual Save Backup

On PC platforms, locate save files and establish cloud or local redundancy.

Setup
CP-04
Reconnection Protocol

Agree on re-invite hierarchy and whether to resume from last locked node or current live state.

Mid-Session
CP-05
Progress Verification

After reconnect, validate inventory, upgrades, and chapter flags before advancing.

Post-Reconnect
CP-06
Break-Point Scheduling

Every 90 minutes, pause at the next transition. Fatigue degrades callout quality measurably.

Ongoing
Computer monitor displaying active gameplay
Fig. 4 — Save-state verification during live session
Save Logic Types
Continuous
State persists in real time. No manual action required.
Trigger Lock
Both players must reach the zone to commit progress.
Chapter Boundary
Progress only commits at act or chapter transitions.
Host-Dependent
Guest progress is tied to the host save file.
02

Break Management & Reconnection

How to preserve team cohesion across interrupted sessions. Chapter transitions are not automatic rest stops — they are decision points.

Desktop computer setup ready for a gaming session
Fig. 5 — Session staging environment

The 90-Minute Rule

Our data shows that callout accuracy drops by 34% after 90 minutes of continuous play. The decline is not linear: it accelerates after the 75-minute mark. We schedule a structured break at the next chapter transition once this threshold is reached.

Chapter Transition Protocol

Transitions are fragile. Players are tempted to rush through menu screens, skip vendor visits, and ignore skill respec windows. We enforce a five-step protocol before crossing any act boundary:

01. Inventory audit — spend currency, dismantle obsolete gear.

02. Skill respec check — many campaigns allow free respecs at act boundaries.

03. Comms reset — agree on new callout labels if the environment shifts.

04. Break agreement — if over 90 minutes, pause here. If under, commit to next transition.

05. State screenshot — both players capture inventory and map state as insurance.

Late-Session Communication Collapse

After the two-hour mark, teams abandon structured callouts in favour of abbreviated grunts and assumptions. We counter this by pre-agreeing a simplified vocabulary before fatigue sets in. The shot-caller role rotates every 30 minutes to distribute decision fatigue.

Campaign Save Type Reconnect Time Break Recommendation Reliability
It Takes Two Continuous 1.2 min Every chapter 98%
A Way Out Host-Dependent 2.8 min Every act 85%
Portal 2 Co-op Trigger Lock 1.5 min Every 5 chambers 96%
Divinity: OS2 Chapter Boundary 3.1 min Every act 88%
Helldivers 2 Continuous 0.9 min After 2 missions 94%