Log inGet started
World

Red Dot Rising

Branchmain
Branchesmain
Commit3b5552605d

README.md

Screens

Everything RED DOT RISING puts on the glass. Mounted by the scene entrypoint on mount_ui.

It owns the five cards (title, how to play, pause, WIN, MORNING SHIFT), the four HUD screens (cats, dawn, crosshair, captions), the menu input map — live exactly while a card is up — and the Focus walk that gives a controller a lit row to steer by.

Every family reaches every row

Three routes end in one place, act(id):

FamilyHow it gets there
mouse, fingerthe row's own onClick, delivered to onCallback
pad, keyboardnavigate walks Focus, confirm fires Focus.id()
mouse againthe pointer crossing a row re-points the focus, so the lit row and the row under the cursor never disagree

A first-person game holds the pointer, and a held pointer never reaches the UI, so a card takes the pointer lock back when it opens and hands it to the game again when it closes.

What it reads and what it writes

Reads Core.state (phase, heat, cutOut, dawn, floor, asleep), Core.dot.active and Core.cats. Writes Core.state.phase through Core.setPhase for title / how-to / paused / play, calls Core.resetRun() on restart, and emits ui.action { id, family } whenever the player chooses a row.

Listens for phase.changed, game.won, game.lost, voice.line (drawn as the caption strip, so a line whose audio failed is a quiet line and never a lost one), beat (a cutscene takes the HUD off the glass and puts it back) and run.reset.

Seeing a card without starting a night

The screens belong to play; in edit they come down. Set Core.state.uiPreview = true and the card for the current phase draws in edit too, which is how a storefront shot of a card is taken.