TV Studio

A server-side state machine with two lifecycles — the fixed quiz arc and a generic timeline of named segments — driving cues, bots, seating and scoring from a data definition. Deterministic: the same definition and the same ticks produce the same snapshots.

• Invalid transitions are rejected, never coerced
• Host overrides apply per room, never by mutating the shared definition
• Lobby policy: a fill wait, bots after a timeout, fast re-entry once a room has seen a show
• Every game concern arrives through an injected hook

A Scriptable camera re-asserted every frame, so a respawn can never steal the shot, cutting across a twelve-mark bank — nine fixed broadcast angles plus a rail, a jib arc and a top shot — with a lens that follows the shot.

• A crane open that pulls wide while it rises
• Rail track, jib orbit, push-in and breathe moves
• Depth of field racks onto the contestant’s face on a reveal and keeps tightening
• Operator hand: Perlin noise on the framing, scaled by how tight the shot is
• Phone framing steps back only as far as the studio walls allow

No external assets. The room, the deck, the LED wall, the truss, the quiz desks with edge-lit acrylic wings, the flown PA, the grandstands and the crowd are generated on the server from the theme — 2,046 parts, 40 lights, 38 light shafts.

• Every colour in the set is theme data, so a reskin never touches a builder
• Fresnels clamped to a ceiling grid, guaranteed to hang below the pipe that holds them
• Light shafts as six additive beams whose widths diverge toward the floor
• The crowd bobs in slices, so the per-frame cost does not grow with the seating

A three-point rig, an audience blinder bar and moving heads choreographed off the replicated show state. The theme defines named looks and moods, a format maps its states onto those names, and a definition may override any of them.

• Looks: fan out, sweep, focus, cross, celebrate, wave, skyward
• Moods: colour, energy, speed, level, chase and a flourish cadence
• Blinders strike on every reveal and on the finale
• Shadows only on the keys, because they cost

Title cards, lower thirds, wipes, a radial timer, the rosco wheel, the scoreboard, desk plates, a video wall with live cards and the winner ceremony with confetti — all from the theme’s palette, fonts and motion presets, so a reskin reaches every widget.

• One layout module owns every screen rule: phone, short landscape, on-screen keyboard
• Widgets fade as one object, and nothing hides until the tween has really ended
• Injected overlays share the contract the built-in widgets use

Serves 2,010 rosco and 600 trivia questions in neutral Spanish and validates answers fairly: diacritics folded, one typo tolerated, the wheel letter derived from the answer’s first character so “ñandú” lands on Ñ.

• One question per letter drawn at random from that letter’s pool, so every rosco is different
• Never repeated within a show, avoided across consecutive shows and across a player’s history
• Difficulty ramps from the easy end of the pack to the hard end within a round
• Packs live server-side; the client never holds an answer key

The game never needs more than one human. Bots take the host role and every empty desk and answer with a profile the host picks — clumsy, normal or expert — and their hesitation is part of the design.

• 35, 60 or 85 percent accuracy, one to seven seconds to answer
• Negative user ids by convention, so nothing downstream mistakes them for people
• A pure module, deterministic under an injected random source

Cross-server spectating rides MessagingService, whose payload cap is one kilobyte: a compact codec with single-letter keys, a monotonic sequence number, and a receiver that drops anything stale or duplicated.

• Only discrete transitions are broadcast; spectators interpolate locally
• Publish and subscribe touch the service only when called, so the module tests headless
• High-frequency intra-server data goes over UnreliableRemoteEvent

Session-locked profiles through Lapis, a skill-earned coin economy with no gambling primitive, daily streaks and quests, a 28-day Series Pass with twelve tiers, a Robux storefront with receipts deduplicated by purchase id, and nine procedural cosmetic slots on the player’s desk, plate, scoreboard row and avatar.

• Receipts are confirmed only after the profile has saved
• A repeated cosmetic pays out coins instead of duplicating
• Every user-authored string passes TextService before it is shown or stored

The Producer Pass makes its owner the host of a private server: go to air, skip, set difficulty and pacing, pick the bot level, and write questions for their own audience. Every button is an intent the server re-authorises and re-validates.

• Room settings clamped so a host cannot make a room unplayable
• Custom questions stored already filtered; the engine refuses to serve unfiltered text
• The experience owner always hosts, detected by creator id rather than a hardcoded user
• A switcher: preview and air monitors per camera mark and a cut the server holds on air before the automatic director takes back over

Two entry points — a server start and a client start — take a definition, a scene, a theme, question sets, an audio manifest, overlays and hooks. A tier manifest lists what Lite ships, and one command builds both models with the version stamped in.

• Lite: the director, both lifecycles, title card, lower third, scoreboard, countdown, wipes
• Pro: the set, the rig, the crowd, the creative moves, the quiz format, the host panel, the video wall
• A Pro cue on a Lite install degrades with a named message; it never breaks the show
• Quickstart, field reference and reskin guide, written for a creator who has never seen it