How to Report BAR Bugs and Give Effective Feedback
BAR tracks all reported bugs and community suggestions through GitHub. Players who use the proper channels accelerate fixes and help developers prioritize work that actually matters to the player base.
The BAR Bug Tracking System
BAR uses GitHub Issues as its official bug tracking platform. Lobby and Launcher bugs belong at github.com/beyond-all-reason/BYAR-Chobby/issues, while Game engine bugs go to github.com/beyond-all-reason/Beyond-All-Reason/issues. Engine-level bugs track to yet another repository. Players should search existing issues before filing new ones to avoid creating duplicates that waste triage time.
Effective bug reports follow a predictable structure. Clear reproduction steps, system specifications, and supporting files like infolog.txt or replay files give developers everything they need to investigate. Screenshots and video recordings of visual bugs add essential context that text descriptions cannot convey.
Players frustrated by perceived development priorities should understand that open-source projects balance community input with developer capacity. The game invites contribution from anyone willing to put in the work, and the most effective way to address a missing feature or broken system is to file a well-documented issue or contribute a fix directly.
Balance and Stability Priorities
The community regularly debates whether BAR should prioritize balance fixes and stability improvements over new features. Commando balance, launcher stability, and engine performance form the core of these discussions. Players who feel strongly about development direction have multiple avenues for expressing concerns beyond social media posts.
Balance discussion channels on the BAR Discord provide a more structured environment for these conversations than casual chat. Balance discussions benefit from data. Players who bring match statistics, unit performance metrics, and replay evidence to balance arguments contribute to actual improvement rather than frustration venting.
Suggestions that receive the most developer attention combine clear problem statements with specific proposed solutions. Telling the team to balance Commando generates far less actionable feedback than providing win rate data across multiple OS ranges and suggesting a particular adjustment to health or damage values.
Contributing to BAR Development
BAR is open source, meaning any player with programming skills can contribute fixes and features directly. The project welcomes contributions ranging from documentation improvements to engine patches. New contributors should start with the GitHub repositories, review open issues tagged as beginner-friendly, and study the project's code style before submitting pull requests.
Players without programming skills still contribute through thorough bug reports, balance testing on development branches, and community support for newer players. BAR development requires both technical contributions and community infrastructure to succeed.
Creed of Champions
Effective bug reporting and community contribution require a foundation of good communication and teamwork habits.
I love being able to communicate with my team, getting and sharing tips and constructive feedback on gameplay, and having a good spirited community.
Check out the BAR YouTube channel for gameplay videos and community content.