Counting personal units and using the ingame keybind editor in beyond all reason

Counting your own constructed units

Spring.GetTeamUnitsByDefs() returns units for an entire team. If you need only the units you personally built, filter the results using Spring.GetUnitAllyTeam(). Compare the ally team ID to your own player info obtained through Spring.GetPlayerInfo(). The function returns an array of unitIDs that match your criteria.

For example, to count personal armada wind generators, iterate through matching unitIDs and check against UnitDefs for the specific unit type. The pattern applies to any unit: filter by ally team first, then narrow by unit definition.

Fixing awkward unit walking paths

Units in BAR sometimes take inefficient routes when moving from a rally point to a guard position. The most common fix is issuing a guard command immediately when the unit finishes building. This eliminates the rally-to-position walk entirely.

Another approach builds a small obstacle like two dragon teeth at the rally point exit. The sixteen metal investment forces units to reposition naturally instead of walking across the map before starting their guard. Alternatively, just move units slightly to the side and start assisting an existing structure. This avoids the routing problem with minimal effort.

Ingame keybind editor widget

The ingame keybind editor lets you modify keybinds without editing config files manually. It installs as a widget in the LuaUI/Widgets folder but requires dependency order:

1. MasterBel2's GUI Framework
2. MasterFramework Extensions
3. MasterFramework FlowUI Extensions
4. Keybind Editor

Enable them in that order. The keybind editor shows a movable window in-game. Backup your existing uikeys.txt file before using the widget since the backup function has not been extensively tested.

You can also control widget state programmatically. Calling widgetHandler:DisableWidget("Camera Minimum Height") from within another widget lets you toggle system widgets on and off based on game conditions.