--- title: "Setting Up LiteBans for Ban, Mute, and Kick Logging | ZCS" description: "Install LiteBans for bans, mutes and kicks with a database, commands, history and a web interface, then test punishments safely." url: "https://www.zcraftstudios.com/blog/litebans-setup-guide" updated: "2026-10-20T07:16:50.972429+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. Setting Up LiteBans for Ban, Mute, and Kick Logging [ All posts](https://www.zcraftstudios.com/blog) # Setting Up LiteBans for Ban, Mute, and Kick Logging ZCraft StudiosOct 3, 2026Updated Oct 20, 2026 Install LiteBans for bans, mutes and kicks with a database, commands, history and a web interface, then test punishments safely. ## In this guide - [Install LiteBans](#install-litebans) - [Basic Punishment Commands](#basic-punishment-commands) - [Viewing Punishment History](#viewing-punishment-history) - [Checking Who Issued a Punishment](#checking-who-issued-a-punishment) - [Setting Up Punishment Appeals](#setting-up-punishment-appeals) - [Customizing Punishment Messages](#customizing-punishment-messages) - [Syncing Across a Network](#syncing-across-a-network) - [Moderation integration check](#moderation-integration-check) - [Troubleshooting: Punishment does not synchronize](#troubleshooting-punishment-does-not-synchronize) - [Build an evidence and recovery route for staff](#build-an-evidence-and-recovery-route-for-staff) - [Official documentation and links](#official-documentation-and-links) - [Verify punishments survive a restart](#verify-punishments-survive-a-restart) ## Setting Up LiteBans for Ban, Mute, and Kick Logging _Banning a player is one command. Knowing their full punishment history six months later needs a plugin actually built for that._ LiteBans is a dedicated punishment plugin for bans, mutes, kicks, and warnings, each logged with a timestamp, staff member, reason, and duration. It's built to be the single source of truth for a server's moderation history, rather than relying on console logs or memory. ## Install LiteBans [LiteBansPunishment history and database-backed moderation for servers and networks.On SpigotMC ](https://www.spigotmc.org/resources/litebans.3715/) Download LiteBans from the project linked above. Check the supported Minecraft version, server platform, Java requirement and dependencies for the selected release. 1. Back up the server files and any plugin database. 2. Stop the server before changing JAR files. Put the compatible plugin build and its required dependencies in the correct plugin folder. 3. Start the server and read the startup log. Resolve missing dependencies or version errors before editing the generated configuration. 4. Stop the server, make one small configuration change, then restart and test it with a non-operator account. Back up the punishment database before upgrades. Test a temporary punishment and its expiry on staging before granting staff access. ## Basic Punishment Commands ``` /ban [reason] /tempban [reason] /mute [duration] [reason] /kick [reason] /warn [reason] /unban /unmute ``` Duration shorthand works directly in the command: `/tempban Player 7d Rule violation`. ## Viewing Punishment History ``` /history ``` shows every punishment a player has received, including expired ones. This is the feature that separates LiteBans from basic ban commands. ## Checking Who Issued a Punishment ``` /banlist /mutelist ``` list currently active bans/mutes, including which staff member issued each one, which is useful for accountability and reviewing staff decisions later. ## Setting Up Punishment Appeals LiteBans itself doesn't include an appeal system. That typically lives on a Discord server or web form separately, with staff cross-referencing `/history` to review the original punishment before deciding on an appeal. ## Customizing Punishment Messages The default kick/ban/mute screens are functional but generic. `messages.yml` controls exactly what a punished player sees, including the reason, duration, and who issued it. This is the single file most servers end up customizing, since it's one of the few LiteBans screens every punished player actually sees directly. ZCraft Studios' **[LiteBans Message Templates](https://www.zcraftstudios.com/products/litebans-message-templates)** is a ready-made version of this file if writing the MiniMessage formatting from scratch isn't worth the time. ## Syncing Across a Network For punishments to apply network-wide (a ban on one backend server blocking the player everywhere), LiteBans needs to be installed on every backend server, all pointed at the same MySQL database. A player banned on one server but not synced to the others can simply reconnect through a different backend. ## Moderation integration check Confirm that bans, temporary bans, mutes, warnings and appeals match your published staff rules. Test whether punishments work across proxy-connected servers, if relevant. Verify database connectivity and backups, then check that role permissions prevent staff from accessing destructive or high-impact commands unnecessarily. ## Troubleshooting: Punishment does not synchronize On a network, confirm that each relevant server or proxy component uses a supported integration and points to the intended data store. Check startup errors and whether the user's identity is forwarded consistently. A punishment visible in one backend is not proof that it applies everywhere. ### How to verify the fix Create a temporary test punishment, switch between backend servers and verify the documented expiration and appeal flow. Avoid testing irreversible punishment actions on real players. ## Build an evidence and recovery route for staff Choose a short record format containing the player identity, reason, evidence reference and issuing staff member. Test whether another moderator can reconstruct the case from those records. Keep sensitive evidence in a restricted place rather than in public punishment messages. When a sanction is disputed, preserve the original record before changing it. The appeal decision should explain the outcome without exposing unrelated players or private staff discussion. On a network, review the documented installation and enforcement model for your exact setup. Test punishment visibility, expiry and removal from more than one backend. A shared database does not by itself prove that every route is protected. Rehearse recovery from an incorrect punishment with a test account. If you migrate from another tool, keep a verified copy of the old records and compare several known cases before treating the new history as complete. ### Troubleshooting paths - History is incomplete: compare stored records and identity mapping. - Backend differs: inspect that server's configuration and supported integration. - Appeal lacks evidence: improve the record before drawing a conclusion. \* ## Official documentation and links - [LiteBans documentation](https://gitlab.com/ruany/LiteBans/-/wikis/home) - [Building a Ban Appeal Process That Doesn't Waste Staff Time](https://www.zcraftstudios.com/blog/minecraft-server-ban-appeal-process) ## Verify punishments survive a restart Test with temporary staff permissions, not with an operator account. Create a short test mute, confirm chat is blocked, remove it, and verify the command history and staff audit trail. Restart and confirm the historical record persists. For multi-server networks, verify each intended backend reads from the correct database and that private database credentials never appear in shared screenshots. Use [the punishment plugin comparison](https://www.zcraftstudios.com/blog/litebans-vs-advancedban-vs-essentials-punishments) before migrating from a different system. ## Resources for this topic - [LiteBans Message Templates | Modern Minecraft Punishment Messages](https://www.zcraftstudios.com/products/litebans-message-templates) ## Continue reading - [Building a Ban Appeal Process That Doesn't Waste Staff Time](https://www.zcraftstudios.com/blog/minecraft-server-ban-appeal-process) - [Dealing With Cheaters on a Minecraft Server](https://www.zcraftstudios.com/blog/minecraft-server-cheaters) - [Setting Up AdvancedBan for Punishment Logging](https://www.zcraftstudios.com/blog/advancedban-setup-guide) - [AFK Detection and Auto-Kick Setup for Minecraft](https://www.zcraftstudios.com/blog/minecraft-server-afk-detection-autokick) [ Previous guide BlueMap Setup Guide: Install a 3D Web Map](https://www.zcraftstudios.com/blog/bluemap-web-map-setup)[ Next guide Setting Up DiscordSRV: Bridging Minecraft Chat and Discord](https://www.zcraftstudios.com/blog/discordsrv-chat-bridge-setup)