- Tested Minecraft Versions:
- Source Code:
AdvancedBan is an All-In-One Punishment-System with warns, tempwarns, mutes, tempmutes, bans, tempbans, ipbans, tempipbans and kicks.
There is also a PlayerHistory so you can see the players past punishments and
the plugin has configurable Time & Message-Layouts which automatically calculate and increase the Punishment-Time for certain reasons.
AdvancedBan provides also a full Message-File so you can change and translate all messages & a detailed config file with a lot of useful settings.
This is a BungeeCord & Bukkit/Spigot-Plugin in one and it supports MySQL and a local embedded Database to provide high performance.
Developed by Leoko
1. Download the Plugin
2. Put it in your Plugin folder. [either in the one of your BungeeCord-Server or in the one of the Bukkit/Spigot]
3. Reload/Restart your Server [if BungeeCord you have to restart it with /end]
4. Check with /advancedban if the plugin is loaded.
5. Configure it like you want & have fun.
| = or
-s = Silent punishemnt (no notification to others)
/kick [PLAYER] <-s> <REASON | @LAYOUT>
Kick a player
/ban /mute /warn [PLAYER] <-s> <REASON | @LAYOUT>
Ban/Mute/Warn a player
/banip [PLAYER/IP] <-s> <REASON | @LAYOUT>
Ban a player's IP. If you enter a name it will use the cached IP
/tempban /tempmute /tempwarn [PLAYER] [Xmo|Xd|Xh|Xm|Xs|#TIMELAYOUT] <-s> <REASON | @LAYOUT>
Tempban/mute/warn a player for a given time or with a time-layout for automatic-time-calcualtion
/tempipban [PLAYER/IP] [Xmo|Xd|Xh|Xm|Xs|#TIMELAYOUT] <-s> <REASON | @LAYOUT>
Temippban a player for a given time or with a time-layout for automatic-time-calcualtion
/change-reason [ID] [New reason]
Change the reason for a punishment by id
/change-reason [ban/mute] [PLAYER] [New reason]
Change the reason for a players punishment
/unban /unmute [PLAYER]
Unban/mute a player
Delete a warn
Delete a punishment
See your own or a player's warnings.
Get player-status: UUID/IP/Country/Ban-Status/Mute-Status/Warn-Count
See all currently active punishments
/history [PLAYER] <PAGE>
See all currently active punishments
To use the command - ab.history
Reloads the messages from file and "some" settings
Shows a list of all commands and a brief explanation
Displays some System-Information which are useful for the configuration
Most of the permission nodes follow a simple layout:
ab.PUNISHMENT.TYPE or ab.COMMAND
So, for example, the /ban command has the permission node ab.ban.perma and the tempwarn command has ab.warn.temp
But please check the list of permissions anyway to ensure you are using the right permissions:
Code (Text):ab.kick.use - /kick
ab.kick.exempt - Immune to kicking
ab.kick.notify - Receives notification
ab.ban.perma - /ban
ab.ban.temp - /tempban
ab.ban.exempt - Immune to ban
ab.ban.notify - Receives notification
ab.ban.undo - /unban
ab.tempban.exempt - Immune to tempban
ab.tempban.notify - Receives notification[/SPOILER]
ab.ipban.perma - /ipban
ab.ipban.temp - /tempipban
ab.ipban.exempt - Immune to ipban
ab.ipban.notify - Receives notification
ab.tempipban.exempt - Immune to tempipban
ab.tempipban.notify - Receives notification
ab.mute.perma - /mute
ab.mute.temp - /tempmute
ab.mute.exempt - Immune to mute
ab.mute.notify - Receives notification
ab.mute.undo - /unmute
ab.tempmute.exempt - Immune to tempmute
ab.tempmute.notify - Receives notification
ab.warn.perma - /warn
ab.warn.temp - /tempwarn
ab.warn.exempt - Immune to warn
ab.warn.notify - Receives notification
ab.warn.undo - /unwarn
ab.tempwarn.exempt - Immune to tempwarn
ab.tempwarn.notify - Receives notification
ab.all.undo - /unpunish
ab.warns.own - /warns
ab.warns.other - /warns
ab.check - /check
ab.check.ip - Also shows IP
ab.changeReason - /change-reason
ab.banlist - /banlist
ab.history - /history
ab.reload - /advancedban reload
ab.help - /advancedban help
ab.systemprefs - /systemprefs
By default, the user will be able to punish an infinite amount of time if he has the perms to use the command.
You can set the max-punishment-time with ab.tempban/tempmute/tempwarn.dur.X
In the config, there is a section called "TempPerms".
There you can configure how long which ID will be able to punish
for example, you set
the player with the perms ab.tempban.dur.1 will only be able to ban 3600s -> 1h
The amount is entered in SEC and if a player has more than one perms the higher numbers override.
There is a second explanation in the config.yml.
If you use this plugin on bungeecord you need to define the permissions in the config.yml of the Bungeecord Server or through a spcial bBungeecord Permission Plugin.
The problem with bungeecord permissions is that there are not *-Perms so a user with ab.* won't have access to all commands. But to simplify the setup there is a setting in the advacnedban config called "EnableAllPermissionNodes" which allows you to use a .all instead of a .* so if enabled a user with ab.all will have access to all AdvancedBan commands. (There is another explanation in the config)
Tempban with Message-Layout:
Check: [No country because it's a localhost-ip]
The config.yml should be self-explaining and there are also explanations in the config.yml
# AdvancedBan v2 - Coded by Leoko
# For each setting, there is a small description.
# Please read each description carefully before changing anything.
# For more information visit: https://www.spigotmc.org/resources/advancedban.8695/
# Do you want your own Plugin or Website? Check out our Dev-Page: http://dev.skamps.eu
# If set to false all bans will be saved locally in a HSQLDB-Database
# Set to false if you want to have only short messages in the console
# On startup and on the shutdown.
# This will be the default reason to be displayed if none is given
# Change this if your server has a different time that your users.
# e.g.: ServerTime: 16:43 | Your Time: 13:43 | TimeDiff has to be set to -3
# You can check the server time with /systemPrefs
# This commands will be disabled for muted players
# A player wouldn't be able to bypass with eg "/minecraft:me"
# These players will not be able to get punished in any way
# this also works if the player is offline
# The date-format which will be used for the %DATE% variable
# This is useful for bungeecord servers or server with permission systems which do not support *-Perms
# So if you enable this you can use ab.all instead of ab.* or ab.ban.all instead of ab.ban.*
# This does not work with negative permissions! e.g. -ab.all would not block all commands for that user.
# If you use external REST-APIs they will have to respond in JSON
# The given APIs will only be used for NAME -> UUID
# For UUID -> NAME will either use the official MojangAPI or the InternFetcher
# To check if you can use the intern fetcher do /systemPerfs and compare your uuid
# to the one you can see online on http://NamesMC.com
# if they are similar we recommend using the InternFetcher
# If dynamic it set to true it will override the 'enabled' and 'intern' settings
# and automatically detect the best possible uuid fetcher settings for your server.
# Our recommendation: don't set dynamic to false if you don't have any problems.
# These are the commands that will be performed on warns
# If you skip a number the command from before will be performed
# You can also use non-AdvancedBan-Commands like 'broadcast' or 'clear %PLAYER%
# Variables: %PLAYER%, %REASON%, %COUNT%
3: "kick %PLAYER% &c&oYou have received your 3rd warning!"
4: "tempban %PLAYER% 30m &c&oYou have received your 4th warning!"
5: "tempban %PLAYER% 5h &c&oYou have received your 5th warning!"
6: "tempban %PLAYER% 7d &c&oYou have received your 6th warning!"
7: "tempban %PLAYER% 1mo &c&oYou have received your %COUNT%th warning!"
10: "ban %PLAYER% &c&oYou have received your 10th warning!"
# Here you can create permission-nodes for max-punishment-duration.
# The permission "ab.tempban.dur.1" would allow the player to ban max. for 600sec = 10min
# The permission "ab.tempwarn.dur.2" would allow the player to warn max. for 3600sec = 1h
# You can only create up to 10 perms. The perms can be overridden with "ab.COMMAND.dur.max"
Here you can change every message. All Message-Variables that are available are used in the default settings.
Here you can define predefined reasons which can be used for (temp-)banning/muting/warning & kicking.
You can use them by just typing @Layout-NAME instead of the reason. So you can have different layouts with different information for different reasons.
And once you have defined them you do not have to type the whole reason.
Here you can define timelayouts which can be used for temporary-punishments.
You can use them by just typing #LAYOUT-NAME instead of the duration. The time increases every time a player gets punished with the same layout.
Code (Text):# The default layouts are in the Message.yml file!
# Message-Layouts can not only be used for bans but also for mutes and warns
# Varibales: %OPERATOR%, %REASON%, %PREFIX%, %DURATION%
# For warns you have also the variable %COUNT% which will be
# replaced with the current amount of warns the player already resived
# Example usage: /ban Leoko @ExampleLayout
- '%PREFIX% &7Banned for Hacking'
- '&c&oBannd by %OPERATOR%'
- "&cIt seems like you are using a"
- "&chacked client please disabled it!"
- "&cUnban in &8\xbb &7%DURATION%"
- '&8Unban application in TS or forum'
- "&eTS-Ip &8\xbb &c&ncoming soon"
- "&eForum &8\xbb &c&ncoming soon"
# You would use this time-layout for example like this: "/tempban Leoko #ExampleLayout Hacking in FFA"
# Or with "/tempwarn Leoko #ExampleLayout Advertising" or with "/tempwarn Leoko #ExampleLayout No capslock please"
# You can also combine this with MessageLayouts like "/tempban Leoko #ExampleLayout @Hacking"
>> Plugins supporting AdvancedBan <<
- Ban-, Kick-, Mute- and Warn-System
- Excellent performance
- BungeeCord & Bukkit/Spigot-Plugin in one
- Easy to use API
- Intern or Extern UUID-Fetcher
- Backup-UUID-Fetcher if Mojang-Servers are offline
- Change UUID-Fetcher REST-API
- MySQL or local embedded HyperSQL
- Full customizable
- Multiple lines in Kick- and Ban-Messages
- Pre-Defined Reasons
- Automatic time calculation [1th-tempban -> 1h | 2th-tempban -> 6h ...]
- Custome Time-Offset [Change the timezone if the server has a wrong time]
- Automatic-Warn actions
- Check-Command [UUID, IP, COUNTRY, BAN/MUTE/WARNS]
Punishment GUI ( @BGHDDevelopment ):
Addon for Party and Friends System ( @simonsator ):
GUI Addon ( @Boobah ):
Use numbers instead of reasons, durations and punishment types ( @Phyrone ):
If you have made one just send me the link per PM.
A webserver is not required
- AdvancedBan version 2.0.0 or higher
- MySQL-Server that is reachable from outside (not just localhost)
- Enabled MySQL not file
The webpanel is not something to download like the first one.
It's a website where you can register your server and the website will generate your own banpanel.
Also the panel does only display things it is not for administration just for monitoring.
BPlaced is not working
Here is a live DEMO:
- Secure login-system (sha1 & no-SQLInjections)
- Mobile optimized
- Flat design
- Own subdomain [NAME.banpanel.eu]
- Own messages & design [coming soon]
- Able to integrate into your webside
Thanks to @mathhulk there is a web interface which you can download and place on your own WebServer this can be great if...
... your MySQL is only accessible for localhost
... you want to make major changes in the layout
This web interface does not include all features listed above, like the player-search or advanced mobile optimization.
Finally please note that all credits of this web interface got to @mathhulk and that we won't provide any support for it.
I don NOT vouch for the security of this web panel!
If you have any problems with the Plugin make sure the first check the console for any error messages with instructions how to solve the issue and to read the Known-Issues-Section below
If you still have the issue just post your it into the discussion area, on GitHub or on our Discord-Server
The new Version of AdvancedBan was a lot of work for and I spend a lot of time and effort on it.
So if you appreciate my work I'd be very thankful about every donation ^^
>> Servers using AdvancedBan <<
We use a Metrics-System called bStats which tracks information about your server
eg. Player, Bit-System, MC-Version, Server-System ect.
More information about bStats can be found here:
All information about the API can be found on GitHub
AdvancedBan is a ban plugin for singel servers and server networks with a great looking ban message
Also, for those who are giving bad reviews, I don't know what you're talking about, be nice to this guy he works hard. Most of these reviews it seems like it's an issue from your side, not his, so just stop and ask him on discord. This guy deserves respect and he's a really nice developer
I have been using AdvancedBan for the past year now. This has majorly improved my server and how I can provide to my player base. I also run the Unofficial web addon by hulkmath @ https://staff.tml.life/banpanel
This web addon looks absolutely wonderful with an amazing developer for it as well. (I also suggest using this if you can host it)
My favorite features go along with Arrowheads844
• Free! (LiteBans is NOT worth its price.)
• BungeeCord Support
• Custom Kick/Warning/Mute/Ban messages.
• Highly customizable messages. I can literally change every aspect of the messages with ease to support the look and feel of my server. (I hate the messages in LiteBans)
• Completely bug-free (Unless I didn't notice it)
• UUID support - This helps when a player changes their name once, twice, or even three times.
• The little features. When I do /history <player> it shows the punishment they received under their OLD username. Good feature!
• Instant punishments - No waiting
• Configurable max durations for each command! I love this feature a lot. I give my Helpers temp ban for only a little bit in case of emergencies but give my moderators like 2-week bans. This makes it easier for me to give ALL my staff the majority of punishment commands but just restrict it to how long they can actually punish someone for. LiteBans doesn't have this.
• Impossible to bypass - No scrummy players trying to get around the system to get back on and ruin the server for others.
A few things I must say though. The country variable thing in /check is broken (was working a month or two ago)
You should make the exempt-players in the config.yml UUID based. I exempted my username and I had a player BungeeCord my BungeeCord and they came on with a cracked account under my username and they destroyed my Hub! My staff couldn't ban him because he came on under my exempted name.
Now I just have ab.all in BungeePerms which exempts me but I think you should make the exempt players in the config UUID based so this doesn't happen again.
Also, for any players who encounter the same thing - BungeeCording your BungeeCord. Use the plugin IP-Whitelist and install it on ALL of your SPIGOT servers.
In conclusion, I think this plugin is absolutely wonderful and I wouldn't want to go to any other plugin (LiteBans is not worth its price in my opinion)
Great plugin! But is it possible that one permission group can just ban some and not all groups? Like this: supporters can only ban players, moderators can ban builders and players, devs can ban supporters, builders and players, admins can ban moderators, supporters, builders and players and owners can ban everyone?
Does that already exist? If not, will this come one day?