BAR hotkey mods and team terminology for modders

Custom hotkey setups in BAR require understanding the engine call system. Team terminology confusion also trips up new modders working with teamID concepts.

Tags: beyond all reason, development, modding, hotkeys, team terminology, lua

Custom hotkey behavior

Making a custom hotkey act like a standard one requires looking at existing implementations in the BAR source. The general modding channel pins contain guidance on hotkey customization, and community members share working configurations there.

TeamID versus player confusion

TeamID in the Spring engine refers to a team, not a single player. FFA games give each player their own team, so teamID and player map one-to-one. Team games group multiple players under one teamID where teamID controls shared resources and vision.

The team terminology guide on the GitHub pages site explains this relationship clearly.

Setting up a dev environment

The BAR GitHub README includes a development quick-start section that covers required tools, build steps, and file structure. Following that gets you a working environment faster than piecing together forum posts.

Custom gadgets go in luarules/gadgets. Use AddTeamResource for giving resources and UnitDestroyed for hooking unit death events.

Creed of champions

Clean hotkey setups and proper macro habits compound over time. Creed of Champions values players who invest in fundamentals and help each other build better habits through teamwork.

[Crd] One of the few places where you can for sure coordinate with people in matches with a good supportive attitude. Everybody tends to be understanding and constructive.