Check a block program using its sentence

In Savebot: The Last Garden, read the sentence below the block bench. Savebot describes the current program there. Use the sentence to check the order and nesting of your blocks before a longer run.

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

Steps

  1. Take a program whose behavior you can describe in one line. For a Collector, the intended idea is to keep checking what it needs before collecting again.
  2. Compare that intended sentence with the game’s readback. Look for actions attached to the wrong condition or actions that sound like they occur every time.
  3. Move one block or change one condition. Compare the old and new meaning, then observe the new branch on a running robot.

How to tell it worked

The sentence matches the action order you wanted, and one actual run follows that meaning.

If you are still stuck

If the sentence is right but the action still surprises you, inspect the selected robot’s live condition. The sentence describes the design. The live reading shows whether its current state should select that branch.

Read the sentence with one expected behavior in mind

Before comparing the generated sentence, write down the intended action in a specific case. For example, with a full load and enough battery, the Collector should recycle. With a low battery, recharge should take priority. A short statement with a condition and the expected action makes it easier to see which part of the generated sentence matters. Open the block program for the robot whose job you want to check.

Read the part that describes the test first. Then read the following action and identify where the conditional section ends. If collecting appears after the entire decision, compare that with the intended fallback case. If recycling appears to belong to the recharge case, locate the block attached to the wrong branch. The sentence under the bench lets you see what the current block arrangement says before waiting for every possible condition in the world.

Make one move and compare the two meanings

Keep a note of what the sentence said before you move a block. Change the smallest placement that makes the intended action belong to its own case. Read it back again and check which actions stayed in the same order. If changing a branch also made the repeat disappear from the description, inspect where the moved block sits relative to the loop. A syntax-free editor still requires the program's structure to match the decision you meant.

If the wording seems ambiguous, choose a contrast you can see on the robot. For example, a full load and a partly filled load with adequate battery should give different outcomes in the intended program. Use both cases and check the live condition while running. If the sentence fits your plan and the robot acts differently, verify you are reading the program of the same robot that performed the action.

Verify the readback at a repeat boundary

Observe the first correct action, then watch the program return to a decision. The sentence is particularly useful if an action runs once and the robot then stops choosing useful work. Check whether the action and the condition belong within the repeat. If they do, compare the state after the first action with the state that starts the next one. Preserve the working cases when making any follow-up edit.

When asking another player to inspect your block layout, include the intended behavior and the sentence the game currently shows. If the visible wording already explains the action order, share the one live state where the result still differs. That isolates the remaining issue to a particular choice instead of handing over the entire routine without context.

Related tasks

Sources