Commands
Moderation commands
Ban, IP ban, mute, warn, kick, blacklist, history, related accounts, reports and helpop commands with their permissions and examples.
The default root is /punish, and every action also has a direct command (/ban, /mute...). The root accepts the same actions: /punish ban ..., /punish reports .... If another plugin occupies the configured root, /sofycore:moderation remains available as a recovery root.
Sanctions
/ban <player|uuid> <duration> <reason...> [-s] [-c]Global account ban. -c clears the target's inventory first (same server, sofycore.sanctions.clear).
- Permission
sofycore.sanctions.ban- Also requires
- STAFF authority and a strictly higher rank than the target.
Arguments
player(required) — Known player name or UUID.duration(required) — 30s, 10m, 2h, 7d or permanent.reason(required) — Free text, up to 256 characters.-s(optional) — Silent: only permitted staff see the announcement.
Examples
/ban Steve 7d Cheating /ban Steve permanent Chargeback -s
/ipban <ip|player> <duration> <reason...> [-s] [-c]Bans that exact IP. A player resolves to their last registered IP.
- Permission
sofycore.sanctions.ipban
/mute <player|uuid> <duration> <reason...> [-s]Global mute for chat and private messages.
- Permission
sofycore.sanctions.mute
Examples
/mute Steve 10m Spam
/warn <player|uuid> <duration|default> <reason...> [-s]Expiring warning. Active warnings can trigger automatic consequences (by default 3 → 10 min mute, 5 → 1 h ban).
- Permission
sofycore.sanctions.warn
/kick <online-player> <reason...> [-s] [-c]Kicks that confirmed connection.
- Permission
sofycore.sanctions.kick
/unban | /unipban | /unmute <target> <reason...> [-s]Removes the active sanction (permissions sofycore.sanctions.unban, .unipban, .unmute). Removing a sanction issued by someone else requires a higher rank than its issuer.
- Permission
sofycore.sanctions.unban
/unwarn <player|uuid> <warn-uuid> <reason...> [-s]Removes one active warning.
- Permission
sofycore.sanctions.unwarn
/blacklist <add|remove|list> [name|ip] [reason...]Permanent literal name or IP blacklist. /unblacklist is the same removal action.
- Permission
sofycore.sanctions.blacklist- Also requires
- OWNER authority or console for changes.
/history <player|uuid|ip|name:nick> [cursor]Full history including expired, replaced and removed sanctions. Without arguments (or /punishinfo) shows your own, with sofycore.sanctions.history.own.
- Permission
sofycore.sanctions.history
/staffhistory <player|uuid|console> [cursor]Actions issued by a staff member.
- Permission
sofycore.sanctions.history
/ips <player|uuid> · /related <ip> [cursor]Up to 16 recent distinct IPs of an account, and accounts seen on an IP. Does not sanction them.
- Permission
sofycore.sanctions.ips
/punish config <show|language|root|command|warn-duration|threshold|type> ...Persisted, network-wide moderation settings: language, command labels, warn duration, thresholds and report types.
- Permission
sofycore.moderation.configure- Also requires
- OWNER authority or console.
Examples
/punish config threshold 3 MUTE:600 /punish config type griefing Griefing
Reports and help
/report <online-player> <type> [details...]Files a report (60 s cooldown). Default types: killaura, reach, fly, speed, antiknockback, xray, autoclicker, other. Opens a menu when used with only the player and menus are enabled.
- Permission
sofycore.reports.use
Examples
/report Steve fly flying near spawn
/reports <list|inspect|take|release|resolve|dismiss> ...Open report queue: inspect, take, release, resolve or dismiss.
- Permission
sofycore.reports.manage
/helpop <message...>Sends a message to the staff of every server (30 s cooldown).
- Permission
sofycore.helpop.use
Rules shared by every action
- Durations:
30s,10m,2h,7d.permanentis accepted for ban, IP ban and mute;defaultuses the stored warning duration. Warnings must expire. -s: limits the announcement to staff withsofycore.sanctions.notify. It does not hide the sanction or its reason from the affected player.-c: on/ban,/ipbanand/kick, clears the target's inventory first. Only works when both players are on the same server.- Hierarchy: staff permissions are not enough on their own. Actions also require internal STAFF authority and a strictly higher rank than the target.
- Reasons and details are limited to 256 characters.