Why popup artillery sometimes fails to fire, how to debug tweakdefs errors in the lobby, and where to find the auto-generated game changelog.
The Core popup cannon is a classic example of weapon behavior that looks wrong until you check both the weapondef and the unit animation script. The popup cannon has a weapon defined in the Lua unit file, but the firing animation lives in the BOS script under cortoast.bos.
When the artillery tracks a target but fails to fire, the problem usually sits in the animation script, not the weapondef. The BOS script controls the turret turn, the popup sequence, and the fire signal. If any of those steps does not complete, the weapon never launches its shot.
Modders should check the springrts weapondefs wiki for tag meanings, then cross-reference the unit animation script. The weapondef tells the engine what to shoot. The animation script tells the unit when and how to shoot it.
Players who try to apply tweakdefs in a public lobby often hit errors. The most common causes are malformed definitions, missing subtables, and nil values that the lobby parser does not handle gracefully.
A tweakdef with a missing subtable silently breaks the entire string. The lobby shows an error but does not say which field failed. The fix is to validate the tweakdef structure offline before pasting it into the lobby. Check every nested table, every weapon reference, and every unit ID.
Base64 encoding issues compound this. URL-safe encoding is mandatory. Standard base64 introduces characters that the lobby parser rejects without explanation.
BAR generates a changelog automatically and publishes it on the website. The in-game changes button, located in the top right, also displays it. Players who want to see what changed between versions should start there rather than hunting through forum posts or Discord pins.
Community balance candidates like Hornet's Balance Candidates Pack get discussed in Discord channels, but the authoritative change list comes from the auto-generated game changelog. That list reflects what is actually running in the current build.
BAR modding demands attention to two layers: the engine's data definitions and the unit scripts that trigger them. When a weapon misbehaves, check both. When a tweak fails, validate the structure before trusting the lobby to diagnose it. And when in doubt about what changed, the in-game changes button never lies.
"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."
Creed of Champions member