Finding where tweak strings live and accessing the right API documentation are two problems that come up constantly. Here is how to approach both.
Tweak definitions appear in several places across the BAR ecosystem. Some players post them in dedicated threads. Others share them through community channels without consistent tagging. The most reliable way to find a specific tweak is asking directly in community spaces where modders gather.
For well-known tweaks like certain Nutty raptors variants, dedicated threads contain full base64 strings. Checking community threads tagged with tweak keywords is usually the fastest path.
Every replay file contains the lobby settings used when the game started. That includes tweak strings. The extraction process works like this:
This method works even when the original player no longer has the tweak posted anywhere. The replay is a self-contained record of what settings the game used.
New BAR modders looking for widget API documentation often struggle because the SpringRTS Lua library documentation is scattered. The primary references live on the SpringRTS wiki.
For metal extractor queries specifically, the relevant API calls are:
GetFeatureResources on the SpringRTS wiki under Lua SyncedReadGetMetalExtraction in the same documentation sectionThe BAR repository itself does not maintain a separate API document. The SpringRTS wiki is the authoritative source for all synced read functions, widget callbacks, and gadget hooks that BAR inherits from the Spring engine.
A practical note that saves everyone time: always share tweak code and mod scripts as text, not screenshots. Someone who has to transcribe code from an image is unlikely to help. Plain text in code blocks lets others paste, test, and debug immediately. This applies when asking for help with any BAR modding question.
Beyond replay extraction, BAR offers a developer UI option in the settings menu. Enabling it exposes the extra mod options and their current values. This is quicker than digging through replays when the goal is just to see what a lobby is configured for.
Good modders share their code as text, point to the right docs, and help each other extract what they need from replays. Clear execution and helpful habits make the whole community work better. That ethos drives the kind of gameplay environment where players actually want to stick around and improve. Check out the channel for more BAR content: Beyond All Reason YouTube.
Creed of Champions rekindled my joy in Beyond All Reason. I had burned out on the game, and the friendly, no-toxicity environment caused me to start enjoying it again.