Deep reference for every bundled SIR+ command provider, including owned files, permissions, runtime state, and override-aware behavior.

SIR+ built-in command-provider reference

SIR+ keeps the same stock provider catalog as Modern SIR, but the runtime around those providers is more powerful.

In SIR+, a provider is not just a command family. It is also something operators can:

enable or disable through the command manager
inspect through commands/states.yml
tune for per-command override behavior when command conflicts exist

That extra control is the main reason these providers deserve their own documentation even on addon-focused servers.

Shared rules in SIR+

Every stock provider still owns its normal files:

commands.yml
lang.yml
optional files such as data.yml, menu.yml, or settings.yml

The SIR+ additions are:

provider state persisted in commands/states.yml
command override state also persisted there
addon and stock command coexistence decisions happening at runtime

Clear Chat

The clear-chat provider remains the stock moderation tool for wiping public chat.

What it owns

command registration
feedback text
stock moderation chat-clear behavior

This provider is simple, but it benefits from the SIR+ state model. If another plugin already owns a similar command label, you can decide whether the stock provider should stay active or whether override behavior should be relaxed.

Color

The color provider owns chat color and style selection.

Files

commands.yml
data.yml
lang.yml
menu.yml

Main command

/chat-color

Common aliases

chatcolor
color

Base permission

sir.color

Typical derived permissions

sir.color.black
sir.color.bold
sir.color.gradient
sir.color.reset

What it owns

per-player color state
menu-driven selection
user feedback
permission-based access to colors and styles

SIR+ angle

This is one of the clearest providers where command override control is useful. If your server already has another color command, you can avoid disabling the whole stock provider permanently until you decide the final command ownership model.

Ignore

The ignore provider manages personal ignore relationships.

Files

commands.yml
data.yml
lang.yml

Main command

/ignore

Alias

ig

Base permission

sir.ignore

What it owns

add and remove ignore relations
persisted ignore state
ignore-specific language feedback

SIR+ angle

Even if an addon introduces extra messaging behavior, the stock ignore layer still matters because it defines the baseline player expectation for private communication.

Message

The message provider owns stock private messaging.

Files

commands.yml
lang.yml

Commands

/message
/reply

Aliases

/message: m, msg, tell
/reply: r

Base permissions

sir.message
sir.reply

What it owns

direct private messages
reply continuity
the default private-message experience of the platform

SIR+ angle

This is one of the first providers to review when:

another plugin already owns /msg
an addon wants to provide custom PM logic
staff expect a different command label priority

Provider state and override state should be checked before assuming the feature is broken.

Mute

The mute provider owns stock mute administration.

Files

commands.yml
data.yml
lang.yml

Commands

/mute
/tempmute
/unmute
/check-mute

Base permissions

sir.mute
sir.temp-mute
sir.unmute
sir.check-mute

What it owns

permanent mute flow
timed mute flow
mute removal
mute lookup
persisted mute state

SIR+ angle

If an addon introduces advanced moderation, decide whether it should extend this provider or intentionally replace parts of the workflow. That decision affects both permissions and command override behavior.

Nick

The nick provider owns nickname changes.

Files

commands.yml
lang.yml

Main command

/nick

Alias

nickname

Main permissions

sir.nick
sir.nick.other

What it owns

self nickname changes
editing someone else's nick when permitted
nickname feedback text

SIR+ angle

This is a compact provider, but it is a useful example of how SIR+ still treats small command families as first-class managed providers with their own state and command ownership.

Print

The print provider is the stock raw-output command family for staff.

Files

commands.yml
lang.yml

Main command

/print

Common aliases

raw-message
raw-msg
rawmsg

Base permission

sir.print

Typical derived permissions

sir.print.targets
sir.print.chat
sir.print.action-bar
sir.print.title

What it owns

raw output to supported surfaces
target handling
feedback strings for operator tooling

SIR+ angle

If another staff plugin also owns a broadcast or raw-message command, this is a good candidate for explicit override review instead of blind command conflict guessing.

Settings

The settings provider owns player-facing communication preferences.

Files

commands.yml
lang.yml
settings.yml

Main command

/chat-settings

Common aliases

settings
chatsettings
csettings
c-settings

Base permission

sir.chat-settings

What it owns

player communication toggles
toggle metadata in settings.yml
the main stock preference surface for communication features

SIR+ angle

Addon features that use per-user toggles should be designed with this provider in mind. Even if the addon has its own commands, players will mentally group those settings with the built-in communication preference system.

Provider troubleshooting checklist

When a stock command family behaves strangely in SIR+:

confirm the provider is enabled in commands/states.yml
confirm the specific command override state is what you expect
inspect the provider's commands.yml for label and alias assumptions
inspect lang.yml or data.yml if the workflow is loading but acting oddly
only then decide whether another plugin or addon is the real source of the conflict

Built-in Command Providers

On this page