Supported Plugins
Compatibility overview for the companion plugins, bridges, and migration sources that matter to SIR.
SIR works on its own, but several integrations become important depending on whether you run the Legacy branch or the modern 2.0.0 architecture. Use this page as the compatibility overview, then continue with Integrations if you want the deeper runtime notes.
Core utility stack
| Plugin or library | Why it matters | Typical impact |
|---|---|---|
| PlaceholderAPI | Expands placeholders across chat formats, announcements, MOTD, and other configurable text output. | Strongly recommended if your server already uses scoreboards, holograms, or placeholder-driven messages. |
| Vault | Lets SIR read permission groups, chat metadata, and group-aware selectors. | Important when you use ranked formatting or commands that target groups. |
| InteractiveChat | Improves compatibility with richer chat components. | Helpful on networks that already run advanced chat presentation plugins. |
| ViaVersion | Optional utility dependency for mixed-version environments. | Useful when your stack is designed around multi-version support. |
Discord bridges
| Plugin | What SIR uses it for |
|---|---|
| DiscordSRV | Global chat relays, join and quit notifications, and Discord-aware messaging flows. |
| EssentialsDiscord | Alternate Discord bridge when your stack already leans on the Essentials ecosystem. |
These integrations matter most for the modern discord module and for any setup that mirrors server activity to external channels.
Login and authentication plugins
| Plugin | Why it matters |
|---|---|
| UserLogin | Lets SIR align join flows and onboarding with login state. |
| AuthMe | Same role as above for AuthMe-based servers. |
| NexAuth | Supports login-aware message timing and gated player flow. |
| nLogin | Helps SIR avoid firing user-facing flows too early. |
| OpeNLogin | Same compatibility category for login-protected servers. |
This category matters mainly in modern SIR, where login-aware modules and join/quit behavior are split more clearly.
Staff and moderation ecosystem
| Plugin | What it influences |
|---|---|
| SuperVanish | Vanish-aware staff messaging and hidden-state behavior. |
| PremiumVanish | Same role as above for PremiumVanish stacks. |
| CMI | Extra utility compatibility around staff workflows and visibility-aware behavior. |
| Essentials / EssentialsX | Shared utility ecosystem, migration source, and staff-flow compatibility. |
| AdvancedBan | Lets SIR coexist with a dedicated punishment platform. |
SIR does not try to replace punishment plugins. It complements them by owning chat-side behavior, messaging policy, and utility flow.
Migration-aware sources
| Source | Supported in base SIR | Notes |
|---|---|---|
| SIR | Yes | Modern SIR can detect whether the source is Legacy data or already-modernized data. |
| Essentials / EssentialsX | Yes | Useful when moving from an Essentials-style server stack into the SIR workflow. |
Branch expectation
Most of the integrations listed here make the most sense in modern 2.0.0, because the feature model is cleaner and easier to audit there. Legacy can still coexist with older plugin stacks, but it usually deserves more manual review before migration.
Need the deeper compatibility details?
This page is the quick overview. If you want the longer explanation of what each bridge changes at runtime, continue with Integrations.
Getting Started
Choose the right SIR branch, install it cleanly, and know where to continue next.
Frequently Asked Questions
Common questions about SIR Legacy, SIR 2.0.0, modules, commands, permissions, migration, and troubleshooting.
Last updated on