What this page covers, and what it deliberately does not
Moon Sweepers gives you a whole moon and a toothbrush. The useful map questions are structural, not cartographic: where do the fixed-value collectibles sit, in what order should you open ground, and how do you keep a crew from sweeping the same crater twice.
That is what this page answers. It does not publish point-by-point coordinates. We only print numbers and locations we have been able to verify, and a guessed coordinate on a map page sends a reader on a wasted trip — worse than no coordinate at all. What follows is the part that keeps working even when the ground moves.
The two collectibles, and why they matter more than dust
Dust is sold by weight, so its value per trip depends on your tools, your processing chain and how far you walked. The two collectibles are the opposite: fixed positions, fixed payouts.
| Collectible | How many | Value each | Total |
|---|---|---|---|
| Flags | 195 | $100 | $19,500 |
| Survey points | 26 | $250 | $6,500 |
About $26,000 of fixed value sits on the map, and none of it depends on an upgrade, a machine or a belt. In a game where the next big purchase is a $20,000 cleaner, that is not a side activity — it is the most reliable funding source in the first two hours.
Why flags come before deep cleaning
The early game tempts you into sweeping one patch until it is spotless. That is the wrong order, for one reason: your cleaning power is low early and high later. Clearing a patch with a $10 hand brush earns a fraction of what the same patch earns behind a $250 robot vacuum, and the collectibles pay the same either way.
So the order that works:
- Open ground and take the fixed-value items first. A flag pays $100 whether you found it with a hand brush or a J.O.O.N.A.S.
- Sweep shallow, wide. Cover a large area at low depth rather than one patch at full depth — you are looking for flags and survey points, not for a clean floor.
- Come back with machines. The patches you skipped are the ones the robot vacuum and the pressure chamber will make profitable later.
- Then build automation under the route you actually walk. Belts go where the work is, not where the base is.
That last point got much easier in patch 1.0.6: belts now turn at 45°, 90° and 180°, run diagonally, and climb ramps and stairs, so a route can follow the terrain instead of needing flat ground. See the Packager guide for the routing rules.
A sweep plan that four players can follow
Splitting a moon between sixteen players fails for a boring reason: nobody knows which ground is already done. Three habits fix it.
- Divide by direction, not by patch size. Player one takes north, two takes east, and so on. Direction boundaries are obvious from anywhere on the surface; patch boundaries are not.
- Use the survey points as anchors. With 26 of them across the map, they are the natural chapter markers: "everything between survey point three and four is done." Recording progress against them is more reliable than remembering a crater shape.
- Announce flags in chat. A flag is $100 for whoever gets there first, and in a 16-player session that is how arguments start. Call it out and the group stops competing over the same rock.
In co-op, one rule covers most of it
Upgrade matrices have been shared across the whole crew since patch 1.0.3, so progression is team-wide. That has a map consequence people miss: there is no reason for each player to "cover their own area for their own upgrades". The crew's cleaning power is one number, so the efficient plan is to put everyone where the density of remaining collectibles is highest, not to give each player a private territory.
What we will add when we can verify it
Two things would make this page genuinely useful, and both need a source we trust:
- Per-area flag and survey point counts, so a crew can tell whether a quadrant is finished.
- Named landmarks per area, so a route can be described in words instead of coordinates.
If you have a list you are confident in, tell us where it came from and we will credit it. Until then this page stays on mechanics and routing, which stay true across patches — unlike a coordinate list, which a terrain change would quietly invalidate.