Commands

Commands

All administration commands support console where meaningful. Commands accept known offline names or UUIDs. IP ban/mute commands additionally accept literal IPv4/IPv6 addresses; hostnames are not resolved. Names never serve as punishment primary identities.

CommandPurpose
/punish <player> <template> [-s]Apply the current policy step
/punish <player>Open policy selection GUI
/punish preview <player> <template>Preview without mutation
/punish <player> <template> --previewAlternate preview syntax
/ban <player> [duration] [reason]Account ban
/tempban <player> <duration> [reason]Temporary account ban
/ipban <player-or-ip> [duration] [reason]IP ban
/mute, /tempmute, /ipmuteCorresponding chat punishments
/warn <player> [reason]Expiring warning and threshold actions
/kick <player> [reason]Network kick with history entry
/unban, /unmute, /unwarn <player> [reason]Remove eligible active punishments, including applicable IP punishments
/checkban, /checkmute, /checkwarn <player>Inspect active punishments and scopes
/history <player> [page]Player GUI history; console text
/staffhistory <staff> [page]Issuance and removal history
/staffrollback <staff> [duration] [confirm]Revoke eligible active punishments from that issuer
/warnings [player] [page]Warning GUI/history; ordinary players may inspect themselves
/banlist [page]Active-ban GUI, always
/mutelist, /warnlist [page]Paginated text lists
/iphistory <player> [page]Observed IP history; sensitive permission required
/namehistory <player> [page]Observed names
/dupeip, /alts <player> [page]Linked-account GUI or configured chat report
/lastuuid <player>Most recently observed UUID for a current username
/prunehistory <player> [duration] [confirm]Hide inactive records while retaining history
/ipreport [page]Addresses associated with many observed accounts
/lockdown <reason> or /lockdown endNetwork admission control
/wrongpunish reloadValidate and reload all configuration files
/wrongpunish info, /wrongpunish debugVersion, database type, cache and sync health; no credentials
/wrongpunish template <name>Display ladder policy
/wrongpunish template <name> <player>Inspect persisted offense and next policy
/wrongpunish modify <id> duration <duration>Change expiration relative to now
/wrongpunish modify <id> reason "Updated reason"Audited reason update
/wrongpunish modify <id> active falseAudited removal; removed entries cannot be reactivated

Shared punishment flags: -s, --silent, --ip, --server=<server>, --scope=<scope>, --reason="some reason". Template IP mode is controlled by its policy, not an --ip override. Aliases are configured under commands.aliases and updated on reload; canonical names remain available. Alias collisions and malformed names cause validation failure.

Durations: s, m, h, d, w, mo, y; combinations such as 1d12h; readable forms such as 30 minutes, 3 months; and permanent, perm, forever. A month is a fixed 30 days and a year is 365 days. Temporary command variants require a finite duration. Numeric input is overflow-checked, and the maximum supported duration is 100 years.

Permissions, aliases and execution context

Canonical commands normally require wrongpunish.<command>. Removal also accepts the corresponding .own grant. /alts also accepts wrongpunish.dupeip. Root subcommands use wrongpunish.reload, wrongpunish.admin or wrongpunish.modify; template inspection also accepts template authorization. Self /warnings is available to ordinary players.

Default aliases: /wp → /wrongpunish, /p → /punish, /phistory → /history, /accounts → /alts. Configure other aliases in commands.aliases.

Issuance, previews, checks, text lists and administration work from console. /punish <player> and /banlist require a player for inventory display; history is text for console.