Spectator HUD and player stats widgets in BAR
Understanding how the spectator stats display works and why running it while playing affects your performance.
TeamStats versus spectator HUD
Press statistics during a match and the TeamStats widget pops up. It shows resource demand, army composition, and production queues for every player on the map. That is a lot more data than the spectator HUD pulls, and it costs more to run. The widget uses measurably more CPU cycles and eats more memory bandwidth than the lighter spectator display.
These two widgets cannot share computed stats between them. Each one does its own calculations independently. Adding a shared stats layer into the base game would solve this, but it is not on the near-term development roadmap. So the cost stays duplicated if you try to run both at once.
Idle builder calculation costs
Tracking idle builders by brute force used to be expensive enough to cause noticeable slow-downs. The calculation had to scan every builder across the entire map and compare resource demand against available income. Newer methods replaced this with smarter checks that only examine builders near known factory queues. The improvement cut the idle widget cost down substantially.
Players who notice frame drops during late-game matches should check if their idle widget is on. It is helpful for early and mid game, but the constant scanning can add up when the map has hundreds of active units.
Player-view HUD during no-fog games
Some players have asked for a spectator-style stat overlay available during live matches when fog of war is disabled. The idea has been discussed and some versions exist in custom modes. Battle Blitz, for example, already runs with reduced fog settings where a full-info HUD makes more sense.
The limitation is mostly about CPU budget. Showing real-time stats for every player requires the same heavy calculations the spectator HUD does, just for a smaller audience. As widget optimization improves, this becomes more feasible.
Font rendering and small text readability
Stats panels pack a lot of numbers into tight spaces. Small fonts are notoriously hard to render cleanly, and some display settings produce blurring at the lower end of readable sizes. If your widget text looks fuzzy, try adjusting your screen resolution or scaling settings before filing a bug report. This is a known engine-level challenge with font rendering, not a widget-specific error.
Creed of Champions: shared information, shared success
Stats widgets reveal what is happening across the entire battlefield. Good teams operate the same way: everyone sees the same information and acts on it. Creed of Champions builds its community around exactly this idea. Cooperation, mutual improvement, and zero ego. When teammates share information generously instead of hoarding it, everyone plays better.
[Crd] 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.
That is the difference between a stats panel and a team that actually uses what the panel tells them.