Understanding how Beyond All Reason handles multiple players on one team, the Gaia environment team, and where to find modding documentation.
BAR allows multiple humans to control a single team. Each player shares the same commander and build tree, which means one player can focus on economy while another handles unit production without stepping on each other. The Spring engine identifies this through allyTeamID and teamID separation: players on the same team share a teamID but maintain distinct playerIDs that the spectator overlay tracks individually.
Spring.GetPlayerList(teamID) returns every human on that team, while Spring.GetTeamList() iterates through all team compIDs including AI opponents and the Gaia environment. Checking whether a team is AI or human means comparing against Spring.GetGaiaTeamID() and verifying the player list length.
When watching a replay as a spectator, the same team inspection functions work. Loop through every compID, pull team details, check player counts, and distinguish between human players, AI teams, and the Gaia environment. A clean diagnostic prints the allyTeamID, player count, and whether each team runs a human or AI.
This matters for modders building spectator widgets or custom overlays that need to color-code teams correctly. Getting the Gaia team wrong shows the environment as a playable opponent. Getting the AI team wrong hides an opponent from the widget display.
Players asking about touch screen control in BAR are looking at widget territory. The game itself does not ship with touch-specific input handling, but the Spring engine Lua widget system hooks into mouse and keyboard events that can be remapped. A second screen running a touch interface could send commands to the primary game instance through widget communication, though this requires custom Lua development.
The barrier is interface design, not engine capability. BAR already handles complex input through its control bindings. Extending those to accept touch coordinates from an external source means writing a widget that listens for incoming coordinate data and translates it into in-game selection and movement commands.
The primary modding documentation for Beyond All Reason maintains itself as a GitHub Gist by badosu, serving as the starting reference for anyone building mods. This document covers the file structure, definition formats, and Spring engine hook points that mods rely on. It is the single most useful reference for questions about where modinfo.lua goes, how unitdefs table structure works, and what fields weapondefs expects.
Beyond that, reading the game source directly in the Beyond All Reason repository answers questions the documentation does not cover. Modding in BAR means working with the Spring engine at a level where browsing the actual game code often provides faster answers than any written guide.
For visual walkthroughs of BAR modding topics, check out the BAR YouTube channel: Beyond All Reason on YouTube. Watching how experienced modders structure their files often teaches more than reading documentation alone.
"Having a space like here that offers a community, trainings, events, and the guarantee to not be judged or insulted by fellow members is really precious. Keeping the game safe, and more importantly, fun." — Crd-011