BAR tracks bugs through GitHub Issues, not chat complaints. Cloaked commander harassment against enemy geo is a real tactic. Here is how both systems work.
Tags: GitHub issues, bug reporting, comm cloak, geo, LLT, self rating, beyond all reason, bar
BAR uses GitHub Issues for all formal bug tracking. Three separate repositories handle different components. Lobby and Launcher bugs go to the BYAR-Chobby repo. Game bugs belong in the Beyond-All-Reason repo. Engine issues have their own tracker. Each one accepts bug reports from the community.
This system keeps reports organized and traceable. Chat complaints disappear into message history while GitHub issues stay visible until resolved.
Players who think their OS does not reflect their actual skill level face a simple choice. Join higher rated lobbies and let the system recalibrate. If you genuinely perform above your visible rating, the OS number will climb to match. Sitting in comfortable lobbies while complaining about the mismatch wastes everyone time.
A cloaked commander can walk into enemy geo positions undetected when radar coverage is thin. The tactic works because geo constructions matter for energy income and disrupting them impacts enemy production timelines.
Some players build Lightweight Laser Towers as an opening strategy instead of standard economic expansion. LLT rushes pressure immediate expansion space and force early defensive responses. The approach works on maps with tight positioning but loses on maps where the opponent can simply expand away from the pressure.
Tactical experimentation like cloaked comm harassment and LLT rushes keeps BAR endlessly interesting. Creed of Champions encourages members to try these creative strategies in a supportive environment where wild builds get feedback, not ridicule.
[Crd] Crd is the first really comfortable community I have been a part of. Everyone is nice and kind, the atmosphere is relaxed, and I am not getting yelled at for not being optimal.