Check the game’s current message and Kefir’s official announcements before assuming a local fault. We have not verified an official per-server live status feed or fixed maintenance timetable. An old announcement cannot establish whether your server is online now.
Maintenance and server status
Check Steam news and the official channels linked from the store. Note the time, region and server named in any notice. A developer post on Steam reported repeated DDoS attacks causing connection errors and lag during launch week; it is historical evidence, not proof that every later loading problem is an attack.
Kefir’s November 4 announcement described planned new EU and East US server openings. A new-server opening is not a maintenance appointment or a universal wipe. For the federal raid and changing servers, see wipe and servers.
Waiting for status information
Players report this message while attempting to enter locations, sometimes returning to the map. The exact cause is unconfirmed. Note whether the message affects one location, all locations, or everyone in your party; this helps distinguish the symptom without claiming a diagnosis. If an official incident is ongoing, check for updates before repeatedly changing settings or servers.
Stuck on changing region
Some players report the game hanging on a changing-region screen. Kefir has not, in the sources checked, acknowledged this specific message or published a dedicated fix. Fully close the game, confirm that Steam is online, and relaunch. If the screen returns, run Kefir’s general loading steps below, including verifying game files. Community guides suggest the same file check; that is community-reported and not a guaranteed repair.
Changing region is not the same action as surrendering to move to a friend’s server. Do not use a server move as a loading fix, because it can carry consequences described in the friends guide.
Loading screen or compiling shaders stuck
- Check that your internet connection works.
- Restart ROB RUN and Steam.
- Update the graphics driver.
- In Steam, open the game’s Properties → Installed Files → Verify integrity of game files.
These are Kefir’s general loading and freezing steps, not a guaranteed shader-specific repair. One player reported success resetting a graphics software shader cache, while others reported that attempted fixes did not work. One other player thread reports that resetting the NVIDIA cache did not help. A community suggestion is to clear the DirectX Shader Cache with Windows Disk Cleanup; this is optional and not confirmed by Kefir, and the game has to rebuild the cache, so the next start can take longer. The cause and success rate remain unconfirmed. Record the exact screen and any error code if you need to contact support.
Is ROB RUN on console?
The Steam store lists Windows. A console release, release date, controller support and Steam Deck compatibility were not confirmed by the sources checked. A lack of a verified announcement does not rule out a future release.
Still unable to connect?
Compare your computer with the official minimum requirements, keep the game updated and check whether friends on the same server have the same issue. If an invitation specifically says your friend is on a different server, consult joining friends; a server move can carry consequences and is not a general loading fix.
Use the error code to choose a next step
| Code | Kefir’s description | Suggested check |
|---|---|---|
| E-0101 / E-0110 | Startup configuration or data cannot be downloaded from the server. | Check the connection and whether websites load. |
| E-0201 | An established server connection was lost. | Check the connection and restart the game. |
| E-0301 / E-0302 | The game version is out of date. | Close the game, restart Steam and update it. |
| E-0124 | An internal asset-loading error. | Verify game files in Steam. |
These are distinct from the unconfirmed cause of a screen that displays no code. If an error persists, save its text or a screenshot and report what happened before the failure to Kefir support.
What to include in a support report
Record the exact message or code, the server and region, and when the problem occurred. Note whether it happens at launch, while changing region, when accepting an invitation or when entering a particular location. A screenshot can preserve the wording if the screen disappears.
Include the steps already tried and whether other players on the same server see the same symptom. This gives support a useful account of the failure without assuming that a shared symptom has a single cause. If an announcement names another region or describes a new server opening, it does not by itself confirm an outage on your server.