Where to start on Noma

In Savebot: The Last Garden, start with Bip and one repeatable job in the Workshop. Noma begins with a sleeping planet and companions that do not know what to do yet. A robot that completes one visible task is easier to build on than a team with several untested jobs.

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

Steps

  1. Identify the active robot and open its Workshop. Decide on a job with a visible result, such as collecting and delivering something that can be recycled.
  2. Teach the action and give it a repeat or condition if your mode asks you to build those. Run one short cycle and watch for a specific result before moving on to water, repair or more robots.
  3. As new robots and jobs appear, keep each first test small. If progress stalls, find out which robot is missing its expected action before editing every program.

How to tell it worked

At least one robot repeatedly performs its intended job while you can see what changes in Noma.

If you are still stuck

If the robot is still doing nothing, inspect the actual program and current conditions in the Workshop. The first world teaches finite actions and repeatable routines through the robot rather than direct player control.

Use Bip to establish a working first job

Bip is the first robot named in the developer's Workshop description of Noma. Begin with one task you can see from start to finish. A small collection route lets you distinguish choosing to pick something up, actually collecting it and moving on to the next action. Select Bip before opening his program. If a different robot later moves in the same area, keep the observation on the one you are editing.

Pick a recognizable target for the first run. Watch for the pickup and for a change in the world or cargo on the same robot. If the expected action is never reached, read the selected program and any condition that comes before it. If the action runs while the target is unavailable, keep the same program while you test a reachable example. That tells you whether to change the job or the scene where you tried it.

Decide which second job solves the current bottleneck

If collection works but nothing useful happens with the collected material, follow that material through the next step before assigning a second Collector. If a robot makes a single successful trip and then idles, check where the repeat or next condition takes it. In Balanced, the Workshop sentence helps when an action sits outside the section that should repeat. In Harsh, follow the active line in the running loop to check that it returns to the decision.

For a planting job, choose one small area and check whether your pioneer plants have changed the soil enough for the next plant stage. If a hazard appears, use the active threat's cause, countdown and remedy to decide what action takes priority. Keep the successful opening job narrow enough that you can return to it after you inspect the threat.

Build up from a result you can recognize

A useful first session on Noma leaves you with an action you know how to run and observe again. Record the initial state that starts it, what you saw it do and what allows it to repeat. When a later task stalls, return to the first point where the world or robot looks different from that observation. A newly active robot and a working program each require their own check. Once more than one robot is moving, test a new job while the earlier one is unchanged. Keep the new routine only after it finishes once and is ready to run again.

If you are returning to Noma after stopping mid-task, begin with the spot where Bip last made visible progress. Check whether the original job still has a usable target there before replacing it.

Related tasks

Sources