LibertyBans

LibertyBans is the sparkling and extraordinary weapon of punishment administration.

:https://img.shields.io/badge/-Home_Page-blueviolet.svg?logo=StarTrek&style=for-the-badge&logoColor=white :https://img.shields.io/badge/-Documentation-blue.svg?logo=Wikipedia&style=for-the-badge&logoColor=black :https://img.shields.io/badge/-Discord-5865F2.svg?logo=discord&style=for-the-badge&logoColor=white :https://www.gnu.org/graphics/agplv3-155x51.png

!(https://raw.githubusercontent.com/A248/LibertyBans/fb285f13b89285c985ac11dae9d440a3f1a1e953/.github/banner.png) [!](https://libertybans.org)

[!](https://discord.gg/3C4qeG8XhE) [!](https://docs.libertybans.org/#/Getting-Started)

[!](https://github.com/A248/LibertyBans)

Why?

The existing punishment plugins all have their flaws. Either they are plagued with bugs and concurrency issues, or they are closed-source and pay-walled, or both.

None of the existing punishment plugins have a test framework which can compare to LibertyBans' extensive automated testing. This means that many bugs are caught automatically and never make it into stable releases.

LibertyBans features a full-suite of punishment-related tools. It is a general-purpose punishment plugin with a focus on effective design, quality of experience, and unbeatable code quality. It can efficiently scale to large networks and operate on single servers with minimal resources, while still offering a rich, modular feature set.

Features Add and remove punishments: /ban, /ipban, /unban, /unbanip - bans or unbans a player or IP address /mute, /ipmute, /unmute, /unmuteip - mutes or unmutes a player or IP address /warn, /ipwarn, /unwarn, /unwarnip - warns or unwarns a player or IP address /kick, /ipkick - kicks a player or IP address Temporary versions of bans, mutes, and warns All player data is stored using UUIDs. List punishments: /banlist - shows all bans /mutelist - shows all mutes /history - shows all punishments for a player /warns - shows all warns for a player /blame - shows all the punishments a staff member has enacted Multiple means to block alt accounts: Automatic enforcement to block alt accounts. By default, when using IP-bans, alts are automatically banned from joining if the main account is banned. This behavior is configurable, and you can even increase the strictness of alt-checking. Manual /alts command - shows suspected alt accounts for a player. Alts notification on join - tells staff members when a player whose suspected alt is banned or muted. Exemption. For example, trainees cannot ban admins; admins cannot ban owners. Layouts & punishment templates. For example, the first mute for swearing lasts 10 days, the next is for 30 days, and the third mute is permanent. Supports calculating the reason, time, and even punishment type. Options and behavior are fully configurable. You can even tweak your connection pool and statement cache settings to fine-tune performance. The plugin is carefully designed to be performant and lightweight. It uses an efficient SQL schema which stores the raw bytes of UUIDs and IP addresses, rather than storing them as strings/text. Full multi-proxy and multi-instance support. You can place LibertyBans on the proxy if you use a single proxy, or on multiple backend servers.

# Commands, Permissions, Configuration​

Everything is explained on the wiki:

• (https://docs.libertybans.org/)**

The wiki has a lot of information, including about the configuration.

The configuration files are extensively commented and the options are explained in detail. If you update LibertyBans, your old configuration will be updated automatically if there are new options.

Commands

Run: /libertybans usage to show all commands. When typing this into your console, leave off the slash.

When creating temporary punishments, the same command is used for permanent punishments. Simply add the time after the username: /ban Player1 30d This is a temporary ban

For an extended guide, see (https://docs.libertybans.org/#/Getting-Started).

Design Effective and lightweight. No complicated installation and avoids unnecessary features. Option to use local file-based database (HyperSQL), or remote database (MariaDB, MySQL, PostgreSQL). Highly scalable, database-oriented performance emphasising calculations in SQL. Low memory usage because punishments are stored almost completely in the database. Best practices for connection pooling and asynchronous calculations are followed. * Well-structured API providing a framework for other plugins to work with. An external (https://github.com/Dimitri-Bit/Liberty-Bans-Web) is maintained by Dmitri and it uses the API.