How to post error logs and report bugs in Beyond All Reason

Finding error logs before filing a report

BAR crashes or misbehaves at some point for every player. The first step before posting about any issue is locating the error log. Error logs live in the game data folder on the local machine. These logs contain the stack trace and context developers need to diagnose problems. Grab the log before doing anything else.

Where to report bugs

Beyond All Reason uses GitHub Issues for bug tracking. The main game repository sits at github.com/beyond-all-reason/Beyond-All-Reason/issues. Lobby-related bugs go to the lobby or launcher repo. Engine-level crashes may belong in the engine repository.

Always search existing issues before opening a new one. If someone already filed the same bug, adding details to the existing thread helps more than creating a duplicate. Include the error log file when posting.

What to include in a bug report

• The full error log file from the game data folder
• A description of what happened leading up to the issue
• Steps to reproduce if the bug is repeatable
• The game version and operating system
• Whether the issue occurs consistently or sporadically

Checking the right repository

Not every bug belongs in the main game repo. Lobby crashes, UI glitches in the launcher, and engine-level rendering failures each have their own tracking location. Matching the bug to the correct repository speeds up the response from developers.

What players say about the BAR community

"One of the few places where you can for sure coordinate with people in matches with a good supportive attitude. Everybody tends to be understanding and constructive." — [Crd] member review