Practical guide
Diagnose and recover from a package fault
Use bounded diagnostics, package isolation, Safe Mode, reload, and standard restoration without stopping simulation.
Procedure
- Open the compiled Scripts diagnostics panel and identify the package, callback, generation, and stable error ID.
- Correct the package source or manifest without changing gameplay owners.
- Reload packages; the host validates the candidate before replacing the live graph.
- If faults repeat, allow the host to disable only the failing package after its threshold.
- Use Safe Mode to remove scripted surfaces or restore the standard interface from the compiled shell.
Example
-- Recovery controls are compiled, not Lua-owned.
-- Fix the package, then activate ui.action.packages.reload.
-- If the replacement fails, the previous valid graph remains active.Constraints and recovery
- Diagnostic history is bounded and does not become simulation truth.
- Safe Mode disables package presentation while fixed-tick simulation continues.
- Do not implement recovery by directly editing owner state or by replacing the compiled shell.