Supported Plugins
Compatibility overview for the server plugins, migration sources, and ecosystems that matter to SIR+.
SIR+ inherits the modern SIR compatibility story and then adds the addon runtime on top. That means this page has two jobs:
- show the third-party plugins that still matter to the stock runtime
- show the migration sources and addon-facing ecosystems that matter before you extend the platform
Inherited runtime integrations
| Plugin | Why it matters in SIR+ |
|---|---|
| PlaceholderAPI | Expands placeholders inside chat, announcements, MOTD, and any text that your modules or addons expose through PlaceholderAPI-driven output. |
| Vault | Keeps permission groups, chat metadata, and group-aware utility behavior available to the SIR+ runtime. |
| DiscordSRV | Supports Discord-linked messaging flows and relay patterns inherited from modern SIR. |
| EssentialsDiscord | Alternate Discord bridge when your server already uses the Essentials ecosystem. |
| InteractiveChat | Helps richer chat presentation stacks coexist with SIR+ text output. |
| ViaVersion | Optional utility dependency for mixed-version networks. |
Login, vanish, and moderation stack
| Plugin | What it influences |
|---|---|
| UserLogin / AuthMe / NexAuth / nLogin / OpeNLogin | Login-aware join flow, gated onboarding, and the timing of user-facing messages. |
| SuperVanish / PremiumVanish | Vanish-aware staff messaging and hidden-state behavior. |
| CMI | Utility compatibility plus a direct migration source for SIR+. |
| Essentials / EssentialsX | Shared utility ecosystem and direct migration source. |
| AdvancedBan | Dedicated punishment handling alongside SIR+ chat and workflow logic. |
Migration sources
| Source | Supported in SIR+ | Notes |
|---|---|---|
| SIR Legacy | Yes | SIR+ can migrate from the old resources/ style layout. |
| SIR Modern | Yes | SIR+ can also reuse already-structured modules/, commands/, and users/ data. |
| Essentials / EssentialsX | Yes | Useful when moving a classic utility stack into the SIR family. |
| CMI | Yes | One of the main compatibility differences versus base SIR. |
Addon-facing expectations
| Component | Why it matters |
|---|---|
| SIRApi | The public API used to compile custom addons. |
| Your target plugin stack | If your addon depends on PlaceholderAPI, Vault, DiscordSRV, or another plugin, that dependency still matters even though SIR+ supplies the addon runtime. |
| Paper / Spigot-compatible runtime | Addons still run inside the normal Bukkit-family plugin environment. |
Important distinction
SIR+ does not require a separate helper plugin just to unlock addons. The addon runtime is already part of the main SIR+ jar. What changes from server to server is the ecosystem your addons expect around it.
Where to continue next
Use Modules & Providers for the built-in feature map, Addon Runtime for loading behavior, and Addons API when you are ready to compile against SIRApi.
Getting Started
Install SIR+, understand the extra admin controls, and prepare for addon-based extensions.
Frequently Asked Questions
Common questions about SIR+, addon loading, provider overrides, migration sources, runtime state, and addon development.
Last updated on