Robot runs out of battery
In Savebot: The Last Garden, put the battery check before the robot starts another work trip, then watch whether it reaches the charger and resumes its job. If it turns back but runs out en route, compare a shorter route before changing the rest of its program.
Full Steam release unless a source specifies the demo. Evidence checked .
Find where the charging trip fails
In a launch-day Steam review, a player described a robot running out of battery and changing its program so it would travel back to the base to charge. That is the task here: diagnose a working robot that loses power during a route. The developer's Collector sample puts the low-power decision before cargo and collection. Apply the order to the robot you are actually fixing, while keeping its normal job specific to its trade.
| What you can see | First check |
|---|---|
| The robot keeps working at low power. | Open that robot's program and find the decision it reaches before starting another work trip. |
| It starts the return but runs out before arriving. | Try the identical logic on a shorter work route, then compare the point where each return starts. |
| It arrives and charges but never works again. | Follow the next pass through the loop and read the active condition. |
Make one trip short enough to observe in full
- Choose the robot that stopped. For a Waterer, observe its watering trip. For a Gardener, watch its planting job. Keep that job as the ordinary branch. A Collector's full-cargo decision belongs to that profession's example.
- Give charging first choice. In a repeating block program, use the supplied low-power check in Peaceful or assemble an available battery test in Balanced. Put the recharge action on that path and the ordinary job on the other. In Harsh, follow the priority in the official Collector example and use the commands the selected robot's Workshop offers.
- Watch the branch, the trip and the next action. Start with a nearby job. Observe the battery reading at the decision, whether the robot leaves for the base, and whether normal work resumes. Then try the usual job location with the same program. The first route gives you a working comparison if the farther one fails.
The fix works when the selected robot returns with enough power to reach recharge, then resumes its own job without an intervention. Repeat the check at the farthest area you intend it to service.
Use the comparison to adjust timing before rewriting the rest
If the near run works and the far run starts charging but never reaches the base, there is a useful difference in return margin. Shorten the work route or start the return earlier if your editor exposes a suitable condition. The Steam store uses battery < 25 as an illustration of the game's vocabulary. It gives no safe percentage for every trade or distance. Watch the selected robot's actual reading rather than adopting 25 as a rule for the whole team.
If both runs ignore the return, read the first battery decision with the live condition display. Test whether the decision is reached between jobs. A robot running a repeated work section can keep choosing it if the battery test lies outside that section. After it charges, check that the ordinary job remains on a reachable branch so a working return trip doesn't leave the robot permanently idle.