Chat is the lifeblood of a multiplayer Minecraft server, but it is also where the trouble starts. Spam, slurs, advertising, arguments that boil over mid-raid — every server owner eventually meets a player who needs to be silenced for a while without being kicked or banned. The cleanest tool for that job is a temporary mute: the player stays online and keeps playing, but their messages stop reaching public chat until a timer runs out. This guide covers exactly how to set that up, the precise command syntax, the permission nodes involved, and the things vanilla Minecraft simply cannot do on its own.
There is no vanilla mute command
This is the single most important fact to understand before you start: vanilla Minecraft (Java Edition) has no mute or temp-mute command at all. If you are running the plain server.jar downloaded straight from Mojang, your moderation toolkit is limited to the built-in operator commands — /op, /deop, /kick, /ban, /ban-ip, /pardon, /whitelist, and friends. Notice what is missing from that list: there is no /mute, no /tempmute, and crucially the built-in /ban is permanent only — it has no duration argument either.
That means to temp-mute anyone, you need two things working together: a server fork that can load plugins, and a moderation plugin that adds the mute command. The community standard for both is Paper or Spigot (the fork) plus EssentialsX (the plugin). The vanilla Mojang jar cannot load plugins under any circumstances, so this is the foundational requirement for everything below.
What you need: Paper/Spigot + EssentialsX
Plugins are loaded by the Bukkit API, which the vanilla server does not implement. To get that API you run one of the Bukkit-family forks instead of the Mojang jar:
- Paper — the most popular high-performance fork; recommended for almost every server.
- Spigot — Paper’s upstream; works but Paper is faster and has more built-in features.
- Bukkit / Purpur / Folia — other options in the same family that also load plugins.
On top of that fork you install EssentialsX, the long-running moderation-and-utility plugin that provides kick, tempban, jail, kits, warps, homes, an economy, and — what we care about here — /mute. Drop the EssentialsX jar into your server’s plugins/ folder and restart. If you run XGamingServer, you can install Paper and EssentialsX in a couple of clicks from the control panel; our managed Minecraft hosting plans ship with one-click Paper installs and plugin management so you are not wrestling with jar files by hand. The full panel walkthrough lives in our Minecraft server documentation.
The /mute command and how temp-mute works
EssentialsX provides a dedicated /tempmute command (with its own essentials.tempmute permission node), but you do not strictly need it: the regular /mute command also becomes a temporary mute the moment you add a duration argument, so /mute Steve 10m spamming and /tempmute Steve 10m spamming achieve the same thing. Leave the duration off and the mute is permanent (until manually lifted); add a duration and it auto-expires. The general form is:
/mute [duration] [reason] Here is how each piece behaves:
- Permanent mute:
/mute Steve— silences the player indefinitely. - Temp-mute (with duration):
/mute Steve 10m— silences the player for ten minutes, then they can chat again automatically. - Temp-mute with a reason:
/mute Steve 1h Spamming chat— adds a reason that is logged and typically shown to the muted player.
Duration strings use compact time units. Common ones you will use every day:
| Example command | Effect |
|---|---|
/mute Alex 30s | Mute for 30 seconds |
/mute Alex 15m | Mute for 15 minutes |
/mute Alex 2h | Mute for 2 hours |
/mute Alex 1d | Mute for 1 day |
/mute Alex 7d Repeated advertising | Mute for 7 days, reason attached |
/mute Alex | Permanent mute (no expiry) |
You can run these from the in-game chat as an operator, or straight from the server console. From the console you typically omit the leading slash — the console always runs at the equivalent of permission level 4, so it can issue any command without being opped.
What a mute actually does to the player
A mute is a chat restriction only. The muted player stays connected and can keep doing everything else — mine, build, fight, use commands they have access to, and move freely around the world. What changes is that their public chat messages no longer reach other players. When they try to talk, EssentialsX intercepts the message and tells them they are muted (and, if you set one, shows the reason and remaining time). This is exactly what you want for a chat-only offense: you stop the disruption without disrupting their actual gameplay.
How to unmute a player
Temp-mutes expire on their own, but you will often want to lift one early — the player apologized, or you muted the wrong person. In EssentialsX the unmute is the same /mute command run a second time on an already-muted player: running it again toggles the mute off.
# Lift the mute on a currently-muted player
/mute SteveIf /mute is run while the player is muted, it removes the mute; if they are not muted, it applies a permanent one. Because of that toggle behavior, always check the player’s current status before re-running the command so you do not accidentally re-mute someone you meant to free. If you are ever unsure, lift it explicitly and watch the confirmation message the plugin returns.
Permission nodes: essentials.mute
By default an operator can run /mute because ops bypass most permission checks. But on a real server you usually do not want to hand out full op (level 4 — that includes /stop and /op) just so a moderator can mute spammers. Instead you grant the specific EssentialsX permission node through a permissions plugin such as LuckPerms. The core node is:
essentials.muteEssentialsX uses the essentials. format for all of its command permissions, and an important quirk to remember is that these nodes are not automatically inclusive — granting one node does not silently grant related ones. There may be additional related nodes around mute behavior (for example, exemptions so trusted staff cannot themselves be muted, or nodes governing the maximum mute duration a moderator can apply). Because the exact node strings can change between EssentialsX versions, always confirm the current node names against the official essentialsx.net/wiki before locking down your permission groups.
A typical moderator group would receive essentials.mute, essentials.kick, and essentials.tempban but not server-management nodes — giving them the day-to-day chat-control tools without the keys to the whole server.
Mute vs. kick vs. ban: when to use which
Muting is the lightest touch on the moderation ladder. Knowing where it sits relative to kicks and bans keeps your enforcement proportional:
| Action | Player stays online? | Built-in to vanilla? | Use it for |
|---|---|---|---|
Mute (/mute) | Yes — only chat is blocked | No — EssentialsX | Spam, insults, advertising in chat |
Kick (/kick) | No — disconnected, can rejoin instantly | Yes | A quick “knock it off” / clearing a stuck client |
Temp-ban (/tempban) | No — locked out for a set time | No — EssentialsX | Serious but forgivable offenses |
Ban (/ban) | No — locked out permanently | Yes (permanent only) | Griefing, cheating, repeat offenders |
The key distinction from a ban is that a mute keeps the player in the game — they lose their voice, not their access. A ban removes them from the server entirely. Reach for a mute when the problem is purely what they are saying, not what they are doing to your world. If the offense escalates to griefing or cheating, step up to a temp-ban; our companion guide on how to temp-ban a player walks through the /tempban workflow, which mirrors the mute syntax almost exactly.
Operator levels and who can mute
Minecraft’s vanilla permission system uses four operator levels, set in ops.json and granted via /op (which by default hands out the level defined by op-permission-level in server.properties — that default is 4). The levels are cumulative:
- Level 1 (Moderator): can bypass spawn protection.
- Level 2 (Gamemaster): command blocks,
/difficulty, target selectors, most cheat commands. - Level 3 (Admin): multiplayer-management commands like
/ban,/kick,/whitelist, and op-ing others. - Level 4 (Owner): everything, including
/stopand/save-all.
This matters for muting because EssentialsX commands sit on top of this system. An op will be able to mute, but the cleaner approach for staff is the permission-node method above — it lets a trusted moderator mute without granting the broad powers that come bundled with a high op level. To assign a custom op level (say, level 1 for a junior helper), edit the level field in ops.json directly, since the /op command always grants the configured op-permission-level rather than a per-player value.
Bonus: cleaner chat with EssentialsX
Once you have EssentialsX installed for muting, it unlocks a lot of other chat-management quality-of-life features. For example, the same plugin controls the join and leave announcements via custom-join-message and custom-quit-message in its config.yml — set them to an empty string ("") to hide those messages entirely. If a flood of join/leave spam is part of your chat-noise problem, see our guide on disabling the joining and leaving messages. EssentialsX is genuinely the Swiss-army knife of Bukkit moderation, so it is worth reading through its config once you have it running.
Frequently asked questions
Is there a temp-mute command in vanilla Minecraft?
No. Vanilla Minecraft Java Edition has no mute or temp-mute command of any kind — and its built-in /ban is permanent-only with no duration option either. To temp-mute a player you must run a Bukkit-family fork (Paper, Spigot, Purpur, etc.) and install a moderation plugin such as EssentialsX, which adds /mute . There is no way to mute a player on a stock Mojang server.jar.
How do I mute a player for 10 minutes with EssentialsX?
Run /mute — for example /mute Steve 10m. The duration unit suffixes are s (seconds), m (minutes), h (hours), and d (days), so 2h is two hours and 1d is one day. You can append a reason after the duration, like /mute Steve 10m Spamming, which is logged and shown to the player. The mute lifts itself automatically when the timer expires.
How do I unmute a player early?
Run the /mute command again on the same player while they are muted — /mute Steve — and it toggles the mute off. Because the command toggles, running it on a player who is not currently muted will instead apply a new permanent mute, so verify their status first and read the confirmation message the plugin returns to be sure the mute was lifted.
What permission node lets a moderator mute without being op?
Grant the essentials.mute permission node through a permissions plugin like LuckPerms. EssentialsX nodes follow the essentials. pattern and are not automatically inclusive, so granting one does not grant related nodes. There may be additional nodes for mute exemptions or maximum durations depending on your EssentialsX version — check the current node names on the official EssentialsX wiki before finalizing your staff permission groups.
What is the difference between muting and banning a player?
A mute only blocks the player’s public chat — they remain online and can keep playing the game normally. A ban removes them from the server entirely (permanently with vanilla /ban, or for a set time with EssentialsX /tempban). Use a mute for chat-only offenses like spam or insults; escalate to a temp-ban or ban for griefing, cheating, or repeat offenders who need to be removed rather than silenced.
Does a muted player know they are muted?
Yes. When a muted player tries to send a chat message, EssentialsX intercepts it and notifies them that they are muted. If you attached a reason and a duration to the mute (for example /mute Steve 1h Advertising), the plugin can show that reason and the remaining time, so the player understands why they were silenced and when chat access returns.
What else should I configure on a new Minecraft server?
Once moderation is sorted, common next steps include enabling Paper’s built-in anti-cheat protections — see enabling Anti-Xray to stop x-ray cheaters — and tuning world settings such as the level type in server.properties. Between EssentialsX for moderation, Paper for performance and anti-cheat, and a permissions plugin for clean staff roles, you will have a server that is both pleasant to play on and easy to run.
The bottom line: temp-muting is a Paper/Spigot + EssentialsX feature, driven entirely by one flexible command — /mute — with the same command toggling the mute back off and the essentials.mute node letting your staff use it without full op. Keep mutes for chat problems, kicks for quick interruptions, and bans for the offenses that warrant removing a player from your world.
Free Minecraft Tools
Speed up your server with our free Minecraft tools:
Ready to play?
Run your own Minecraft server with XGamingServer
Spin up an always-on Minecraft server your friends can join in minutes — no port-forwarding, no tech headaches.
