Getting Started & Modes
Choose a programming mode, teach Bip its first job and learn how to read a changing world.
- Choose Peaceful, Balanced or Harsh
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.
- Start your first robot in Peaceful
Open the Workshop in Peaceful and inspect the tests already supplied for the robot. Use them to tell when a simple action will run, then watch the robot to see the matching situation in the world.
- Where to start on Noma
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.
- Use pioneer plants before flowers and trees
Start with pioneer plants where the current soil needs preparation. The official description presents a progression from pioneers to flowers and then trees. Observe what changes before expecting later plants to take over a barren area.
- Read a threat’s cause, countdown and remedy
Open the active threat and read its cause, countdown and remedy before editing a robot. The official description says each threat provides those three pieces of information.
- Check whether an Ark pantry loop can run alone
Test the pantry as a closed cycle. The developer describes the Ark as a system where nothing comes in or leaves. Leave the robots to work for a complete cycle and look for any stock that shrinks without being replaced.
- World order and first checks
The route goes from Noma to Thalassa, then Twilight, Sylve and the Ark. Wake the current world to reveal the next one.
Use one job to decide how much programming you want
Choose a mode by how you want to set up the first decision. In Peaceful, start by reading a supplied test and identifying which action follows it. In Balanced, draw out or describe the choice before assembling the blocks yourself. In Harsh, read the indent and the order of the branches the same way you read the blocks. The official Collector example provides a shared example of battery, cargo and collection, but each mode gives you a different way to express or inspect those choices.
If the quickest way to get started is to see a robot perform visible work, begin with a supplied test. If the question you want to answer is why an action runs for one state and stays idle for another, blocks let you build and read the decision. If your aim is to express the program as text, use Harsh and copy the sample from the guide with its branch indentation intact. Verify which mode is shown on the save you are actually playing.
Finish one loop on Noma before adding jobs
Start with Bip and a task with a visible end. For a collecting job, observe one pickup, the next cargo or battery transition and what the robot does after that. If it completes the planned cycle, keep it as a known starting point while you add a planting or maintenance job. If the action never runs, read the Workshop state before moving to a different location. If it runs and makes no useful change, check the action's target in the world.
At a planting patch, look for the transition from pioneers to soil suitable for the next plants. Keep the first working area small enough to compare with a barren area. When flowers are available, test them in the prepared patch and observe the result before extending the route. If a timed threat is active, use the threat information to decide whether you should interrupt that test.
Use signs of progress appropriate to the job
A working first robot is one you can leave to repeat the assignment. A working plant succession is a patch that supports the next stage. A working threat response is an observable change before the countdown ends. A working Ark pantry is a cycle that replaces its consumables as its own robots use them. These outcomes call for different checks. Follow the guide for the result you are missing and return to the choice of programming mode only when you want a different way to author the next decision.
When looking at a shared guide or screenshot, check its programming mode before copying the controls it shows. A Harsh example can explain the order of a decision even when you are using Balanced blocks. The guide for your own mode shows how to express it in your editor. If the advice assumes a different mode, use its description of the desired behavior and find the matching setup for your save.