Fixing common BAR crashes and keybind bugs

Crashes during large fights with raptors and scavengers

BAR handles thousands of units on modest hardware when everything runs smooth. The crash pattern most players hit involves specific unit types in large engagements. Raptors and scavengers cause the most reported crashes, especially when fights push past three to four thousand units on screen.

A 3060 Ti with 16 GB of RAM and a modern multi-core CPU runs BAR well under normal conditions. If you are still crashing with those specs, the issue is usually tied to the pathfinding load from fast-moving units rather than raw hardware limits.

Try reducing the pathfinding thread limit in settings or turning off certain unit types in large team games if the host allows it.

Keybind stuck moving camera to the same spot

Sometimes a key combination like Shift-Q starts snapping the camera to a fixed map position. This happens in every lobby, not just one game. The cause is usually a corrupted or accidentally saved keybind.

The fastest fix is to reset your keybinds. Go into the settings and switch your keybind layout to a different preset, then switch back. This flushes out the stuck mapping. If the problem persists, check whether keydebug mode is active, as that can interfere with normal keybind behavior.

False alt account detection

BAR occasionally flags a legitimate player as an alt account. This blocks the player from queueing into matches. The player did nothing wrong. The detection system sometimes picks up false positives from shared IP addresses or hardware signatures.

If this happens to you or a friend, open a support ticket through the community channel. A moderator or developer can review the flag and clear it. Do not try to fix this yourself by reinstalling or changing settings. The issue only resolves from the server side.