Choose Peaceful, Balanced or Harsh

In Savebot: The Last Garden, choose Peaceful if you want the game to provide useful tests, Balanced if you want to build those tests yourself with blocks, or Harsh if you want to write the program line by line in the game’s Python-like language.

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

Steps

  1. Decide which part you want to learn first. Peaceful keeps the focus on deciding what the robot should do while giving you useful tests. Balanced puts the loop and tests in your hands using the visual editor.
  2. If you already write code, try Harsh to build the same decisions as lines. Plan to insert game-specific commands from the Workshop. A function from another Python program is unlikely to match the available vocabulary.
  3. Pick a small first goal for the mode you choose. Build or inspect one Collector behavior, then run it and trace the first condition. Use that experience to judge whether you want more or less support.

How to tell it worked

You know how conditions are supplied in your chosen mode and which editor you will use for the first robot.

If you are still stuck

The developer describes the mode choice at the start. If you need to change an existing save, read the option the current game shows before assuming you can switch mid-world.

Compare what you actually build in each editor

Use one job to compare the modes. Suppose you want a Collector to stop collecting when it has no space and complete a recycling delivery. In Peaceful you can look for a supplied test and see how the action depends on it. In Balanced you set up the condition and attach the action yourself. In Harsh you express the choice in the game's text syntax. Forgeur Games gives an example in which a recharge check goes first, a full-cargo check goes second and ordinary collection occupies the remaining case.

Peaceful is a practical starting mode if you want to see how battery and cargo affect a working routine before designing the tests. Read what a supplied test detects and choose a situation that makes its result change. You can still learn to tell which robot ran which action. That skill transfers when you later decide to build your own conditions.

Choose Balanced for visible control over the decisions

Balanced is useful when the part you want to try is designing the program. Start with a short description of which branch should run. Put the battery check in front of the cargo check and read the sentence below the block bench after assembling them. If the sentence appears to describe a collection action regardless of cargo, you have a specific block layout to inspect. This mode lets you work on order and nesting without writing a text command.

Harsh makes sense when you want to express those same decisions line by line. It uses a Python-like syntax and actions from the game. Select the actual in-game command if you are unsure how a method is spelled. The error display helps when a word is unknown, and the running line gives you a place to look if the program validates but behaves surprisingly.

Test your choice with a clear end point

Use three states for a first Collector comparison: ordinary collection, a full load with enough power and a low battery. Look at one decision in each state. If you can explain the result, the mode gave you a way to do the job. If you spend the session struggling with syntax and mainly want to understand world conditions, the visual editor may fit the next test better. If you can read the supplied tests but want to control how they combine, build the same job in Balanced when starting a suitable save. Check the current game's options before assuming you can convert an existing save between modes.

If you are comparing across modes, use the same intended job and stop after one complete cycle. The part to compare is what you needed to author in each mode and what you could inspect afterward. Changes to the place or the robot's job can hide that difference.

Related tasks

Sources