Make a robot answer a Sylve help signal
In Savebot: The Last Garden, program a sender and at least one responder. Forgeur Games says every robot hears the help call for 30 seconds, while only robots you have taught to respond actually answer.
Full Steam release unless a source specifies the demo. Evidence checked . Guide updated .
Steps
- Teach one robot the help call in the situation where you need assistance. Keep the first test separate from unrelated alerts so the actual event is easy to identify.
- Teach a second robot a response and decide what action should follow the signal. Check its program while the sender calls for help.
- Run a test and look for a change on the responder during the signal window. Compare the sender’s action with the responder’s live condition if nothing happens.
How to tell it worked
The receiver performs a taught response within the visible help-call test rather than continuing its previous program unchanged.
If you are still stuck
Hearing is separate from responding. If the sender called but nobody acted, check whether the responder has an applicable help branch and whether the signal is still within the announced 30 seconds.
Assign a sender and a responder you can observe together
Choose the robot that should call for help and one other robot to answer. Give the sender an event you can identify as the trigger, then teach the other robot what action to take when it detects the help signal. Keep the first test small and choose positions that allow you to watch both. The developer says every robot hears the call for 30 seconds. The programmed response is what makes the intended helper act.
Start the sender and identify the moment the call is issued. Watch the selected responder's relevant decision before the 30 seconds pass. Record the action that would count as an answer in this test. If the helper is already working near the sender, follow the active program rather than judging by position alone. It can be nearby for a different task.
Diagnose where the call stopped leading to action
If the sender runs but never reaches the call action, trace the event or condition that should start it. If the call is issued and the responder never checks it, watch the responder's current job and determine when it returns to the decision that can answer. A check after the announced window can explain why a task that eventually resumes never responded during the call.
If the responder checks during the available time and takes an unexpected action, inspect the taught branch and the target. If it chooses the intended response but fails during travel or work, keep the successful communication test and follow the resulting job separately. Issuing the signal, selecting a response and completing the helper's job are three observable outcomes.
Test the solo case before asking several robots to respond
Use the same sender and responder for a second trial. If the first worked only while the responder was idle, try a relevant ordinary job and inspect when it reaches its help decision. If it never checks in time while working that job, make the next change where you observed the delay. For a longer setup, test each additional responder distinctly so another robot's success cannot hide the behavior you are adjusting.
Record the send time, the responder's starting action and when it chose a response. The 30-second signal window describes how long the call is heard. Track arrival at the job or completion as its own result. This helps separate a responder that acted on time from one whose actual job remains unfinished.