Customizing units in Beyond All Reason starts with understanding how to copy existing unit definitions and modify properties. New modders often ask how to get popular custom units like Nutty B Raptors running. The engine provides a clean template system through Lua table copying.
Tags: beyond all reason, modding, nutty raptors, custom units, !bset commands, unit copy, lua modders guide
Creating a custom unit starts with copying an existing unit definition. The pattern looks like this:
table.copy(UnitDefs["baseunit"])objectnamemetalcostEach override layer replaces one property of the parent unit. Everything else carries over unchanged. This approach keeps custom unit code short and maintainable.
When you copy a unit, the essential swaps include the model file, the build icon DDS, the script definition, and the base cost values. Weapons require additional attention since every range and damage parameter lives in separate weapon definitions.
Weapon definitions need their own section in the new unit. Simply copying the unit does not automatically create weapon variants.
The community maintains shared documentation on !bset commands and lobby tweaks. These resources live in community channels and Google Docs. Singleplayer scenarios sometimes need longer setup guides than what lobby commands cover.
Asking specific questions in modding channels gets you direct answers. Experienced modders review code and point out missing pieces.
BAR modding rewards collaboration. When experienced developers share code patterns, newcomers learn faster and contribute sooner. Communities that practice open knowledge sharing, like Creed of Champions, carry this same ethic into gameplay.
[Crd] The removal of toxicity, the goal of fun and learning, makes for a refreshing spot to play and spend time. It has also made a game with plenty of complexity a bit less daunting to dive into.
The same principle applies whether you are building custom raptor units or coordinating with teammates in a ranked match.