How to report bugs in Beyond All Reason
Found something broken in BAR. Here is where to go, what to include, and how to move the conversation forward without creating noise.
Tags: bug report, troubleshooting, community, beyond all reason
Where to report bugs
The Beyond All Reason community runs a dedicated bug-reporting channel on its Discord server. That channel is the right place for anything that looks like a genuine game issue: commander behavior breaking, units doing the wrong thing, crashes, UI widgets failing, or pathfinding going sideways.
If a bug affects competitive play directly, such as the commander failing to build certain unit categories, post it there immediately. Organized matches can be derailed by a single unresolved bug.
What to include in a bug report
A useful bug report needs enough information that a developer can reproduce the problem. Include these details:
- What you were doing when the bug appeared
- What you expected to happen
- What actually happened instead
- Game version and any relevant settings
- The replay file, if the bug occurs in a match
Screenshots help. A short clip or gif helps even more. The more evidence, the faster someone can track down the root cause.
When a bug is already known
Some bugs get reported and sit in a queue. Developers know about them. The fix might be waiting on a code revert or a more complex patch. If a developer mentions it is a known issue and already reported, adding a duplicate report does not speed things up. It does add noise.
Checking the bug channel for similar reports before filing a new one saves everyone time.
PRs welcome culture
BAR is open source. When a bug gets identified, the fastest fix sometimes comes from a community member who spots the problematic commit and submits a pull request to revert it. The open-source nature of the game means players with coding skills can directly contribute solutions instead of just reporting problems.
Most players cannot write patches. But understanding that the pipeline exists and that reports feed directly into development helps set realistic expectations for fix timelines.
Bugs in competitive and scrim matches
When a bug hits during organized scrimmage play, the disruption multiplies. Teams waiting for a match to continue should note the bug, share the details in the report channel, and move on. Pushing for an instant fix during a live event rarely works. Document the issue, move forward, and check back later for resolution status.
Common BAR bugs worth watching
A few bug categories come up repeatedly:
- Commander build queue failures — the commander stops producing certain unit types without warning
- Unit pathfinding blocks — units get stuck on terrain or each other
- Widget rendering issues — overlay elements misbehave after game updates
- AI economy behavior — AI commanders fail to build expected unit compositions
These tend to get resolved in subsequent patches, but keeping track of recurring issues helps separate genuine bugs from unexpected behavior that is actually working as designed.
Join a community that handles issues calmly
Bugs happen in every game. How a community responds to them says everything. Creed of Champions runs organized matches with players who know how to report problems without turning a game into a complaining session. When things break, they document it and move forward together.
"One of the few places where you can for sure coordinate with people in matches with a good supportive attitude. Everybody tends to be understanding and constructive." — [Crd]