SelfCommands

SelfCommands

Players create their own shortcuts. /hub, /kit pvp followed by /heal, a welcome broadcast, whatever they use often enough to get tired of typing.

Action types

Type - What it does - Permission

• command - Runs the payload as the player - none by default
• console - Runs the payload from the console - selfcommands.admin
• message - Shows the player text, with title: and actionbar: prefixes - none by default
• bungeecord - Connects the player to another server - selfcommands.type.bungee

A type whose permission is missing from the configuration is refused, not allowed. The unsafe direction is never the default.

Commands

Command - What it does

• /sc create <name> <type> <action> - Create an alias
• /sc edit <name> <type> <action> - Change one
• /sc delete <name> - Remove one
• /sc list - List your aliases
• /sc info <name> - Show the detail
• /sc manage <player> <list|delete|clear|give> - Inspect and change another player's aliases
• /sc reload - Reload the configuration

/selfcmd, /selfcommand and /scmd are aliases.

Limits and safety

A per player alias limit, raised with selfcommands.limit.<n> A cooldown, bypassed with selfcommands.cooldown.bypass A blacklist of commands nobody may wrap. It is applied to every command in a chain, not only the first, so /heal; op me is refused rather than half executed. The check also splits on &&, ||, | and newlines, which this plugin does not treat as chains, so an alias cannot be stored in a form another plugin might chain later The type permission is checked again at the moment the alias runs, so revoking a permission takes effect immediately instead of when the alias is next edited

Storage

SQLite or MySQL. Aliases are held in memory per online player and loaded on join, so running one costs no database query.