Moon Sweepers Zones and Map: Reading the Surface

Sectors, Regions, and Why the Distinction Matters

Two different units of progress show up in Moon Sweepers, and confusing them is the most common reason players feel stuck.

• A section is the small unit — one hex-shaped piece of ground that flips from dirty to clean.
• A region is the larger unit — a group of sections that completes as a whole.

The Steam achievements corroborate the split: one tracks helping to clean a hundred sections, another tracks completing ten regions. That tells you the game counts both, and it tells you the region counter is much slower.

Practically, this means section progress is not region progress. You can sweep for twenty minutes, watch the section count climb, and see no movement at all on regions, because regions only complete when their last section does. If a region near your base has one stubborn corner left, finishing it is worth more than starting three new ones. Players who read the beginner guide first tend to internalize this faster.

The store page's progress tracking is therefore best read as a completion map: it shows you what is done, not what is valuable.

The Color Code

Community guides describe the same three-color scheme with unusual consistency, which makes it the most reliable map information available:

The blue rule is the one that pays. A blue patch next to a green cluster means you already did most of the work; finishing it costs a fraction of what starting fresh costs, and it usually completes a region. New players chase orange because untouched ground looks like the real game, then leave a map full of near-misses behind them.

Orange has one legitimate use: it is where exploration rewards sit. Community guides describe flags and survey sites scattered across untouched territory, each worth a one-time cash reward. Those are worth a detour when they are on your route to a new work area, and not worth a dedicated expedition before you own a vehicle.

Terrain: Craters, Plains, and Slopes

The store page does not describe biomes. Community guides consistently distinguish flat plains from crater terrain, and several claim crater floors hold denser dust — but density claims are secondhand and may have been rebalanced.

What is safe to plan around:

• Plains are fast. Good visibility, easy driving, low risk of getting stuck, and usually the easiest place to learn a new vehicle.
• Craters are vertical. They need climbing, they are darker, and they punish a badly tuned motor. They are also where the interesting terrain is.
• Rims are buildable high ground. If solar exposure matters to your layout, elevated ground beats a basin.

Rather than trusting a density number, run the ten-minute test from the dust farming guide: time a container fill on a plain, then on a crater floor, and use your own data. That result is valid for your build and your patch.

Picking a Base Site

There are no published coordinates worth copying, and the guides that say otherwise are the ones to distrust. What you can do is score candidate sites against four criteria:

A site that scores well on all four is better than a beautiful location that scores on two. And the site you pick at hour one will be wrong by hour six — that is normal. Stations are meant to move forward; the progression guide treats forward stations as a purchase category rather than a one-time decision.

Using the Map in a Group

In a 16-player lobby, the map stops being a personal tool and becomes the coordination layer. Three habits make the difference:

1. Assign regions, not patches. Each squad takes a region and owns it to completion. Overlapping squads produce blue patches and duplicated travel.
2. Name stations by direction, not by color. "North rim station" survives a session; "the one by the big rock" does not.
3. Re-check the map every thirty minutes. Frontiers move fast with sixteen players, and a hauler running yesterday's route is burning the crew's time.

The multiplayer guide covers the role split that makes this work — scouts find the orange, sweepers convert it to green, haulers connect the two.

What the Map Does Not Show

A short list, so you do not go looking for features that are not there:

• No dust density overlay. Density is inferred from terrain, not displayed, and your sweep width depends on gear the tools reference tracks.
• No per-player contribution breakdown. The counters are collective.
• No "optimal route" line. Route planning is on you.
• No guarantee that green means empty. Community guides note that visually gray ground can still hold dust, so trust the counter over the texture.

That last point is the one that wastes the most time. The surface reads as uniformly gray from a distance, and the map is the only reliable statement about what is actually done.