How to Ban, Mute, and Warn Players, LiteBans & AdvancedBan Guide

Running a Minecraft server means dealing with rule-breakers. Whether it is a player spamming chat, griefing builds, using hacked clients, or harassing other players, you need a structured punishment system. The vanilla /ban command exists, but it lacks temporary bans, mute functionality, warning systems, and any kind of history tracking. This guide covers the two leading punishment plugins, LiteBans and AdvancedBan, and walks through best practices for fair, consistent moderation.

Vanilla /ban, why it is not enough

Minecraft's built-in ban command is bare bones. It supports permanent bans and IP bans, but nothing else:

/ban PlayerName Reason here
/ban-ip 192.168.1.1 Reason here
/pardon PlayerName
/pardon-ip 192.168.1.1
/kick PlayerName Reason here

There is no /tempban, no /mute, no /warn, no punishment history, and no web interface. The ban list is stored in banned-players.json, a flat file that does not sync across a network. For any server with more than a handful of players and a single moderator, you need a plugin.

LiteBans vs AdvancedBan comparison

Feature	LiteBans	AdvancedBan
Price	Premium ($8)	Free
Database	MySQL, PostgreSQL, MariaDB, H2	MySQL, HSQLDB (file-based)
Multi-server sync	Yes (real-time via shared DB)	Yes (via MySQL)
Web interface	Yes (built-in web page)	No (third-party tools only)
UUID support	Full (online + offline mode)	Full
Proxy support	BungeeCord, Velocity	BungeeCord
Warning escalation	Via command templates	Built-in warning thresholds
Silent punishments	Yes (-s flag)	Yes
Active development	Active	Maintenance mode
Broadcast messages	Fully customizable	Fully customizable

LiteBans costs a few dollars but earns it with real-time database sync, a built-in ban page, active development, and polished configuration. AdvancedBan is free and covers the basics well, but development has slowed and it lacks a native web interface. For serious servers, LiteBans is the investment that pays for itself in saved admin time.

Installing LiteBans

1. Purchase and download from SpigotMC.
2. Place LiteBans.jar in your plugins/ folder.
3. Restart the server. LiteBans creates plugins/LiteBans/config.yml and messages.yml.
4. Configure the database backend (see MySQL section below).
5. Reload with /litebans reload.

LiteBans works immediately with its default H2 file-based database. You can start using it right away and migrate to MySQL later when you need cross-server sync.

Core punishment commands

Both LiteBans and AdvancedBan share similar command syntax. These examples use LiteBans format:

Banning

/ban PlayerName Hacking (x-ray confirmed via CoreProtect)
/tempban PlayerName 7d Griefing, first offense
/tempban PlayerName 30d Griefing, second offense
/unban PlayerName

Always include a reason. "Hacking" is too vague, "Using x-ray resource pack, confirmed via CoreProtect inspection" gives context for appeal reviews.

Muting

/mute PlayerName Spam
/tempmute PlayerName 1h Chat spam, first warning
/unmute PlayerName

Muted players cannot send chat messages but can still play normally. This is appropriate for chat violations where a ban would be disproportionate.

Warning

/warn PlayerName Language, keep chat respectful
/unwarn PlayerName

Warnings are recorded in the player's history. After a configurable number of warnings, you can escalate automatically (e.g., three warnings triggers a 24-hour tempban). LiteBans handles this through custom command templates that execute on warning thresholds.

Kicking

/kick PlayerName AFK too long, server full

Kicks disconnect the player immediately but do not prevent them from rejoining. Use kicks for soft enforcement, AFK players during peak hours, players asked to restart their client, or as an immediate interruption during an active incident while you decide on a ban length.

Silent punishments

/ban -s PlayerName Under investigation

The -s flag applies the punishment without broadcasting it to the server. Useful when you are investigating a suspected hacker and do not want to alert their associates.

IP bans and evasion

/ipban PlayerName Ban evasion on alt accounts
/unbanip 192.168.1.1

