Maintenance mode and production
DearScenario Player has no persistent dev switch. Runtime mode determines
the idle display: Normal mode is black unless idle_screen.image_path selects
a readable image; Maintenance mode shows the local guide and ignores that
image. The old idle_screen.mode setting has been removed.
Runtime maintenance state
| State | Local engineering panel | Browser maintenance commands | Remote Debug |
|---|---|---|---|
| Normal process | Hidden | Blocked | Not usable |
| Maintenance process | Available locally | Allowed from an authorized HTTP source | Available |
Start a Maintenance process with DearScenario Player --maintenance or -m. The mode
is selected before the player is constructed, is not written to config.json,
and cannot be changed while the process is running. The ordinary executable
entry always starts Normal mode.
Browser-maintenance policy
Browser maintenance is still subject to the HTTP source policy. The browser
must use the player's same origin for mutating requests, and the source must be
loopback or permitted by controller_whitelist. A non-empty whitelist matches
exact source IPs; an empty whitelist permits reachable sources without an
automatic private-subnet gate. OSC cannot invoke maintenance-only commands.
Commands such as mask_set and calibration_set declare
requires_maintenance_access. They return MAINTENANCE_MODE_REQUIRED in Normal mode or
MAINTENANCE_ACCESS_REQUIRED for a disallowed Maintenance source. Screenshots are
ordinary HTTP GET resources and do not require Maintenance.
Going live
- Start a Maintenance process and finish calibration and mask work.
- Save the desired configuration.
- Stop the Maintenance process and restart the ordinary entry.
- For a custom Normal-mode idle background, set
idle_screen.image_path; leave it empty for black idle.
Previous / Next
- Previous: How It Works
- Next: Configuration Sources