Begin with a short mining trip and your first ore sale

The No Asteroids demo covers the first 15 in-game days, giving you a limited window to turn a basic mining trip into a working upgrade loop. This No Asteroids first 15 days walkthrough uses the stages shown in a player's demo session rather than inventing a mandatory shopping list for each day. Your orders, income and purchase timing should determine how quickly you move between stages.

On your first trip, board the lander and head to the asteroid. The recorded keyboard controls use the left mouse button to dig, C for the mineral scanner and E at the lander to board. A later official update adds keyboard rebinding, so follow your current on-screen prompts if you have changed those bindings.

Watch both remaining air and cargo. Return before air becomes an emergency, then sell your haul at the Trade Terminal near the lander. That first sale funds the next round of equipment instead of ending the trip's purpose at excavation alone.

Spend the early trips fixing your largest bottleneck

The player's early choices show why equipment upgrades work best when tied to a problem you have actually encountered.

What slows your next tripUpgrade area to inspect
Searching for useful depositsMineral scanner equipment in the Suit Locker
Running out of airAir tanks and the return route
Filling cargo well before you must leaveCargo Hold and applicable Compactor upgrades
Spending too long returning from a holeThe purchasable tether
Extracting a deposit too slowlyTools and their upgrades in the Workshop

In player experience, the scanner upgrade highlights ore through rock. The tether then helps with the return to the lander, while more air and carrying space support longer or more productive trips. These are useful examples of responding to a bottleneck, not proof that every save needs those purchases in exactly that order.

Check the order of the day before leaving. The recorded session includes requests for particular ore quantities and extra money for completing them. Read the actual request rather than assuming that a fixed day always asks for the same mineral.

Work toward stronger harvesting and the Engineering opening

The recorded demo progression moves from the pickaxe to a sledgehammer and then a drill. The player finds the sledgehammer useful for breaking open a route, but describes it as different from harvesting the ore itself. The drill produces a substantial improvement in that player's harvesting experience, after which cargo capacity becomes more noticeable as a limitation.

Later in that same demo session, a message opens the engine room and introduces Engineering. Inspect the ship slots and the descriptions of guns and support systems there. Ship guns attack the asteroid automatically while you mine, providing another way to increase the operation's excavation beyond your handheld tool.

Do not force a particular unlock day onto this route. The evidence supports the progression shown, not a universal trigger tied to a purchase or an exact daily schedule.

Finish the demo with your continuing save in mind

The official demo announcement says you can play the first 15 days and carry your save into the full game on the same computer. As of November 19, 2026, the full release is scheduled for November 24.

Later preview videos that continue past day 15 are not evidence that the public demo removes that limit. Use the demo to learn the mining, selling and upgrading loop, then keep the same-computer save for continuation rather than treating a preview's later equipment as a required demo milestone.

FAQ

Do I need to make the same purchases on specific days?

No fixed day-by-day shopping sequence is established here. Follow the stages and address the limitation your current trips actually reveal.

Is the drill available in the documented demo route?

Yes. The cited player demo session purchases and uses it before that session reaches the demo ending.

Does the demo save transfer to the full game?

The developer says it carries over on the same computer. The announcement does not establish a cross-computer transfer procedure.