Starship Horizons
Log In
Knowledge BaseConsoles And Screens

Consoles And Screens

Everything the server can put in a browser is a screen. The STATION SELECTION page lists them in four groups, and the grouping tells you how to treat them.

Main — the player stations

These are the seats. Each is a complete console for one officer, and each binds to a vessel when you open it.

StationWhat it does
FlightFlies the ship. Helm, throttle, waypoints, autopilot, jump drive. See Flight.
TacticalWeapons, targeting, ordnance, weapon groups, shields under fire. See Tactical.
OperationsComms, crew, cargo, decks, alert status, objectives. See Operations.
SciencesScanning, sensor analysis, planetary survey. See Sciences.
EngineerPower, damage control, repair teams, fabrication. See Engineer.
CaptainOverview and command. Deliberately has few controls. See Captain.
Main ViewerThe forward view with no instruments. For the big screen.
ViewportA bare 3D view, for a secondary monitor.
SpectatorWatch without taking a seat.

Secondary — single‑purpose displays

Each of these shows one thing well. They are for the extra monitors around a built bridge, or for a phone or tablet propped beside a laptop — not for playing a role from.

Alert Status, Shield Status, Cargo Hold, Radar, Stellar Navigation, Stellar Body, Star System, Center, IRIS, Ship OS and Mission Status. Mission Status is the useful one for a GM who wants a second window showing objectives and messages without the whole GM console.

In Progress

Screens that exist but are not finished: Crew Roster, Collision Alarm, Dashboard, Vessel Status and a few role‑specific panels. They will load. They may be incomplete or wrong, and they are not part of a session you care about.

Admin

Stations that reach into the running game or the content on disk. Do not hand these to players.

StationWhat it does
Game MasterRuns the session. See Running A Session As Game Master.
HydraThe editor suite. See Modding With Hydra Studio.
ScoreboardSession scoring, for events and conventions.
GalleryBrowses the models and images the loaded modules provide.
DMX / MQTT viewersDiagnostics for physical show control — lighting, props, hardware.
GamePadsShows what the server sees from connected controllers. The place to check when a joystick is not working.

Where the list comes from

The station list is not fixed. Each module contributes screen registrations, and they are merged after the base game loads, so an enabled module can add stations or replace one that already exists. That is how the Hydra editor's screens appear only when the Hydra module is enabled. A screen can also be marked not visible, which keeps it off the selection page while leaving it reachable at its own address.

The mechanics of that are in Client Architecture.

Last updated 5 September 2026