Legacy vs Current
Compare SIR Legacy with the current 2.3.1 branch and decide why migration is recommended.
Legacy vs current SIR
SIR has two important documentation contexts:
- Legacy: SIR
1.7.0and below, built around the old Maven project andplugins/SIR/resources/tree. - Current: SIR
2.3.1, built around the maintained Gradle multi-project layout with split modules, command providers, API, and shared runtime internals.
Use Legacy documentation only when you are auditing an old installation or planning a migration. New servers should start on SIR 2.3.1.
Branch comparison
Legacy versus current SIR
The recommendation for new installs and migrations is to use current version 2.3.1.
1.7.0 and below. Migration reference only.
2.3.1. Recommended maintained branch.
Single Maven project under src/main.
Gradle multi-project: api, runtime, plugin, module/*, and command/*.
plugins/SIR/resources/modules and plugins/SIR/resources/commands.
plugins/SIR/modules, commands, users, and state files.
Broad module toggles inside the old resources tree.
/sir modules GUI or CLI plus modules/states.yml.
Central command metadata in resources/commands/commands.yml.
/sir commands GUI or CLI plus provider state in commands/states.yml.
Large umbrella folders such as chat and hook own multiple concerns.
Dedicated modules for channels, discord, login, vanish, moderation, tags, and more.
Data can live inside old command folders like chat color, mute, ignore, and chat view.
Player-facing state is normalized into users/ files.
Mostly legacy color codes and older SIR tags.
SIR tags, legacy codes, hex colors, and MiniMessage through Takion/PrismaticAPI.
No current public API target documented for new integrations.
Published SIR API artifact and package reference for integrations.
Do not use for new installs.
Use this branch for new installs.
Good source for auditing old data before migration.
Target branch for moving away from Legacy.
Documented for audit and migration, not active feature support.
Current documentation and support baseline.
Recommendation
Migrate to SIR 2.3.1 when possible. The current branch has clearer file ownership, module and command management through /sir, cleaner API packages, and better documentation around formatting support.
Frequently Asked Questions
Common questions about SIR Legacy, SIR 2.3.1, modules, commands, permissions, migration, and troubleshooting.
Modules
Branch-aware explorer for SIR modules, their files, keys, dependencies, commands, and configuration examples.
Last updated on