Where Beyond All Reason tracks bugs, which GitHub repo handles which problems, and how to file reports that actually help the development team.
Beyond All Reason uses GitHub Issues to track all reported bugs and problems. The team organizes reports across three separate repositories. The lobby and launcher issues go to the BYAR-Chobby repo at github.com/beyond-all-reason/BYAR-Chobby/issues. Game-specific bugs go to Beyond-All-Reason at github.com/beyond-all-reason/Beyond-All-Reason/issues. Engine-level problems have their own engine repository.
This structure means you need to pick the right repo before filing. A lobby crash and a unit behavior bug land in completely different tracking systems. Posting in the correct place gets your issue seen by the right people.
Good bug reports include steps to reproduce, screenshots or video clips, and the game version number at time of crash. Community memes and chat screenshots about specific matches don't help development, but a clear reproduction path does. If you can make the bug happen again reliably, your report becomes incredibly valuable.
When filing, describe what you expected to happen versus what actually happened. Include any error messages that appeared on screen. Links to game replay files help developers test the exact scenario you encountered.
Before filing a new issue, search the relevant GitHub repository. Many common bugs already have open reports, and duplicates slow down the triage process. If you find an existing issue, you can add your reproduction steps and confirm the bug on your system. That extra data helps developers prioritize the fix.
Community feedback loops work best when they stay constructive. Filing a clear, helpful bug report takes effort, and communities that appreciate that effort are the ones where developers and players work together smoothly.
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.