Guide
GoreBox 27 Problems and Fixes: The Complete List
Install failures, performance cliffs, session trouble and controller quirks: every common GoreBox 27 problem in one place, in fix order.

CONTENTS On this page
Most GoreBox 27 problems are six problems in twenty costumes. This page keeps the full list together, in fix order, from reader mail and rack testing for GoreBox 27 official site.
Install and launch
Failed installs are short files or full storage until proven otherwise: verify the 606.2 MB, free real space, fetch on Wi-Fi. A game that will not start on an old phone should be checked against the Android 8.0 floor before anything clever is attempted.
Performance and scenes
Slowdowns trace to scene scale, accumulated wreckage and heat: clear debris, shrink casts, cool the phone. Our performance guide has the per-tier budgets. A world that got too ambitious can always be retired with honours and rebuilt saner.
Sessions and controls
Multiplayer trouble splits into version drift (everyone on the current build, per our update guide), host load (strongest phone hosts) and network (our lag guide's ladder). Controller detection quirks end with pairing at the system level before launching. Nine problems in ten on this page end in one of those three sentences.
Editor and map problems
A map that slows every session down is usually one ambitious structure too honest about its physics: collapse-prone towers near spawns tax every device in the room, every round. Retire the set piece or rebuild it from denser materials and the map recovers. A spawn that drops players into water or debris is a layout problem, not bad luck; move it ten metres and the complaints stop. And a build that looks fine solo but misbehaves hosted is telling you the host's ceiling is lower than yours, which hands you straight to our lag fix ladder for the room-wide version of the cure.
When to stop fixing and restart clean
Some scenes simply accumulate too much history: hundreds of bodies, fields of debris, a world that has been at war for three hours. The honest fix is retirement with honours. Save what you love, close the session, and rebuild the idea at a saner scale in a fresh world; the new version is usually better anyway, because you now know which parts carried the fun. If the game itself, not the scene, is the problem after every cheap check on this page, install the current file over the top from the download page. Your maps and settings survive that route, and it ends more hauntings than any other single step.
Problems that are actually features
A honest section of this list is not problems at all. The bot who will not speak to you after you shot him is not bugged: GoreBox 27 remembers attackers, and a grudge is a system working as designed. The scene that slows down after three hours of war is carrying exactly the debris and bodies you left in it, which is persistence, not decay. The cover that stopped working against a bigger calibre was never cover against that calibre. Half of learning GoreBox 27 is separating genuine faults, which the sections above fix in order, from systems whose honesty surprised you. Only file the second kind under problems once, in GoreBox 27 terms: education.
Quick Answers
What single check fixes the most problems?
Versions: current build on the game, current build on every device in the room.
The game got slower the longer I played. Broken?
Probably physics debt: bodies and debris persist. Clear the scene and restart the session.
Should I reinstall to fix session problems?
After the cheap checks, install the current file over the top. Your maps and settings survive that route.