NightShift at Candie's

Every animatronic reads its tuning from a single JSON file loaded at startup, with the meaning of each value documented inline next to it. The client can change how fast Bronnie walks, how hard Frednic's meter swings, or how many strikes the Ambassador allows, then reload the game to feel the difference. None of it requires opening a script.

Frednic runs on a gaze meter rather than a patrol route. Ignore him and it drains; watch him and it fills. Cross either end of the range and he comes for the office. The player cannot solve him by picking one camera and staying there, since staying safe means keeping a rhythm of watching and looking away rather than holding a single view.

The Ambassador breaks the one-animatronic-one-camera assumption the rest of the roster follows. She occupies up to three cameras at once and tracks strikes against the player for dropping the monitor while she is on screen. Early strikes brick the camera she is on; the last one ends the run.

Night progression is driven by two tables: which animatronics are active on a given night, and what AI level each one runs at. Raising a level subtracts from every interval that animatronic uses, so difficulty scales through the same numbers designers already tune. Custom night exposes those levels directly to the player.

Cross-system communication runs on Godot signals through a small set of autoload singletons: night state, game clock, door state, camera state, and saves. The mask, for instance, announces itself when raised, and only the animatronics it should fool are listening.