Node-Based Galaxy Map

Lore & Background

In the shattered remnants of the old human Empire, the Aeon—a vast, self-aware supercomputer that once administered galactic governance—has calcified into an authoritarian overlord. Its drone fleets patrol every sector, and its logic is absolute: dissent is an error to be corrected. The Rebels, a scattered coalition of smugglers, defectors, and idealists, operate from a hidden base at the edge of mapped space. Their single most important objective is to broadcast a message that will shatter the Aeon's hold on loyalist ships, but that message must be physically carried through Aeon-controlled territory by a lone pilot and a small crew.

The galaxy the pilot navigates is not a blank canvas. It is a lattice of contested space: Aeon patrol corridors, rebel supply drops, derelict stations, and the cold void between stars. The node map abstracts this political reality into a series of binary and ternary choices. A node might be a shop run by a nervous rebel contact, a combat encounter with a heavy Aeon frigate, or a random event where a dying trader begs for help. The map does not tell you what lies ahead; it only tells you that something does, and that you must commit to a direction before the oxygen gauge ticks down another notch.

What makes the node structure feel alive, within the fiction, is the sense of a galaxy that is actively hostile to the pilot's presence. The Aeon's forces are not static; the encounters escalate, the paths narrow, and the final stretch to the Rebel base is often a gauntlet. The map encodes the story's tension: you are a single thread trying to pass through a net that is designed to catch you.

In Their Own Story

The cockpit smells of burnt wiring and recycled air. You watch the node map glow on the forward display—seven amber dots strung across a dark field, each one a door you can walk through or a door that will close behind you forever. O2 reads 78%. The engine hums a low, tired note. Your engineer is patching a hull breach on deck two, and the medic is arguing with the pilot about whether to spend the last of the repair kits now or save them for whatever is waiting at node four.

You choose node three. A shop. A tired voice on the comm offers a weapon upgrade for credits you don't have, and a quiet rebel woman asks if you've seen her sister's ship. You don't stop. You can't stop. The O2 drops to 74%, and the next set of nodes shuffles into view: two combat encounters, one event, and a path that threads between them like a knife through silk. You take the middle path. The stars blur. The Aeon is out there, patient and vast, and your little ship is a splinter in its eye.

You keep flying.

Reader's Guide

The Aeon's grip on the galaxy is enforced through control of space itself. Rebel pilots must thread a branching corridor of nodes from their starting position to the hidden Rebel base, and the map is generated fresh each run so the Aeon can never predict the exact route. At every node you face a choice: engage, detour, or push through. Unchosen branches vanish, so a single early decision can deny you a critical upgrade or force you into a fight you weren't ready for.

This is where the in-ship systems become your survival kit. Oxygen depletes in real time, so lingering at nodes or over-warping drains your margin. Power must be split between shields, weapons, engines, and life support every second; a heavy shield allocation leaves your engines sluggish and your O2 support thin, while maxing engines lets you warp faster but leaves you exposed. Hull damage from any encounter must be patched by a crew member in real time, and if a system goes offline the whole ship suffers cascading failures.

The node map is the strategic layer; the ship is the tactical layer. Master both. Read the node types before you commit—combat nodes escalate, event nodes are unpredictable, shops are rare. Budget your O2, your credits, and your crew's health across the full path, because the Rebel base is always the same distance away, but the road to it is never the same road twice.

Did You Know?

• The node map is procedurally generated for every single playthrough, meaning the exact sequence of encounters, shops, and combat nodes changes each time you launch a new run.
• The number and type of nodes available at each step depend partly on the ship type you select at the start, so a scout-class vessel and a heavy gunship can face meaningfully different route options.
• Once you warp to a node, the alternative branches from that junction are permanently lost for the duration of the run—there is no backtracking or re-routing.
• The Rebel base, your ultimate destination, is always the final node on the map, but the path length and the mix of encounters between start and finish vary by ship and difficulty setting.