If you are digging into Beyond All Reason modding or tweaking your setup, you will run into the terms "widget" and "gadget." They look similar on the surface but work in completely different ways. Getting the distinction right matters for multiplayer safety, installation choices, and what you are actually allowed to change.
Tags: beyond all reason, widgets, gadgets, lua modding, multiplayer, synced, unsynced
The engine draws a hard line. Widgets are unsynced. Gadgets are synced. That single word decides everything downstream.
Unsynced means the code runs locally on your machine only. A widget can draw extra UI elements, show overlays, or reorganize your screen. No other player sees it. The game engine does not check it against other clients.
Synced means the code runs identically on every player's machine. Gadgets change game-state logic. The engine verifies them across all connected clients to keep the match fair.
This is why you can safely use custom widgets in multiplayer. You cannot just drop a custom gadget into a standard match without breaking sync.
Widgets are your personal toolkit. Install a widget to change how information appears on your screen, add build presets, or show resource graphs. Other players will not see any of it, and the match stays clean.
Gadgets operate at a different level. They alter actual game mechanics. Map scripts and official game modes use gadgets for things like changing wind speed or enabling special rules. You cannot install a personal gadget into a standard ranked or casual match, and for good reason.
A common question from newer modders: can a widget change wind speed during a match? The answer is no. The engine exposes SetWind() for synced code only, which means map scripts and gadgets. Widgets lack access to it. Wind control lives on the synced side by design.
The BAR modding community is welcoming to newcomers. Read through existing code, follow what each function does, and use unitdefs to understand how units are structured. Community members who explain their code openly help the next person get started.
Tower defense experiments show the flexibility of the system. Construction turrets that build structures instead of mobile units demonstrate how much room exists for creative concepts. Some designs could support infinite-tier progression systems with the right framework.
Stick to widgets for personal quality-of-life improvements. Leave synced logic to official game modes and maps. Keep widgets lightweight to avoid slowing down the client. Disable anything you are not actively using.
The community around BAR modding values clear documentation and cooperative problem solving. Groups like Creed of Champions carry that same ethic into gameplay itself. Players who take time to understand how the engine works tend to become the most helpful ones in the scene.
[Crd] 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.