LibertyBans

LibertyBans handles punishments: banning, muting, warning, and kicking from the server. But it isn't just a set of commands — it keeps a record of every punishment, so you can come back to it at any time.

That's its main advantage. For each player, you can see why they were punished, who issued the punishment, when it expires, and whether it was revoked. When a player returns and breaks the rules again, you don't have to guess — you see the full history.

The plugin also supports escalation: you set that the first offense gets a warning, the second a short ban, and the third a longer one. The server then punishes predictably, and management doesn't have to handle every case individually.

It can work with multiple servers at once — if you have a proxy with several worlds, a punishment issued on one applies everywhere. Punishment data can be stored in a database, which is a better choice for a larger server or server network than files.

The other side matters too: a player can appeal, and you decide based on the record, not on impressions. If a punishment is unfair, you revoke it with a single command, and the history will show that it was revoked.

Warning: punishment commands are easy to mix up (and one ban issued by mistake can mean a player can't get into the server). Give punishment permissions only to people who are supposed to use them — and set who may revoke bans.

1. Decide how punishments will be stored: files (simple) or database (for multiple servers or a network).
2. Download LibertyBans from modrinth.com/plugin/libertybans (or from the author's official page) for your server type.
3. Upload the .jar to the plugins folder. For a proxy, it belongs on the proxy, so punishments apply across all servers.
4. Restart the server and open the configuration — set storage (files or database).
5. If you use a database, verify that the plugin connected (message in the console), and set up backups.
6. Go through the punishment escalation settings: what happens for the first, second, and third offense.
7. Assign permissions: a regular player has no punishment permissions, management can warn and mute, top management can also ban.
8. Check who can revoke punishments — and whether it should be reported to others (so a ban is not revoked silently).
9. Test it on a trial basis: give your own test account a warning and see how it was recorded in the history.
10. Save your appeal procedure (where the player writes) — you will need it at the first dispute.

Store punishments in a database if you have multiple servers or a proxy. A punishment issued in one place then applies everywhere, and history won't diverge.
Set up punishment escalation (escalation) before you need it. A server that punishes predictably doesn't have to handle every case manually.
Give punishment permissions only to those who are supposed to use them. An accidentally issued ban is the most common mistake on servers with multiple admins.
Set who may revoke punishments, and whether revocations are announced to others. A silently revoked ban looks like weakness of the leadership.
History is the best argument in a dispute and in an appeal. Learn to look at it before deciding — it saves arguments.
Server rules must match punishments. If players don't know what they risk for what, every punishment looks arbitrary.
Back up punishment data. Without it, history will be lost during restoration — and that is exactly what should remain.