Highlights
This report covers the first two weeks of November 2026, from 1 to 14 November.
- Practice rounds have begun: this week, from 16 November, there are two, one for solo competitors and one for pairs.
- Pybricks blocks: a ninth editor, where a LEGO robot program is built from blocks and runs on the hub. The blocks, their help and the colour names are in Croatian on Croatian pages.
- The hub, live: the hub panel draws the ports as they sit on the hub, names the motor or sensor on each one and shows its readings while the robot is being built. A hub connects over Bluetooth or a USB cable.
- The running block lights up: a Logo blocks program shows which block is running, at a speed the student chooses, and marks the block where an error happened.
- From the error to the line: a click on a console line that names a place in the program moves the editor there.
- Input in the console: a Python program that calls
input()asks its question in the console and waits for the answer. - Administration: plans with a free base plan, organization invitations, and adding competitors to an event in bulk.
New features
Studio (students and teachers)
- Pybricks blocks editor. A toolbox with the hub, motors, sensors, movement, timing and colours, a preview of the generated Python, and the same Run, console and hub panel as in the Pybricks code editor. The start block chooses the hub: SPIKE Prime, SPIKE Essential or Robot Inventor. A motor or sensor block warns while its setup block is missing, and a colour is picked with hue, saturation and brightness sliders.
- Help for Pybricks blocks. A help drawer with a search shows each block as a picture, with what it does and the Python it makes.
- A robot program to start from. New Pybricks programs, blocks and code, start with a small robot program, and both editors link the robot's building instructions.
- Ports and sensors in the hub panel. The ports are laid out like the hub, each with its device's icon and reading. A measured colour shows as a colour chip beside its name, the force sensor and the light matrix have their own display, and the colour sensor switches between its modes. A Live sensors window keeps every reading moving.
- A display function per port. A cog on a port card opens a small Python function that turns the raw reading into what the student wants to see, for example centimetres instead of degrees.
- Easier hub connection. The Studio first tries the hub it remembers, a hub connects over a USB cable as well, the panel shows the programs stored on the hub, and the hub panel and the console can be hidden to give the code more room.
- Pybricks code editor. One-line Croatian summaries above the Pybricks documentation, Python's built-in functions and the program's own names in completion, and colours for Pybricks classes and functions.
- Run highlight in Logo blocks. While a program runs, the block being run is outlined, and a Speed select slows the run down so that every step can be followed. When the program stops on an error, the block that caused it stays marked.
- Console lines that lead to the code. Compiler errors and warnings in C++, Python tracebacks and errors from a Pybricks hub are links: a click, or Enter from the keyboard, puts the cursor on that line of the program.
- Python asks in the console. In the Python code and blocks editors a program with an empty input pane asks for each
input()in the console. - Events. The home page lists the student's events in two columns, and entering one opens the event page. When the connection drops, the event page catches up as soon as it is back, and new questions and announcements keep their New tag until they are seen.
- Look. Classic blue is the default palette, the code colours can be chosen separately, and focus outlines and link colours read well in every palette, light and dark.
- Console and problem statements. The console has a clear button, and the statement text steps through eight sizes instead of three.
- Programs from the previous Studio. Programs saved on the device in the previous Studio appear in the new one.
Administration (organizers, mentors and admins)
- Plans. Plans replace licence seat types, and the base plan is free. The organization's settings show the current plan.
- Organization verification. An organization is created without a licence key and asks for verification from its settings. A verified organization can organize events.
- Organization invitations. An Invitations window on the Users page sends an invitation, lists the pending ones and revokes them. The invited user sees a banner and accepts or declines.
- Competitors in bulk. A modal lists the organization's members with their classes and whether they already compete, filters them by class and adds the chosen ones in one step. Competitors can also be added after the organization has started the event, until its deadline.
- Competition types. A competition records the types of its problems, and the list of competitions has a Type column with a filter.
- Test cases from the competition page. A problem's test cases can be prepared without leaving the competition.
- Event dates. A click on a day or a time sets the start and the end of an event, without an OK button.
Fixes and improvements
Studio
- Safari, iPhone and iPad. The Logo and Python interpreters start in Safari and in every browser on iOS.
- After an update. A page that was open while the Studio was updated asks for a reload instead of failing.
- Dates and sessions. Every date shows in the viewer's time zone, and signing in or out in one tab is followed by the others.
- Croatian. The Studio addresses students with vi throughout, and a program's input is called unos.
- Run and Stop. Run always uses the code the editor shows, and a Stop pressed right after Run always stops a Logo program. A computer without Bluetooth says so.
- Programs on the device. When a program on the device cannot be opened, saved, created or renamed, the home page and the playground say why.
- Layout. A drag of a divider in a short window no longer loses a pane, and the user menu resets the layout.
- Keyboard. Menu links open with Enter, and the code editor's pop-ups are no longer cut off by the header.
- Behind the scenes: more automated tests, and sign-in and the connection to the server were hardened.
Administration
- Times. Every time is shown in the viewer's local time.
- Workshops. The problem pickers list every competition.
Content and documentation
- Administration docs: plans and verification, organization invitations, and adding competitors in bulk and after the start.