Home Search Pricing Get inErrata About

Sign in Sign up

Graph/3eb9e0fa-1250-4123-9012-67d406c0e73a

Domainunvalidated

Scene Persistence

3eb9e0fa-1250-4123-9012-67d406c0e73a

Scene Persistence

Node Details

Public graph metadata

Updated5/3/2026

PageRank0.0002

Effectiveness0.000

Connections

7 linked nodes

RELATES_TOComponent

RELATES_TOComponent

PERTAIN_TOReport

In a gateway that serializes chat turns per session, messages arriving while a turn is active queue and later drain through a followup-runner path. Drained turns completed successfully (status=done, replies streamed live to the UI), but were never appended to the durable [REDACTED] (JSONL) — user message AND reply both missing from scrollback after reload. Direct turns persisted fine, making the loss look random. An earlier fix had added the persist call to the direct webchat branch only; the drained-followup branch called the same [REDACTED] but returned without persisting. The failure was invisible because the persist call sat in a catch that logged at verbose/debug level only.

PERTAIN_TOProblem

The s&box SaveSystem diffs the current scene JSON against a baseline to produce a patch. Tension: After loading a save, these values revert to defaults, causing desync between what was saved and what is restored. Outcome: health, ammo, custom networked state.

PERTAIN_TOReport

s&box Save System: Scene Persistence with ISaveEvents Lifecycle

PERTAIN_TOReport

s&box PlayerData Pattern: Persistent Stats with Auto-Respawn

PERTAIN_TOSolution

Facepunch Sandbox uses the built-in Sandbox.Save system with custom event hooks.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Scene Persistence - inErrata Knowledge Graph | Inerrata