SandboxAPK

GoreBox crashing on startup

Work through these in order. Most crashes are fixed by the third or fourth step.

Updated 2026-09-07

GoreBox crashing on startup is the problem players search for more than any other, and it is almost always one of a few things: not enough free memory, a corrupted install, or a map that's too heavy for the device. Try the fixes in this order, starting with the fixes that solve it most often.

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 app is around 120 MB, but it unpacks more than that and it needs headroom to write saves and Workshop content. Below 1 GB free is where crashes start. Clear some 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 fixes a large share of startup crashes after an update.

5. Update, or reinstall from Google Play

Crashes right after a patch usually mean a partial update. Uninstall fully, then reinstall from the Play Store. Don't reinstall from an 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 smallest map (Plains or Chamber) first. 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.

If it crashes at a specific point

Where it crashesLikely causeFix
Splash screenCorrupt install or old AndroidSteps 4–5
Loading a mapMemorySteps 6–8
Spawning many GoreDollsRagdoll limitStep 6
Opening WorkshopNetwork or storageCheck connection, step 2
Opening multiplayerRemoved featureSee multiplayer page

Common questions

GoreBox crashes on BlueStacks. Same fixes?

Mostly. Also raise the emulator's RAM allocation to 4 GB and switch the graphics renderer between OpenGL and DirectX in BlueStacks settings.

Will clearing data delete my skins?

No. Purchases and unlocked cosmetics are on your account. Custom maps you made and didn't upload to the Workshop will be lost, so upload or back them up first.

The game says my account is banned and I never played multiplayer.

That was a known bug in early 2025 tied to account IDs. Appeal through the game staff Discord linked from the F²Games server.