FIELD GUIDE / ROBOT DELIVERY
Give J.O.O.N.A.S. a clear delivery route
The robot collects; a Capsule Catcher receives; the outgoing route decides whether that material reaches your factory or the base.
QUICK ANSWER
In patch 1.0.5, J.O.O.N.A.S. targets the emptiest Catcher in the nearest group. Catchers within 100 m of each other are grouped; the robot moves to the next group only when every Catcher in the current group is over 80% full. That 100 m condition is about Catcher grouping, not a stated robot launch range.
Connect collection to a destination
- Place the robot and a Capsule Catcher. Leave room to see the Catcher’s inventory and connect its output.
- Choose the destination. Run an outgoing conveyor to the base receiving port for a direct route, or to the appropriate input of your processing line.
- Watch a delivery. Confirm which Catcher receives the capsule. Do this again when adding nearby Catchers.
- Follow material beyond the Catcher. A receiving robot system is only part of the job. Confirm that the Catcher drains and the final destination accepts the material.
For a selling route, finish with a balance check. A robot cleaning and a Catcher receiving capsules do not by themselves confirm that the base has paid.
Read the group before blaming distance
The patch 1.0.5 rule has two stages: select the nearest Catcher group, then select its emptiest Catcher. It replaces the simpler expectation that capsules always go to one nearest Catcher.
20% · 70%Choose the 20% Catcher
81% · 92%Use the next group
Those percentages illustrate the Catcher selection choice, rather than a measured robot route. If two factories’ Catchers belong to the same group, an emptier one may receive material you expected elsewhere. Inspect their inventories and actual incoming capsules before changing the downstream belts.
The 100 m grouping condition describes Catchers relative to each other. It does not specify a robot’s maximum launch distance or resolve every grouping boundary case. For a borderline placement, check the receiving Catcher in the game.
Separate collection, delivery and output
| Symptom | Next check |
|---|---|
| The robot is not cleaning | Find it on the map and inspect its current activity and collection state. |
| Its container is full | Watch for a launch and inspect receiving Catcher inventories and available output space. |
| Capsules arrive at an unexpected Catcher | Compare group placement and fill levels using the 1.0.5 rule. |
| A Catcher receives but stays full | Follow its outgoing conveyor to the first blocked or disconnected stage. |
| The line reaches the base without payment | Run the small-load auto-selling check at the actual intake. |
Patch 1.0.4 addressed operation away from players. On an updated game, standing beside the robot should not be the first response to a delivery problem. Start with its visible state and the receiving route.
Add capacity at the actual constraint
More robots will not drain a blocked Catcher. First make sure receiving material can leave and reach its destination. Add collection capacity when the downstream line is consistently short of material; improve output when inventories keep filling.
There is no fixed robots-per-Catcher ratio used here. Terrain, collection conditions and the outgoing route can change what your factory receives. Expand one part, watch the effect, and keep the arrangement that improves delivery.
Guide assumptions
Check your current machine menus and observe a complete delivery route. Read the model assumptions before using a factory estimate.