BAR development discussions happen in dedicated Discord channels that require a specific role to access. Players who want to follow development work, report bugs, or suggest features need to know where to go and how the reporting process works.
Access to BAR development Discord channels requires the Development role, which any player can assign themselves through the server's role customization system. On the BAR Discord, navigating to channel customization and grabbing the wrench Development role unlocks the entire Development channel category.
Players should read pinned messages in development channels before posting. These pins contain setup instructions, formatting guidelines, and answers to the most frequently asked questions about how development discussions operate. Reading pins reduces duplicate posts and keeps the channels focused on novel discussion topics.
The Development role carries an expectation of respectful discussion. Development channels cover ongoing work, design debates, and early-stage concepts that may change significantly before release. Players joining these channels should approach discussions as collaborators rather than customers demanding specific outcomes.
Bug reports go to a dedicated channel separate from suggestions and general discussion. Keeping bug reports in their designated channel ensures developers can triage and track issues efficiently without wading through feature requests and casual conversation.
The BAR GitHub repositories serve as the official bug tracking system. The Lobby and Launcher issues live at github.com/beyond-all-reason/BYAR-Chobby/issues, while game engine issues use github.com/beyond-all-reason/Beyond-All-Reason/issues. Players can check existing issues before filing new ones to avoid duplicates.
Effective bug reports include reproduction steps, infolog.txt content, and relevant replay files. Reports that describe symptoms without any actionable data take much longer to resolve or remain unsolvable entirely. Players who invest a minute in collecting supporting information save the development team hours of investigation time.
Players under reporting restrictions cannot file bug reports involving other players. These restrictions apply when the system detects potential malicious behavior and the community moderation team needs time to investigate.
Bans affect OS rating in some cases. A three-day ban can reset a player's OS downward, typically dropping several tiers depending on pre-ban standing. The exact impact depends on factors the moderation team evaluates case by case.
Players who believe they were wrongly restricted should reach out through the appropriate moderation channels with relevant context. False reports do exist in the system, and the team reviews appeals with access to server-side data that the affected player cannot see.
BAR players who want to engage with development and community improvement need 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.