Crash Bot

Think like the ship's computer

Your ship is damaged, its launch systems need attention, and its view of the surrounding world is incomplete. Use machines as your eyes and hands: observe, recover useful material, repair the ship and decide when to leave.

Programming is part of the game. A machine can only sense and act through its installed hardware. Change its program, inspect what it knows, and use the result to improve the next attempt.

• Assess the emergency. Inspect damaged ship systems, available resources and departure checks.
• Assemble a machine. Choose components and a starter program for the task. Tools, power, processing capacity and sensors matter.
• Program behaviour. The Blueprint foundation connects execution and typed values, with conditions, arithmetic, variables, timers, named events and callable routines.
• Understand failures. Inspect execution, step through routines, use breakpoints, and navigate larger graphs with zoom, search and an overview.
• Explore through evidence. Cameras and sensors build observations; the world view is based on what machines have discovered.
• Recover and launch. Bring material back, repair the ship and weigh additional cargo against the remaining departure window.

The world and machines we are working toward

These approved reference images establish the visual direction. They are concept art, not current gameplay screenshots. Illustrated locations, machine variants, numbers and interface details are not a list of finished features.

A working foundation, with substantial work ahead

The prototype has ship assessment and repair, component assembly, programmable machines, sensors, bot cameras, recovery missions, save/load and launch logic. Existing standalone checks have exercised both fleet and single-machine recovery loops.

The current direction includes modular walkers, improved programming tools and a clearer ship-computer interface. Navigation, fleet reliability, physical behaviour, beginner usability and visual quality still have open acceptance work. Older successful tests do not establish that every later build is ready.

Terrain styling and the polished artwork shown here are direction for development. They do not represent the prototype's current finished appearance. The available development player is a Windows prototype; public system requirements, supported release platforms and a release date have not been announced.

For prototype testers

1. Start with Emergency assessment and read the ship's departure requirements.
2. Inspect a starter machine and its program before changing components.
3. Run a small change, watch sensor and execution feedback, and save a checkpoint.
4. When reporting a failure, include the build, mission seed, machine configuration and the steps leading to it.

Prototype controls and save compatibility can change. Use the instructions supplied with your particular build; the public page is an introduction to the project, not a replacement for its test guide.

Common questions