Silent Punishments
Punish a player without making a public scene.
A silent punishment is a real punishment that is never announced. The player is banned, muted, or
warned for real and sees the normal screen or message, but nothing is broadcast to the server. Only
staff with the phantombans.silent.see permission get a quiet note about who did it. To everyone
else, it just looks like the player left or went quiet.
This is useful when you want to act on a suspected cheater or troublemaker without warning them, and without starting a public reaction.
How it works
Add the -s flag to any ban or mute command, or use the dedicated alias commands. Both do the same
thing: the punishment is applied normally, but the public broadcast is suppressed and only staff with
phantombans.silent.see are notified.
The -s flag needs phantombans.silent.use. The notice goes to staff holding
phantombans.silent.see.
Commands
Silent Ban
/ban <player> [duration] [reason] -s
/silentban <player> [duration] [reason]
/unsilentban <player>/silentban is simply an alias of /ban -s. The player is banned for real: they are kicked, cannot
rejoin, and see the normal ban screen. Nothing is announced. Staff with phantombans.silent.see get
a quiet notice naming who did it.
Who sees what
| Audience | What they see |
|---|---|
| The punished player | The normal ban screen or mute message, like any other punishment |
| The rest of the server | Nothing at all |
Staff with phantombans.silent.see | A quiet message naming the staff member who acted |
Lifting a silent punishment is also quiet, so it does not give the game away. Use /unsilentban or
/unsilentmute (or /unban -s and /unmute -s).
Keep the reason generic
Because the player still sees the screen or message, keep the default reason generic (for example “You have been banned”). That way the player cannot tell a silent punishment apart from a normal one. You can set these defaults in the config.
History
Silent punishments still appear in a player’s history, so your team always has the full record even though the server never saw it happen.
The phantombans.silent.see permission is powerful. Only give it to staff you trust. See
Permissions.