In-game event

Update 0.1.3.9: Cleaner Coding API, Smoother UI, and New Credits Screen

Code My Robot Vacuum · published 23 May 2026, 22:38 UTC · build 23381328

All news Players around this date Read on Steam

Hello Coders,

This update focuses on making Code My Robot Vacuum feel cleaner to play, read, and navigate. The biggest change is a coding API cleanup: the old dirt-checking function has been renamed to robot.detect_dirt(), with tutorials, examples, completions, guides, wiki entries, and objectives updated to match.

There are also smoother UI hover animations across many menus, a working FOV slider, a new Credits screen, Workshop/editor tracking improvements for future balancing, and a batch of visual and stability polish.

Major Additions

A clearer dirt detection function

The robot dirt-sensing API has been updated from robot.is_dirty() to robot.detect_dirt().

This should make scripts easier to read and better match what the function actually does: checking whether the robot can detect dirt. All related learning material has been updated.

This change affects the examples and documentation around dirt detection, so new players should see the correct function name consistently while learning.

New Credits screen

A Credits screen has been added to the Start Menu.

It includes an animated scene presentation, auto-scrolling credits text, a dedicated back button, and an editable credits file for future updates.

Gameplay & Feel Improvements

The FOV slider now works properly. Camera field-of-view changes should now apply correctly from the Settings menu.
Tile hover tooltips behave better near the camera button. The tile tooltip now hides when the mouse is over the camera mode button, preventing jitter and unwanted tooltip overlap.
Grid visibility and shader stability have been improved. Several level scenes received small grid positioning adjustments to reduce visual artifacts, with shader safety improvements to avoid edge-case rendering issues.
Level selector transitions are cleaner. Fade overlays are now cleaned up more reliably, reducing the chance of lingering transition visuals.

Creator / Workshop / Editor Improvements

Better Workshop and custom map insight for future updates

The game now records more useful, privacy-aware analytics around Workshop and custom map activity, including custom map plays and editor actions such as saving drafts, creating new drafts, playtesting, and publishing.

This does not add a new visible editor tool by itself, but it helps identify how players use custom content so future Workshop and editor improvements can be better targeted.

Custom map plays can now be tracked by source.
Workshop editor actions can now be tracked more consistently.
Playtest and publish events now include more useful context, such as map details and publish status.
Analytics behavior respects the relevant privacy setting toggles.

UI / Quality of Life

Smoother, more consistent button hover animations

Buttons across several UI screens now share a more consistent hover feel. Hover scaling, rotation, focus behavior, click handling, and cleanup have been centralized so menus feel more polished and less uneven from screen to screen.

This affects all areas.

Many buttons now use the same “juicy” hover behavior.
Duplicate hover logic was removed from multiple screens.
Some upgrade buttons intentionally skip the global hover animation where it would interfere with their layout.
Changing the code editor font family now applies editor-specific settings immediately.
Display settings are now only reapplied when they have actually changed, reducing unnecessary display reconfiguration.

Fixes & Polish

Fixed an issue where fade overlays in the Level Selector could remain active longer than intended.
Improved cleanup for UI hover tweens and dirt spawn fade behavior.
Improved shader safety around ellipse rendering edge cases.
Fixed analytics progression calls to match the expected API format.
Improved tracking accuracy when purchasing upgrade levels.
Removed an old backend SDK and replaced it with the current analytics integration.

Closing Note

This update is mostly about polish, consistency, and making the game easier to maintain and improve. The coding API is clearer, the UI feels smoother, settings behave more reliably, and the new analytics hooks should help guide future balance, progression, and Workshop improvements.

Thanks for playing, testing, and sharing feedback.

Other announcements

All news

In-game event13 Sep 2026Campaign Results, Rebalanced Stages 5–10 & Bug FixesThis update brings a new Campaign Results overlay , a substantial rebalancing pass for stages 5–10, and several improvements to tutorials, the code editor, and campaign progression. Major Additions New Campaign Results Overlay Campaign stages now end with a dedicated results screen, giving you a clearer summary when you finish a stage and a more polished transition before continuing your campai…In-game event18 May 2026Update 0.1.2.9: Breakpoints, Step-by-Step Debugging, and Better Python SupportHello Coders, This update makes coding and debugging your robot programs much clearer. You can now set breakpoints, step through code one statement at a time, get better support in external Python editors, and receive clearer feedback when upgrades become available. Major Additions Breakpoint Debugging The code editor now supports breakpoints. Set a breakpoint, run your program, and execution w…Game update18 May 2026Update 0.1.3.3: Battery Failure and Rich Guide PagesHello Coders, This update makes failure states clearer, learning tools more useful, and stage transitions smoother. The biggest change is battery depletion: when your robot runs out of power, the game now clearly stops execution, shows a failure state, and gives you a clean restart path. The in-game Guide also received a major usability pass with rich formatting, highlighted Python examples, co…