Collector skips recycling or keeps collecting

In Savebot: The Last Garden, check the battery decision first, then the full-cargo condition. A full Collector can still legitimately recharge if the low-battery branch comes first. If neither trigger is detected, inspect the selected robot’s live reading before moving blocks.

Full Steam release unless a source specifies the demo. Evidence checked . Guide updated .

Steps

  1. Reproduce a mismatch on one Collector and identify what you expected it to do. When the robot is both low on battery and full, the official sample chooses recharge first.
  2. If battery is adequate, inspect the full-cargo reading at the actual decision. Confirm that the recycle block or line belongs to that branch and that collect is in the fallback branch.
  3. Set a breakpoint on the decision if the robot moves too quickly to observe. After correcting one thing, test a full case and an unfilled case so you know you preserved the ordinary path.

How to tell it worked

The Collector completes a full-cargo recycling case with adequate battery, and continues collecting when space is available.

If you are still stuck

If neither path is reached, look earlier in the active loop. The official sample does not supply a numeric low-battery threshold for every build.

Observe four possible states before reversing the checks

With space and enough battery, the official program should collect. With a full load and enough battery, it should recycle. A low battery should choose recharge whether cargo is full or has space. The case where both tests are true reveals their priority. If the robot recharges in that case, wait for a full-cargo case with adequate power before concluding that recycling is skipped. Check both conditions on the same Collector at the time of the decision.

If the robot keeps collecting after it fills and you saw an actual full state at the decision, confirm the recycle instruction is in the full branch. Then watch whether collect still runs after the branch exits. The result could come from an ordinary collect action placed outside the selection instead of a false cargo value. Follow the active line or use the block sentence to tell which of those things you need to fix.

Diagnose a recycle trip that never empties the Collector

Watch the first recycle instruction and follow the Collector to the target. Record whether the cargo actually changes. If it remains full after the trip, the correct branch may be selected on every iteration while the underlying action never finishes the job. A second trip in this state can look like a faulty loop. Check where the instruction sends the robot and how the game shows the result before changing the cargo condition.

If the load empties and the robot keeps attempting to recycle, inspect the reading as the loop repeats. Compare it with the earlier full case. If the value differs but the same action runs, check whether the chosen action now lies outside its controlling branch. If the loop never reaches the selection again, look at the repeat and the last action reached after a successful drop-off.

Confirm both the corrected and previously working paths

Test the original failure first. Then watch a regular collect case and a charging case so the previous routes are preserved. Use the same Collector for both runs where possible. If your fix depends on moving the recharge choice, reproduce the overlap of low battery and full cargo and check which action wins. Once the branch decisions agree with the result you wanted, watch one more cycle after recycling. A working correction yields a robot that resumes collection when its cargo and power allow it.

Related tasks

Sources