The Module Manager in BAS: Creating and Sharing Modules

Modules are the boxes that hold what BAS can do — and the Module Manager is where you manage them: installing what others built, toggling what you have, and packaging your own work to reuse and share.

What it does

The Module Manager lets you:

• Create new modules — package your own functionality.
• Install ready-made modules — add functionality others have built.
• Enable or disable installed modules — load only what a given project needs, keeping it lean.

Anyone can build and share a module

The system is open: anyone can create their own module and hand it to someone else. Modules are packaged in .zip format, which makes them trivial to distribute and import. This is what turns a personal solution into a reusable asset — solve a problem once, wrap it in a module, and you (or the community) never solve it again.

How a module is built

The structure mirrors the rest of BAS: a module consists of functions, and functions consist of action blocks. That’s the same three-level hierarchy that runs through the whole product — blocks compose into functions, functions compose into a module. When you’ve built functions you keep reaching for across projects, packaging them into a module is the natural next step.

Why it matters

The Module Manager is what makes BAS an ecosystem rather than just an editor. Captcha solvers, integrations, parsing helpers — much of what you’d otherwise build from scratch already exists as a module someone published. Install those, disable what you don’t need, and contribute your own back. Reuse at the module level is the difference between rebuilding the same logic forever and standing on what’s already been solved.