---
title: "AdvancedBan Warn Actions, MuteCommands and Punishment Ladder"
description: "Build a fair punishment ladder in AdvancedBan: automatic warn actions, MuteCommands, time layouts, duration limits for staff and example escalations."
url: "https://www.zcraftstudios.com/blog/advancedban-warn-actions-mutecommands-ladder"
updated: "2026-11-04T03:54:52.505345+00:00"
source: "ZCraft Studios"
---
> Site index for AI agents: https://www.zcraftstudios.com/llms.txt (full reference: https://www.zcraftstudios.com/llms-full.txt). Every page is available as Markdown by adding `.md` to its URL or sending `Accept: text/markdown`.
1. [Home](https://www.zcraftstudios.com/)
2. [Blog](https://www.zcraftstudios.com/blog)
3. AdvancedBan Warn Actions, MuteCommands and Punishment Ladder
[ All posts](https://www.zcraftstudios.com/blog)
# AdvancedBan Warn Actions, MuteCommands and Punishment Ladder
ZCraft StudiosNov 4, 2026
Build a fair punishment ladder in AdvancedBan: automatic warn actions, MuteCommands, time layouts, duration limits for staff and example escalations.
## In this guide
- [Design the ladder first](#design-the-ladder-first)
- [WarnActions](#warnactions)
- [MuteCommands](#mutecommands)
- [Message and time layouts](#message-and-time-layouts)
- [Limit how long staff can punish](#limit-how-long-staff-can-punish)
- [Staff workflow](#staff-workflow)
- [Message screens](#message-screens)
- [Test the ladder](#test-the-ladder)
- [Frequently asked questions](#frequently-asked-questions)
- [Related reading](#related-reading)
## AdvancedBan Warn Actions, MuteCommands and Punishment Ladder
**Quick answer:** use AdvancedBan's **`WarnActions`** to escalate automatically (for example a kick at 3 warnings and a temporary ban at 5), **`MuteCommands`** to stop muted players using private-message commands, **layouts** to keep reasons and durations consistent, and **duration permissions** to stop new staff handing out huge bans. Write the ladder down first, then configure it.
_Option names come from the plugin and fork documentation, last checked November 2026\. Compare with your generated `config.yml`, since layouts change between builds._
## Design the ladder first
| Offense | Warning | Second | Third |
| ---------------------- | --------------------- | --------------------- | ------------- |
| Spam | Warn | Temp mute | Longer mute |
| Language or harassment | Warn | Temp mute or temp ban | Longer ban |
| Griefing | Rollback and warn | Temp ban | Permanent ban |
| Exploiting | Warn | Temp ban | Permanent ban |
| Hacking | Temp ban after review | Permanent | n/a |
Publish it with your rules. See [Server Rules Template](https://www.zcraftstudios.com/blog/minecraft-server-rules-template-examples) and [Ban Appeal Process](https://www.zcraftstudios.com/blog/minecraft-server-ban-appeal-process).
## WarnActions
`WarnActions` runs commands automatically when a player reaches a number of warnings. A format that follows the default style:
```
WarnActions:
3: "kick %PLAYER% &cYou have been warned 3 times"
5: "tempban %PLAYER% 1d Too many warnings"
8: "ban %PLAYER% Repeated rule breaking"
```
Variables such as `%PLAYER%`, `%REASON%` and `%COUNT%` are available. Use the sample in your generated config as the exact template, and test on staging. Temporary warns that expire reduce the count over time, so decide whether that fits your ladder. See the [Commands Cheat Sheet](https://www.zcraftstudios.com/blog/advancedban-commands-permissions-cheat-sheet).
## MuteCommands
Muted players should still be unable to speak through other commands. `MuteCommands` lists the command names to block while muted. The default list covers commands such as:
- `me`, `say`, `action`, `describe`
- `msg`, `tell`, `w`, `whisper`, `pm`, `m`
- `r`, `er` and Essentials variants such as `emsg`, `etell`, `eme`
The config notes that the list also stops namespaced forms such as `/minecraft:me`. Add commands from other plugins, such as private-message commands from chat plugins or party plugins, so a mute is real. Test with a muted account.
## Message and time layouts
Layouts let staff apply a preset instead of typing a reason.
- **Message layouts** map a name to a ban or mute message.
- **Time layouts** increase the duration with each repeat offense for the same reason.
For example, a "spam" layout can start with a short mute and grow with each repeat. Staff then use `@layout` in the command. That makes enforcement consistent and easier to appeal. See the [Setup Guide](https://www.zcraftstudios.com/blog/advancedban-setup-guide).
## Limit how long staff can punish
AdvancedBan can limit punishment lengths by permission:
1. Create duration permission nodes for each staff group.
2. Map each node to a number of seconds in the config's duration table.
3. Give each group the node that matches its limit.
A new helper can then give short mutes and temporary bans, and only senior staff can issue permanent punishments. See [Staff Training Checklist](https://www.zcraftstudios.com/blog/minecraft-server-staff-onboarding).
## Staff workflow
1. Check `/history` before every punishment.
2. Always give a reason.
3. Record evidence in a ticket. See [Discord Ticket Systems](https://www.zcraftstudios.com/blog/minecraft-server-discord-ticket-workflow).
4. Use `/change-reason` to fix mistakes rather than removing records.
5. Review appeals with someone not involved.
## Message screens
Ban and mute screens are the most-read text on your server. Keep them short, state the reason and duration, and link to your appeal page. If you want a ready-made set, the ZCraft [AdvancedBans Messages Config](https://www.zcraftstudios.com/products/advancedbans-messages-config) provides styled screens in English and Spanish. Follow the pack's README to install it.
## Test the ladder
1. Use a test account and a staff account on staging.
2. Issue warnings and confirm each action triggers.
3. Mute the test account and try every command in `MuteCommands`.
4. Check that staff duration limits apply.
5. Restart and confirm punishments persist.
## Frequently asked questions
**What are WarnActions in AdvancedBan?** Commands that run automatically at set warning counts.
**What does MuteCommands do?** Blocks the listed commands for muted players.
**How do I stop moderators banning for too long?** Use duration permissions and the config's duration table.
**What is a time layout?** A preset that lengthens the punishment with each repeat of the same reason.
**Can I escalate bans automatically?** Yes, through layouts and warn actions.
## Related reading
- [AdvancedBan Commands and Permissions: Cheat Sheet](https://www.zcraftstudios.com/blog/advancedban-commands-permissions-cheat-sheet)
- [AdvancedBan Not Working? Fixes](https://www.zcraftstudios.com/blog/advancedban-not-working-fixes)
- [Best Anti-Cheat Plugins](https://www.zcraftstudios.com/blog/minecraft-anticheat-plugins-compared)
## Continue reading
- [AdvancedBan Not Working? Permissions, MySQL and Command Fixes](https://www.zcraftstudios.com/blog/advancedban-not-working-fixes)
- [AdvancedBan Alternatives: AdvancedBanX, LibertyBans, LiteBans](https://www.zcraftstudios.com/blog/advancedban-alternatives-advancedbanx-libertybans-litebans)
- [AdvancedBan Commands and Permissions: Cheat Sheet](https://www.zcraftstudios.com/blog/advancedban-commands-permissions-cheat-sheet)
- [AdvancedBan on a Network: MySQL, BungeeCord and Velocity](https://www.zcraftstudios.com/blog/advancedban-network-mysql-bungeecord-velocity-setup)
[ Previous guide AdvancedBan Commands and Permissions: Cheat Sheet](https://www.zcraftstudios.com/blog/advancedban-commands-permissions-cheat-sheet)[ Next guide AdvancedBan Alternatives: AdvancedBanX, LibertyBans, LiteBans](https://www.zcraftstudios.com/blog/advancedban-alternatives-advancedbanx-libertybans-litebans)