How to report bugs in BAR through GitHub issues

Where to file bug reports for the BAR lobby, game engine, and launcher, plus which repository handles each type of issue.

Tags: beyond all reason, bug reporting, github, issues, troubleshooting

Filing lobby and launcher bugs

Lobby and launcher issues go to the Beyond-All-Reason/BYAR-Chobby repository on GitHub. This covers problems with the lobby client, matchmaking interface, launcher crashes, and anything related to the Chobby lobby system. Before filing, search existing issues to avoid duplicates.

Include details like operating system, game version, steps to reproduce, and any error messages or log snippets. Screenshots of the bug in action help developers understand the problem immediately.

Filing game and engine bugs

Actual gameplay bugs, unit behavior issues, and engine crashes are filed at beyond-all-reason/Beyond-All-Reason on GitHub. This repository tracks problems that occur during matches rather than in the lobby. Engine-level issues follow the same process under that repository.

Replay files attached to bug reports are extremely valuable. A replay showing the exact moment a unit behaves incorrectly gives developers a reproducible test case instead of relying on text descriptions.

Moderation and ban discussions

Bug reports are not the place for moderation appeals. Players with questions about bans or lobby moderation should use the appropriate community channels rather than GitHub issues. Issue trackers are for technical problems, not social disputes.

Separating technical bugs from moderation discussions keeps the issue tracker focused and searchable for developers. Filing a moderation complaint as a GitHub issue creates noise and delays resolution of actual bugs.

Creed of Champions

"The removal of toxicity, the goal of fun and learning, makes for a refreshing spot to play and spend time. It has also made a game with plenty of complexity a bit less daunting to dive into."

[Crd]