Integration model

Modern SIR is designed to be useful by itself, but several modules become much more powerful when companion plugins are available. The integration story is split across:

shared runtime libraries bundled with SIR
optional Bukkit plugins detected through softdepend
migration sources supported by /sir migrate

Bundled runtime

You do not need to install separate helper jars for the internal SIR runtime:

Runtime piece	Role inside SIR
`Takion`	Shared formatting, scheduling helpers, message utilities, and general runtime support
`GlobalScheduler`	Sync and async task execution
`bStats`	Anonymous plugin metrics unless disabled globally

This matters because the plugin already ships with the core services needed for its own modules and command providers.

Utility and text ecosystem

Plugin	Why SIR cares
`Vault`	Lets SIR resolve permission groups, chat metadata, and group-aware selectors such as the `print` command's group targeting
`PlaceholderAPI`	Expands placeholders inside chat formats, announcements, join and quit messages, MOTD text, and other configurable text outputs
`InteractiveChat`	Improves compatibility with richer chat components and chat presentation stacks
`ViaVersion`	Declared as an optional utility dependency for cross-version server setups

If your text formats or group selectors are central to your server, Vault and PlaceholderAPI are usually the first integrations worth validating.

Discord ecosystem

SIR can cooperate with:

DiscordSRV
EssentialsDiscord

This mainly affects the discord module and any feature that can emit webhook-style output, such as:

join and quit notifications
advancement announcements
global chat relays
announcement broadcasting

If you migrate from older chat stacks, this is one of the places where channel IDs and message templates deserve a manual audit after import.

Authentication plugins

The project recognizes login and auth plugins such as:

UserLogin
AuthMe
NexAuth
nLogin
OpeNLogin

These integrations matter mostly for the login and join-quit flow. They let SIR behave correctly around:

pre-login and post-login spawn behavior
gated onboarding
first-join and join message timing

Vanish ecosystem

SIR also knows how to operate alongside vanish or admin utility plugins such as:

SuperVanish
PremiumVanish
CMI
Essentials

This primarily affects the vanish module and chat-side staff workflows. Typical use cases include:

allowing hidden staff chat with a dedicated key
blocking normal users from messaging vanished staff
preserving internal staff communication without leaking presence

Moderation ecosystem

SIR does not replace punishment plugins, but it does complement them well.

The explicit soft dependency here is:

AdvancedBan

Typical pattern:

SIR detects or formats a moderation event in chat
your server policy then chains to a punishment plugin or external workflow if needed

This division keeps SIR focused on chat and interaction policy while letting dedicated punishment plugins own ban history, appeal flow, and punishment UX.

Migration-aware integrations

The migration routines implemented in Modern SIR recognize:

Essentials / EssentialsX
older SIR data folders

Those integrations are operational, not just runtime compatibility. They matter because /sir migrate can:

copy or translate user data
move or map shared files
convert module or command state
create snapshots under back-ups/

If migration is your main concern, continue with Migration Guide.

Recommended validation order

If your server stack is large, avoid enabling every external integration at once. The safer order is:

boot SIR with stock config
validate module state and command state
enable PlaceholderAPI and Vault behavior
validate Discord relays
validate auth/login hooks
validate vanish and moderation-specific workflows

That sequence makes it much easier to isolate whether a problem comes from SIR configuration or from another plugin in the stack.

Integrations