BitAspire Wiki
SIRSIR

Modules & Providers

Branch-aware hub for the detailed Legacy and Modern module and command-provider references.

Explore SIR by branch

Legacy and Modern SIR document the same plugin idea through two very different structures:

  • Legacy keeps broad folders such as chat/ and hook/
  • Modern splits the platform into dedicated modules/* and command/* loaders

That means the fastest way to learn the plugin is to pick the branch first and then read the detailed module and command references for that branch.

Branch Explorer

Choose the SIR branch and the kind of docs you want to read

Switch between Legacy and Modern, then narrow the view by architecture, modules, commands, migration, or FAQ.

Modern 2.0.0Show the main entry points for this branch.

Modern branch guide

Choose this path for new installations or for the maintained Gradle multi-project branch with split loaders.

Separates built-in features into `modules/*` and `command/*` with their own runtime folders and state files.

Adds `/sir modules`, `/sir commands`, and `/sir migrate [source]` as the main operator workflow.

Best baseline if you want the current SIR architecture without the addon runtime from SIR+.


Detailed references


What changed the most?

The biggest architecture jumps are these:

  • Legacy chat/ becomes channels, cooldowns, emojis, mentions, moderation, and tags
  • Legacy hook/ becomes discord, login, and vanish
  • command families move out of one broad Legacy registry into dedicated provider folders with their own state

If your goal is migration rather than discovery, continue with Configuration Layout and Migration Guide.

Last updated on

On this page