Why loading into a map can fail
Official: Kefir’s loading-and-freezing help article, checked November 9, 2026, recommends checking connectivity, restarting the game and Steam, updating the graphics driver, and verifying installed files. These are troubleshooting actions, not a diagnosis that every stuck map has damaged files. We have not reproduced the symptom in game or measured how long a successful load should take.
First separate three observations: a frozen loading screen, an application that exits to the desktop, and an error that returns you to the map. Also note whether every destination fails or only Looty Bay. This is our reporting method, not a hidden game mechanic. An exact message gives support more useful evidence than “not working,” especially when a different destination still opens.
Step by step: use the smallest relevant check
Begin with the official news hub and the communities listed by Kefir. Look for a recent notice naming your region and the time of your failure. This site is a dated evidence snapshot, not a live monitor. If a matching outage is announced, local repairs cannot establish that the service has recovered; retry after the developer’s update rather than inventing a recovery deadline.
Next follow the official loading checklist. Check ordinary connectivity, close the game, restart Steam and the game, and check your graphics driver. In the Steam library, open ROB RUN’s Properties, choose Installed Files, then Verify integrity of game files. Record which action you completed and retry the same destination. Change one thing at a time so a successful retry is not attributed to an unrelated adjustment.
If an error code appears, use Kefir’s error-code article instead of treating the loading percentage as a code. Official: E-0124 concerns internal asset loading, while E-0301 and E-0302 indicate an outdated version. The listed responses are file verification for the former and restarting Steam to update for the latter. Those distinctions do not prove that a screen without a code has either fault.
If it still will not load
Prepare a short support report with the destination, region, server identifier if visible, local time and time zone, exact screen text, and whether the application stayed open. Include your PC specifications and a screenshot with private details hidden. The same test repeated after each change is more useful than a long list of settings changed together. Use the official help center rather than our editorial contact for account-specific investigation.
Do not delete configuration folders, edit the registry, disable anti-cheat, or buy a “loading fix” on the strength of this page. We have no verified Looty Bay-specific repair involving those actions. A successful retry on one machine is an observation, not proof that all players or worlds recovered. Likewise, remaining stuck does not by itself establish a ban, a wiped base, or lost money.
Keep nearby symptoms separate
Use the status-information guide if that exact wording appears; use the shader guide if the screen explicitly mentions shader compilation. A crash belongs in the crash checklist instead. Keeping these symptoms separate avoids applying advice for an application exit to a game that is still waiting for a response. The related links below cover those branches without promising that they share one cause.