Interface

HUD & interfaces

The interface keeps the current ship and the next useful action in view. Detailed windows for cargo, communication, objectives, groups, and navigation open only when they are needed.

Overview

The ship at a glance

Hull, shields, action points, movement, cargo, and active effects stay close to the map.

Actions follow the screen

Desktop keeps frequent tools around the map, while mobile gathers them into a compact action bar.

Details on demand

Inventory, map, tasks, chat, group tools, and the Wiki open as focused views instead of crowding the play area.

Rules

Reading the HUD

The main HUD answers the questions that matter from moment to moment: which ship is active, what it can still spend, what is nearby, and what the last action changed.

The ship state keeps hull, shields, action points, movement, cargo, and active effects together.
Selecting something on the map opens the actions and information that currently apply to that target.
Inventory and module changes refresh the displayed ship values after the server confirms them.
Action feedback and event logs explain what changed instead of asking the player to infer it from the map.

Always relevant: Current ship, nearby space, remaining resources, and recent outcomes.
Detailed rules: Combat, Gathering, and Modules explain the mechanics behind the controls.

Desktop and mobile

Both layouts expose the same game state. What changes is how many tools can remain open around the map without getting in the way.

Desktop keeps frequent controls and status panels around the play area.
Mobile gathers scan, group, corporation, craft, repair, and stealth actions into a collapsible bar.
Inventory, map, tasks, chat, and other detailed tools open in focused windows on both layouts.
The Wiki sits with those tools and provides a direct route back to the game.

Same information: Desktop and mobile read the same server-confirmed ship state.
Different priority: Desktop favors simultaneous visibility; mobile favors quick, compact access.