Read the selected robot’s live sensor values

In Savebot: The Last Garden, run the program and inspect the value shown next to a condition block for the selected robot. Forgeur Games says the value is live while the program runs.

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

Steps

  1. Select the robot that showed the problem, particularly if several robots have the same program. Open its Workshop and find the condition that should trigger the action.
  2. Run the program and watch the number or state beside that condition. Compare it in two situations, such as before and after cargo fills, rather than assuming one snapshot describes the entire run.
  3. Use the active line or a breakpoint to match the reading to a branch. Fix the condition if its reading never crosses the test you designed. If it does cross, inspect whether the action is nested where you intended.

How to tell it worked

You can explain the robot’s action using the reading from that robot at the time of its decision.

If you are still stuck

If the number seems constant, check that the relevant robot is selected and running. A general sensor list does not replace the actual value seen by its program.

Match the displayed value to the robot making the decision

Open the selected robot's Workshop and find a condition in the action path you are investigating. If two robots share a program, start with the one that displayed the unexpected behavior. A Collector with plenty of charge and one on low battery will naturally choose different actions. Observe the indicator while the selected program runs and tie the first reading to a visible world state, such as a partly filled load.

Change the state by watching that robot perform its ordinary work. Look again when it fills or when another clearly relevant condition becomes true. Keep the same robot selected during the transition. Note when the value changes and compare it with the action the robot chooses. There is no need to infer a numeric threshold from the fact that a single value appeared beside a condition.

Separate an unchanged reading from a choice made earlier

If you never see a change, first verify that the world state you are comparing actually differs. Check that you chose the relevant condition, such as the full-cargo check, and that the selected program is running. When useful, choose a stronger contrast instead of waiting on two similar states. Use the value at the moment the decision happens rather than relying on what the world looked like after the robot moved.

If a reading does change but the action is surprising, watch whether that condition was reached. The low-battery test can choose recharge before the code gets to the cargo test. A normal full reading at that moment can coexist with no recycling action, because the earlier decision took priority. Use a breakpoint at the controlling decision if the two states are hard to separate during a fast run.

Diagnose what happens after the right action starts

If the condition is reached and the robot enters the intended branch, keep observing until you see the result. A cargo reading can explain why a robot chose to leave for recycling. The actual drop-off is a separate check of the target and route. If the expected result never arrives, leave the working action choice in place and inspect where it goes.

Write a short comparison that you can repeat: selected robot, condition, first and second states, observed values and resulting actions. Use that comparison for the next test after an edit. This also gives you something concrete to share if its readings appear inconsistent. A description of which condition was visible and what the same robot did gives more information than a snapshot of the number alone.

Related tasks

Sources