LibertyBans Plugin FAQ

LibertyBans requires a SQL database (MySQL, MariaDB, or compatible). Configure your database connection details in the plugin's config file with your host, port, username, password, and database name, then restart the server to initialize tables automatically.

/ban punishes a specific player UUID, while /ipban blocks an entire IP address and prevents any account from that IP from joining. IP bans are stronger for stopping alt accounts but affect all players on that connection.

LibertyBans tracks player UUIDs and IP addresses; when you IP ban someone, it automatically blocks alternate accounts from the same IP. When a banned player's alt tries to join, the plugin detects the shared IP and denies access.

Yes, use /mute to silence a player while keeping them in-game, or /ipmute to mute all accounts from an IP. Muted players cannot send chat messages but can still play normally.

Configure all servers to connect to the same SQL database in their LibertyBans config files. Bans, mutes, and warnings applied on one server instantly sync to all others using that database.

A regular /ban only blocks that player's UUID, so they can rejoin using an alternate account from the same IP. Use /ipban instead if you want to prevent alts, or enable IP-based alt detection in your punishment.

Yes, LibertyBans maintains a full audit trail of every ban, mute, warning, and kick with timestamps and moderator names. Check player history through the plugin's lookup commands or database queries.

Use /unban to remove a UUID ban or /unbanip to remove an IP ban. The player can rejoin immediately after the punishment is lifted.

LibertyBans uses standard permission nodes for commands and operates independently of permission plugins, but it integrates cleanly with systems like LuckPerms. Check the documentation for specific permission node names to assign moderator roles.

LibertyBans is optimized for performance and uses efficient database queries with caching, so it has minimal impact even on large networks. Most overhead comes from your SQL database connection, not the plugin itself.