Showing build radius visibility and fixing spectator widget loading in beyond all reason

Making build radius visible on commanders

Commander build ranges blend into many BAR map backgrounds. The fix uses Spring.GetUnitRadius(unitID) to retrieve the actual build radius value, then draws a visual ring underneath the unit. Community widget developers have already implemented this pattern in range display widgets.

If an existing range widget misses build radius, ask the developer or check their repository. Many widget authors maintain public repos where they push updates. Downloading the latest version often adds new range categories without any configuration needed.

Widgets not loading while spectating

Spectator mode in multiplayer BAR matches changes what widgets see. Some widgets rely on team data or ownership information that does not exist for a spectator. If your widgets appear inactive during spectating, check two things:

• The widget requires ally team data that spectators cannot access
• Lobby settings restrict certain widget categories for balance reasons

Game installation drive does not affect widget loading. Whether BAR sits on C or D drive, the LuaUI folder resolves the same way. If widgets fail to load during spectating, the lobby configuration is the most likely cause.

Widget development for visibility overlays

Building a widget that draws visible markers requires Spring drawing functions. The general pattern:

1. Get the unit ID for the target (commander, factory, or any builder)
2. Call Spring.GetUnitRadius(unitID) to retrieve the radius
3. Use gl.Circle() or equivalent OpenGL calls within a widget:DrawWorld() hook
4. Position the overlay slightly below unit level so it does not obscure the model

Color and opacity choices matter on maps with similar terrain colors. Red or orange overlays tend to stand out against most BAR map palettes.