BitAspire Wiki

Commands

Branch-aware explorer for SIR commands, providers, permissions, aliases, language files, and migration notes.

SIR commands

SIR commands changed heavily between Legacy and the current 2.3.1 branch.

Legacy used one broad commands/commands.yml registry. Current SIR uses dedicated command-provider jars and lets operators manage provider state through /sir commands.

Knowledge Explorer

Choose the entry you want to inspect

The data below follows the current repository resources and excludes descriptor-only files unless they define commands.

Current 2.3.1main

Main /sir command

Summary

Administrative entry point for help, reload, support, migration, modules, and command providers.

What it offers

  • - /sir modules GUI or command fallback.
  • - /sir commands GUI or command fallback.
  • - /sir migrate for supported sources.

Plugin dependencies

Required

No hard plugin dependency in the default resource files.

Optional

No optional plugin hook is required for the documented defaults.

Configuration files and important keys

commands/main/lang.yml

Main /sir command language.

lang.helplang.supportlang.reloadlang.migrate.help/start/no-data/unknown/done/error

commands/lang.yml

Global command fallback messages.

lang.no-permissionlang.not-playerlang.wrong-arg

Commands

CommandPermissionAliasesUsage
/sir modulessir.admin.modules-/sir modules <module> [enable|disable|toggle]
/sir commandssir.admin.commands-/sir commands <provider> [enable|disable|toggle]
/sir migratesir.admin.migrate-/sir migrate <Essentials|SIR>

Configuration examples

  • - Use /sir modules or /sir commands first; edit state files manually only when the server is offline.

Command state

In current SIR, provider metadata comes from each provider's commands.yml, while runtime enable state is managed by SIR and persisted separately. Prefer /sir commands before editing state files by hand.

Last updated on

On this page