mech_runners

mech_runners

You are the remote runner for HOUND-7, an autonomous combat frame linked through a terminal. SAINT-11 can walk, auto-engage, and keep itself alive, but it needs you to read the screen, issue intent, manage risk, recover field data, and choose what kind of route this run becomes.

The best way to learn is to play. Use the core commands below, follow command hints, and let faction routes, strange signals, salvage, and story hooks reveal themselves through the run. Not every system is meant to be visible at the start.

What you are doing

• Read the panels. Top status tells you combat state, time, node, hull, shield, heat, q-link, target, and route. The local panel is your first stop during combat.
• Ask the terminal for facts. scan, status, log, and nav tell you what is known and what can be done next.
• Guide SAINT instead of driving it. SAINT auto-attacks by default. You win by choosing targets, adjusting shields and power, using countermeasures, recovering salvage, researching upgrades, and making route/story decisions.
• Expect discovery. New commands, route options, faction interactions, research, and hidden anomalies are more satisfying when discovered through play. If a command is not in help or autocomplete yet, keep playing and look for the unlock.

Core loop

1. Start with start.
2. Read top status, local panel, notifications, and recent console output.
3. Scan the area before committing.
4. Target and survive while SAINT fights.
5. Recover salvage, repairs, telemetry, and research data.
6. Check objectives when the fight changes or ends.
7. Preview and choose a route.
8. Repeat until the endgame path opens.

Commands you will use constantly

help

start

scan targets

status

target list

target set <id>

fire laser.cutter <id>

shield status

cm status

salvage scan <id>

salvage download <id>

salvage collect <id>

research list

log objectives

log quests

nav options

nav preview r1

nav route r1

nav commit

pause

resume

You do not need to memorize every command. Use help, Tab, and command output as your guide.

How to think during an encounter

• Unknown contact? Start with scan targets, scan local, and sometimes scan comms.
• Need focus fire? Use target list, then target set <id>.
• Incoming missile or warning? Check cm status, then use cm launch <projectile> or cm burst if the threat is active.
• Taking heat or shield pressure? Check status, shield status, and route power or shield modes as needed.
• Faction contact? Some encounters reward restraint, hails, weapon holds, or careful scanning more than raw damage.
• After the fight? Scan/download/collect salvage before leaving if the field is safe.

Route and story discovery

Use log objectives, log quests, respond list, and nav options when the run starts to feel quiet. These commands point you toward the current objective, optional hooks, and route choices without spoiling every hidden path.

Different seeds and route choices can expose different faction contacts, salvage, research, anomaly evidence, and consequences. The game is built around learning patterns over multiple runs, not following one perfect checklist.

Minimal first-run rhythm

start

scan targets

target list

target set E1

status

fire laser.cutter E1

scan comms

log objectives

salvage scan <visible salvage id>

salvage download <visible salvage id>

salvage collect <visible salvage id>

research list

nav options

nav preview r1

nav route r1

nav commit

Then repeat: read, scan, survive, recover, research, check objectives, choose a route, travel.