Routine

The routine represents the execution of the user's code in a specific arena. The routine panel, located at the top-left corner of sBotics, allows you to start, stop, and restart the simulation. Routine information such as score, time, and multipliers is displayed at the top center of the screen, as shown below.

To start the routine, click the “play” icon. To stop it, click the square in the same place. If you want to restart the scenario, use the restart icon (↺).

The console is the main output tool in sBotics, along with the Buzzer and LED components. It allows you to print sensor values, display text, and describe the step-by-step execution of the robot.

You can manually clear the console using the broom icon, and access the detailed log by clicking the document icon, both located on the right side of the panel.

The log file, accessible via the “Document” icon on the console panel, is an external record generated by sBotics. It allows you to create charts, .csv files, and other advanced implementations based on data generated during the simulation.

sBotics uses tiles to score the routine. Each tile has a score value, which is added (or multiplied) to the total score as the robot moves around the arena.

The path, formed by tiles, can be divided into smaller segments called “tracks” using “Checkpoints”. A typical sBotics arena may contain one or more tracks. Leaving the correct track may result in a “Progress Failure”.

As mentioned earlier, the track is subdivided by checkpoints. On the routine panel, checkpoint tiles are marked with orange arrows indicating the direction in which the robot will be repositioned when starting a new attempt from that checkpoint. If the track passes over the same tile in different directions, multiple arrows will be shown.

Thus, the arena below is segmented into small tracks when considering the checkpoints.

If the robot deviates from the expected track, a progress failure counter will appear at the bottom of the interface, indicating the type of failure and the remaining time before penalty. In the example below, the counter shows a failure due to robot inactivity.

When the counter reaches zero, a new attempt starts, forcing the robot to restart.

For track-related progress failures, deviating by more than two tiles results in a “severe” failure, while deviating by only one tile is a “minor” failure. The time allowed to correct the deviation varies depending on the arena setup — 50 seconds for minor failures and 10 seconds for severe failures in OBR competitions.

Note in the images above: a one-tile deviation is marked in orange, while two or more tiles is marked in red.

The routine panel allows you to start new attempts and move on to other tracks if available. It also shows the routine's status in terms of attempts and tracks.

Track	Attempt	Total Attempts
Current track number	Current attempt number within this track	Total number of attempts across all tracks

Note: The attempts panel and the retry/advance features are only available in “line/track”-type arenas.

You can restart the current track or move on to the next one, resetting the robot's position and code.

Note: In some arenas, the “Advance” button is only available after a minimum number of attempts (3 in OBR).

To preserve values between attempts, use static variables: “estatico numero” / “estatico texto” / “estatico booleano” in rEduc or 'static double' / 'static string' / 'static bool' in C#.

The execution report, displayed at the bottom of the attempts panel, logs routine events in two formats: simplified and detailed.

Both reports allow you to recreate the robot's path and identify scoring points and failures. The detailed report is used by the competition system to verify the execution's integrity.

Example of a Report Snippet:

[0:00] Score added;
↳ 5 pts. (×1.00);
↳ 1 @ 1.

[0:00] First time on tile: 0;

[0:05] Passed over tile: 0;

[0:05] First time on tile: 1;

[0:11] Score added;
↳ 15 pts. (×1.00);
↳ 1 @ 1.