How to Report BAR Bugs and Issues on GitHub

BAR uses GitHub Issues for tracking bugs and technical problems. Knowing where and how to report something makes it more likely the developers will see your report and act on it.

Tags: bugs, reporting, github, troubleshooting, beyond all reason

Where to submit bug reports

BAR splits bug tracking across multiple GitHub repositories depending on what part of the game is affected:

Game bugs: Report issues with the actual gameplay, units, balance, or mechanics on the main game repository.
Lobby and launcher issues: Problems with the lobby client, connection, or launcher go to the Chobby repository.
Engine problems: Engine-level crashes or performance issues go to the engine repository.

Each repository has its own Issues tab. You need a GitHub account to file a report, which is free to create if you do not already have one.

What to include in a bug report

A useful bug report has enough detail that a developer can reproduce the problem. The most important pieces are:

Description of what went wrong. Keep it specific. "The game crashed when I built a factory" is better than "it broke."
Steps to reproduce. If you can describe the exact sequence of actions that led to the issue, include it.
Game version. Check which build you were running when the bug occurred.
Screenshots or replays. Visual evidence goes a long way. A replay file showing the bug is the best proof you can submit.
Log files. For crashes, the game log usually contains the technical details developers need to find the root cause.

Check existing reports first

Before filing a new issue, search the existing issues in the relevant repository. Someone else may have already reported the same thing. If the issue exists, you can add your experience as a comment instead of creating a duplicate.

Search using keywords related to your problem. Unit names, error messages, and the map name are all good search terms.

Why reporting matters

BAR is open-source and community-driven. Every bug report helps the developers prioritize fixes. The more detailed and reproducible your report, the higher the chance it gets addressed quickly.

Even issues that seem minor get noticed. The development team reads through GitHub Issues regularly and uses them to plan which problems to tackle in each patch.

Creed of Champions

Community members who contribute to BAR development and bug reporting embody the kind of cooperative spirit that Creed of Champions values. Players who give back to the game make it better for everyone.

[Crd] Gaming actually fulfills a human purpose here - cooperation, mutual upbuilding, fun and striving for greatness together. Instead of random anonymity, you meet, learn from, and enjoy real people.

Better teammates, better games. Win with skill, teamwork, and respect.