IP bans block all accounts connecting from that IP address. They are a blunt tool, shared IPs (college campuses, VPNs, some ISPs) mean you might accidentally ban innocent players. Use IP bans sparingly and only for confirmed ban evaders. LiteBans also supports range bans for blocking IP ranges, but this is even riskier and should only be used against targeted attacks.

Punishment history

/history PlayerName
/banlist
/warnings PlayerName

/history shows every punishment a player has received, active and expired bans, mutes, warns, and kicks. This is invaluable for escalation decisions. A first-time griefer gets a 3-day tempban; checking their history and finding two prior warnings and a previous tempban justifies escalating to 30 days or permanent.

MySQL for multi-server sync

If you run a network with multiple servers behind BungeeCord or Velocity, a shared MySQL database makes bans apply everywhere instantly. One moderator bans a player on the survival server, and that player is immediately banned from the creative server, the minigames hub, and every other backend.

# LiteBans config.yml
sql:
  driver: MySQL
  address: 127.0.0.1:3306
  database: litebans
  username: litebans_user
  password: "strong-password"

Every server in the network points to the same database. LiteBans uses connection pooling (HikariCP) for efficient database access, so even busy networks with 200+ concurrent players handle ban lookups without TPS impact.

Setting up a public ban page

LiteBans includes a PHP-based web interface that displays active bans, mutes, and kicks on a public web page. Players can look up their punishment history, and transparency builds community trust.

1. Upload the web/ folder from the LiteBans download to your web server (Apache or Nginx with PHP).
2. Edit settings.php with your MySQL credentials.
3. Access the page at your domain (e.g., bans.yourserver.com).

The ban page shows the player's name, reason, duration, banning staff member, and date. You can customize the theme, add your server logo, and restrict which punishment types are publicly visible.

Building an appeal process

No punishment system is complete without a way for players to appeal. Mistakes happen, moderators misread CoreProtect logs, automated anti-cheat flags false positive, or circumstances are more nuanced than they appeared. A fair appeal process typically includes:

• A form or Discord channel, Google Forms, a forum section, or a dedicated Discord channel where banned players can submit appeals.
• Required information, username, ban reason (from the ban screen), explanation of what happened, and why the ban should be reconsidered.
• Staff review, a senior moderator or admin reviews the appeal, checks the player's /history, reviews CoreProtect evidence, and makes a decision.
• Response, reply to every appeal, even denials. "Appeal denied, evidence clearly shows x-ray mining pattern in CoreProtect logs" is better than silence.

Punishment guidelines, a suggested escalation ladder

Offense	First	Second	Third
Chat spam / mild toxicity	Warning	1h tempmute	24h tempmute
Slurs / hate speech	7d tempmute	30d tempmute	Permanent mute
Minor griefing (few blocks)	Warning + rollback	3d tempban	7d tempban
Major griefing (base destruction)	7d tempban	30d tempban	Permanent ban
Hacking (x-ray, fly, kill aura)	30d tempban	Permanent ban
DDoS threats / doxxing	Permanent ban + IP ban

Adapt this to your community. Stricter servers move the permanent ban threshold earlier; lenient communities give more chances. The key is consistency, apply the same standards to everyone, including staff members and their friends.

Common mistakes

• Permanent banning without evidence, always check CoreProtect before banning for griefing. /co inspect proves exactly who broke what and when. Without evidence, your appeal process becomes unwinnable arguments.
• Not recording reasons, /ban PlayerName with no reason leaves future staff guessing. Always include a clear, specific reason.
• Over-relying on IP bans, most players have dynamic IPs, so IP bans expire naturally when the ISP rotates addresses. They also hit shared households and public networks. Use them as a supplement, not a primary tool.
• Banning in anger, if a player is actively disrupting the server, kick them first to stop the immediate damage, then investigate calmly with CoreProtect and make a measured decision.
• No staff training, every moderator should understand the escalation ladder, know how to use CoreProtect and the ban plugin, and have clear guidelines on when to escalate to senior staff. Document your rules in a staff handbook and use LuckPerms to restrict which punishment commands each staff rank can use.

Need reliable hosting for your server? Astroworld Hosting offers NVMe SSD, Pterodactyl panel, and DDoS protection. See features , plans from €6.39/mo.