Read a threat’s cause, countdown and remedy
In Savebot: The Last Garden, 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.
Full Steam release unless a source specifies the demo. Evidence checked . Guide updated .
Steps
- Identify which threat is active and note when its countdown ends. Use its stated cause to choose the robot or area that needs attention.
- Read the remedy shown by the game. If it requires a robot action, check the Workshop for the relevant instruction and decide which existing program should handle it.
- Use the current countdown as feedback while you observe the robot. If it seems to ignore the threat, inspect the condition and the selected robot’s live reading.
How to tell it worked
You can point to an active remedy and see whether the robot is carrying it out before the relevant deadline.
If you are still stuck
Different threats can call for different actions. For a solar flare in Twilight, use the world-specific shelter advice instead of applying a response from a different threat.
Read the three pieces of the warning before editing
Open the actual threat and read its cause, remaining time and remedy. They answer separate questions. The cause tells you which world problem you need to diagnose. The countdown tells you when further work will run out of time. The remedy tells you what outcome to aim for. Copy the relevant wording or keep the notice visible while selecting the affected robot or area.
Identify a specific result that would satisfy the remedy. For a Twilight solar flare, use the guide about reaching shade under a sail or mild ground. Seeing a robot begin the trip is an intermediate observation. This case is resolved for that robot when it reaches the intended protection. In a different threat, take the observable goal from that notice before replacing a program. The developer says what information warnings provide and does not give one solution for every world.
Use the countdown to choose the first realistic action
Look at the target and the robots that can reach it. Start with a robot capable of performing the relevant action. Check both the time until it begins to respond and the journey it has to complete. If the current work keeps it busy when the warning is active, use the program to see which decision made it stay where it was. If it leaves immediately and still arrives late, examine how far it had to travel.
If the remaining time is short, run a small response you can observe. Save deeper rewrites for after you have identified what failed. When you have time to test, choose one robot and track it from the trigger to the desired result. If a second robot appears to react differently, compare how it was programmed and where it started before altering both.
Record the first failure so the next warning is easier to handle
If the threat remains active, decide whether your robot missed the trigger, attempted the remedy without completing it or completed an action that did not answer the notice. The active branch and the target in the world support those distinctions. After a successful response, check whether ordinary work resumes safely and identify what the robot should do next time.
Keep the threat's wording, the starting area, the rough time available and what you observed. A case in which the robot recognized the warning and reached protection after the countdown calls for a different change than one in which it never reacted. Use this record to test the same issue if the event recurs.