The No Asteroids co-op guide in one line: sessions hold up to 8 players across platforms, joining a session is free, and every credit earned from ore lands in one shared wallet. The campaign is the host's save, guests dig into the host's run while keeping their own game on their own accounts, and every credit earned from ore goes into one shared wallet that only the host can spend from.

How a co-op session is set up

The host owns the campaign. Everyone else joins that run and works the same asteroid, and the contract goal stays on the ship's wall board for the whole crew. Crew suits are numbered, so you can tell who is on the rock, and two crew can be seen working the same seam with the shared goal still tracked on the board.

One wallet, and the host approves the spending

All ore money from the crew lands in a single shared wallet. The host decides who is allowed to spend it, which means a purchase from the shared wallet has to be requested from the host and approved by them rather than bought by whoever happens to be standing at the terminal. Plan purchases around that rule: agree the upgrade order with the host before the run, not at the trade terminal.

A crew that sells together also saturates the market together, which is worth planning for: market saturation.

Reading the shared board and the LANDING counter

Two shared readouts matter in a crew. The wall board keeps the contract goal and the credit progress for the session, so it is the same page for everyone. Over the dig site, a LANDING n counter shows how many crew members are still on the surface, which is the countdown everyone's decision depends on: when the lander is about to leave, that number tells the crew how many people still have to get back.

Adding bots to a session

Bots can be added to a co-op session in the demo build. Two things about them are worth knowing before you fill a slot with one: they all crowd together at the same dig spot instead of spreading out over the asteroid, and each bot costs more than 2 GB of RAM plus extra CPU, so a session full of bots is heavy on the machine that hosts it. The build gives you no bot commands to change their behaviour and no cap on how many can join, so treat a bot as a body at the dig face rather than as a worker you can direct, and keep the count low on older hardware.

The landing counter still decides when the session ends, bots or not: the lander countdown.