Evidence boundary: The two thresholds come directly from the October 28, 2026 developer patch. Examples here reason from that text; GGClue has not captured any actual targeting behavior, and the patch does not specify tie-breaking or chained group topology.
Work through the cases without guessing
| Example situation | What the patch supports | What remains unknown |
|---|---|---|
| Two catchers in the nearest group, one at 20%, one at 70% | Prefer the emptier catcher | Other group geometry and actual target feedback |
| Every catcher in the nearest group at 81% | Select another viable group | Behavior if no such group exists |
| One catcher at 80%, another at 81% | The condition that every catcher is over 80% has not been established | Exact switch at 80% is not stated |
| Three receivers in a line, A–B and B–C within 100 m but A–C farther apart | The notes do not define transitive grouping | Whether all three share one group |
In particular, do not reinterpret “over 80%” as “80% or higher”, or “within 100 m of each other” as a global maximum capsule flight range.
Diagnose a catcher receiving more than another
- Verify the installed build is 1.0.5 or later, rather than following an older video that assumed one permanently selected receiver.
- Sketch the receiver placements, approximate distances and current fill readings. You do not need exact world coordinates to test the nearest visible cluster.
- Compare the receivers within the likely nearest group. If one is emptier, the developer’s note suggests that receiver is favored.
- Check whether all receivers in that group exceed 80%; if not, do not conclude that the routing system should already change groups.
- Inspect the selected catcher’s output. A correctly targeted catcher may remain full because its downstream conveyor is disconnected.
- Record a single actual delivery with its fill readings before and after. This is the minimum evidence needed to investigate a case that disagrees with the patch text.
Receiver routing is not automatic sale
The catcher receives capsules; a connected output path still has to deliver material to the Hub’s intake. When money is not increasing, separate which catcher J.O.O.N.A.S. targets from whether the catcher outputs can travel to the Hub. For the second task, follow Packager and conveyor sale troubleshooting. For stalled Garage output, use the Garage outfeed guide.
What images would verify this guide
An original game capture should show (A) catcher positions and readable fill %, (B) the delivered capsule’s selected destination, and (C) the catcher output belt. Add a small, clearly labelled schematic explaining the 100 m/80% conditions only as editorial interpretation. Do not manufacture a top-down map and label it as captured gameplay.
Source
- Developer 1.0.5 patch: https://steamdb.info/patchnotes/26264480/
Known unknowns: Whether receivers in a chain form one group, how equal fill levels are handled, target selection if all groups exceed 80%, and maximum firing distance require independent in-game verification or a developer clarification.
Related GGClue guides
For this task, see Moon Sweepers hub.