GoreBox crashing on startup

Work through these in order. The early steps clear the common causes; the later ones are for specific cases.

By Usman Shafqat · Updated 2026-10-03

GoreBox can crash during startup or while loading a map. Common causes are low free memory, a corrupted or partial install, and a map too heavy for the device. Try the fixes in this order; the early steps clear the common causes and the later ones handle specific cases.

Android

1. Restart the phone

Obvious, and it clears the RAM that GoreBox needs. The game wants a lot of memory at launch while it loads assets. If a dozen apps are sitting in the background, it can get killed before the menu appears.

2. Check free storage

The 16.5.3 xapk is about 683 MB and unpacks to more, and the game needs headroom to write saves and Workshop content. Low free storage can contribute to crashes, particularly on first launch after an update when assets are unpacked. Clear space and try again.

3. Confirm your Android version

Minimum is Android 7.1. On 7.x devices it will install but crash on launch on some chipsets. If your phone is that old, there's no fix beyond an older APK version from Uptodown's archive, which will lack current features.

4. Clear the cache, then data

Settings → Apps → GoreBox → Storage → Clear cache. Try launching. If it still dies, come back and clear data. That wipes local settings (your account and purchases are tied to Google Play and come back), and it can resolve startup crashes caused by corrupted local data after an update.

5. Update, or reinstall from Google Play

Crashes right after a patch (reported widely on the F²Games Discord after 16.4 and 16.5) often trace to a partial update. Uninstall fully, then reinstall from the Play Store, or from one of the two mirrors on the GoreBox APK page. Don't reinstall from a random APK site; a mismatched build is one of the main causes of the problem you're trying to fix.

6. Lower the settings before it crashes

If the game reaches the menu and crashes when a map loads: Settings → Graphics. Drop shadows, set the ragdoll limit to 10 or lower, turn off blood decals, and load the Canvas map on the Void preset first, since it has almost nothing in it. Then raise things one at a time.

7. Turn off battery optimisation for GoreBox

Some phones, especially Xiaomi, Oppo and Samsung with aggressive power saving, kill the game during loading. Settings → Battery → App power management → set GoreBox to unrestricted.

8. Free up RAM

The community wiki lists 6 GB as the comfortable amount. On 3–4 GB phones the game runs, but only if nothing else is open. Close browsers and social apps before launching, and avoid Workshop maps with high object counts.

PC (Steam)

9. Verify game files

Steam → Library → right-click GoreBox → Properties → Installed Files → Verify integrity. This catches corrupted downloads, which are the usual cause of "crashes to desktop with no error".

10. Update graphics drivers

Unity games are sensitive to old drivers. Update through GeForce Experience, AMD Software, or Intel's driver tool, then reboot.

11. Launch in windowed mode

Right-click GoreBox → Properties → Launch Options → add -screen-fullscreen 0. If it now starts, the crash was a display mode issue; switch to borderless in the settings menu afterwards.

12. Check the crash log

Unity writes a Player.log to %USERPROFILE%\AppData\LocalLow\F2Games\GoreBox\. The last few lines usually name the problem. A "DllNotFound" or Photon line means a corrupted mod folder or leftover Photon settings; delete the mod folder and verify files again. Post the log in the F²Games Discord if you're stuck.

What players report by device class

These are community reports, not our own tests: gathered from the F²Games Discord help channel and Google Play reviews for 16.5.x, September 2026. Patterns, not guarantees.

If it crashes at a specific point

Common questions