AdvancedBan
This bukkit page is discontinued!
Visit our SpigotMC page to get the latest version: https://www.spigotmc.org/resources/advancedban.8695/


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.

[NEEDED]
<OPTIONAL>
| = 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
Alias: /tipban
/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
/unwarn [ID]
Delete a warn
/unpunish [ID]
Delete a punishment
/warns <PLAYER>
See your own or a player's warnings.
/check [PLAYER]
Get player-status: UUID/IP/Country/Ban-Status/Mute-Status/Warn-Count
/banlist <PAGE>
See all currently active punishments
/history [PLAYER] <PAGE>
See all currently active punishments
To use the command - ab.history
/advancedban reload
Reloads the messages from file and "some" settings
/advancedban help
Shows a list of all commands and a brief explanation
/systemprefs
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:
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
ab.ipban.perma - /ipban
ab.ipban.temp - /tempipban
ab.ipban.exempt - Immune to ipban
ab.ipban.notify - Receives notification
ab.ipban.exempt - Immune to ipban
ab.ipban.notify - Receives notification
ab.tempipban.exempt - Immune to tempipban
ab.tempipban.notify - Receives notification
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.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.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.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.tempwarn.notify - Receives notification
ab.all.undo - /unpunish
ab.warns.own - /warns
ab.warns.other - /warns
ab.warns.other - /warns
ab.check - /check
ab.check.ip - Also shows IP
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
ab.banlist - /banlist
ab.history - /history
ab.reload - /advancedban reload
ab.help - /advancedban help
ab.systemprefs - /systemprefs
How to limit the punish duration:
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
1: 3600
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.
Note when using Bungeecord:
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)

Some images:
Warn:

Tempmute:

Tempban with Message-Layout:

Ban:

Kick:

Check: [No country because it's a localhost-ip]


Config.yml:
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 UseMySQL: false # Set to false if you want to have only short messages in the console # On startup and on the shutdown. DetailedEnableMessage: true DetailedDisableMessage: true # This will be the default reason to be displayed if none is given DefaultReason: "none" # 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 TimeDiff: 0 # This commands will be disabled for muted players # A player wouldn't be able to bypass with eg "/minecraft:me" MuteCommands: - 'me' - 'say' - 'action' - 'eaction' - 'describe' - 'edescribe' - 'eme' - 'w' - 'm' - 'pm' - 'whisper' - 'ewhisper' - 'emsg' - 'msg' - 'etell' - 'tell' - 'er' - 'r' - 'reply' - 'ereply' - 'ac' - 'eac' - 'amsg' - 'eamsg' - 'ehelpop' # These players will not be able to get punished in any way # this also works if the player is offline ExemptPlayers: - 'Leoko' - 'md5' - 'dutchy1001' - 'ItzSomebody' # The date-format which will be used for the %DATE% variable DateFormat: "dd.MM.yyyy-HH:mm" # 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. EnableAllPermissionNodes: false # 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 UUID-Fetcher: # 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. Dynamic: true Enabled: true Intern: false REST-API: URL: "https://api.mojang.com/users/profiles/minecraft/%NAME%?at=%TIMESTAMP%" Key: "id" BackUp-API: URL: "https://us.mc-api.net/v3/uuid/%NAME%" Key: "uuid" # 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% WarnActions: 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" TempPerms: 1: 600 2: 3600 3: 43200
Messages.yml
Here you can change every message. All Message-Variables that are available are used in the default settings.
Layout.yml
Messages:
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.
Time:
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.
# 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 Message: ExampleLayout: - '%PREFIX% &7Banned for Hacking' - '&c&oBannd by %OPERATOR%' - '&7' - "&cIt seems like you are using a" - "&chacked client please disabled it!" - "&cUnban in &8\xbb &7%DURATION%" - '&7' - '&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" Time: ExampleLayout: - '30m' - '2h' - '1d' - '1w' - '1mo' - '2mo' - '4mo' - 'perma'

- Ban-, Kick-, Mute- and Warn-System
- Excellent performance
- BungeeCord & Bukkit/Spigot-Plugin in one
- PlayerHistory
- Easy to use API
- Advanced-UUID-Support
- 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]
>> Plugins supporting AdvancedBan <<
Addon for Party and Friends System ( [USER=67188]@simonsator[/USER] ):
GUI Addon ( [USER=57888]@Boobah[/USER] ):

English:
(detailed)
(brief)
Dutch/Nederlands:
Russian:
Spanish:
If you have made one just send me the link per PM.

Requirements:
- AdvancedBan version 2.0.0 or higher
- MySQL-Server that is reachable from outside (not just localhost)
- Enabled MySQL not file
A webserver is not required
Note:
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.
Free MySQL-Databases:
BPlaced is not working
Here is a live DEMO:
Features:
- 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






Register here:
Standalone WebInterface Alternative
Thanks to [USER=138878]@mathhulk[/USER] 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 [USER=138878]@mathhulk[/USER] and that we won't provide any support for it.
I don NOT vouch for the security of this web panel!
Example: https://whatisin.space/ab-web-addon

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 <<
BlizzardCraft Network
> mc.blizzardcraft.net

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:

None yet 


All information about the API can be found on GitHub
Thanks!
Nice plugin. How to use temp ban? dont work /tempban LukasGAME122 24hours &4Banned &f- &cKillaura (MultiAura)
First attempt to ban LukasGAME122 failed because you used hours instead of h.
Second attempt failed because LukasGAME122 is a name used for a cracked account.
When using /tempban Stampy_Cat2 24h &4Banned &f- &cKillaura (MultiAura) it works as it should, see below.
I wasn't aware there was a bukkit page for the plugin.
From now on I will give support here as I do on the Spigot and Github site.
The unban doesn't even work. I tried /unwarn but it isn't working.
first do /warns [player] search for the warn ID for example #43 then do /unwarn 43 done ;)
@chsedv
Das geht leider nicht du musst den ganzen AdvacedBan Ordner löschen
@LeokoTime
Super, danke! Habe mir sofort die v2.0.4 geholt aber da fehlen dann meine gebannten Spieler.
Ich hatte alle gebannten Spieler in der Datei "Bans.yml"
Nun bei v2.0.4 sind die nicht mehr enthalten da die Datei nun heisst "data.yml"
Wie kann ich meine alten gebannten Spieler aus der Datei BANS.YML in die DATA.YML importieren?
@chsedv
This version is available on the Spigot-Forums but will be released here too today or tomorrow
Hello. Pls help me. Im using Spigot 1.10.2 last but have error messages in Server Log.
WARNING!!!
You are running an outdated version of AdvancedBan! Newest version:2.0.3 Your version:10.3 This could be a security risk and we highly recommend you to update the plugin!
WARNING!!!
Where i can download this new version?
Update to 1.10
update to bukkit 1.10.x ???
How can i make it for BungeeCord?
I know taht in the config is a line called "BungeeIP" there I have put in my IP (with :[Port]) and it is however still not working?
Thanks for your answer!
[13:08:43 INFO]: PeRFecTxTabZ issued server command: /banlist [13:08:43 WARN]: Exception in thread "pool-3-thread-155" [13:08:43 WARN]: org.apache.commons.lang.UnhandledException: Plugin AdvancedBan v10.3 generated an exception while executing task 8824 at org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NullPointerException at me.leoko.advancedban.handler.CommandHandler.runCommand(CommandHandler.java:347) at me.leoko.advancedban.Main$3.run(Main.java:238) at org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftTask.run(CraftTask.java:53) at org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) ... 3 more
Do you think you can add like a watchlist kind of thing into this as well? Kinda like http://dev.bukkit.org/bukkit-plugins/eyeonyou/ because that would be really cool to have apart of this plugin.
@LeokoTime
Thanks Leoko, thanks to your supposition (UUID-requests) i've solved two of my problems: Citizens use UUID-requests to fetch skins too, so i've near 100 NPC who were fetching skins everytime a player load them. Good way to create a NPC is the -p argument, who save a snapshot of the skin. No more errror on UUID requests with your plugin now !
Thanks a lot, you save my day o/
(Yeah late response, but maybe it can help someone else)
Could you add a temp-ban-ip in the next update? Thanks!
@Lastcube
If you have a big server it could be that you IP-Adrass got banned from the Mojang-Servers due to too many UUID-Requests. I'm currently woking on a new version of AdvancedBan where this will be fixed but this version will take a long time to develop.
More information on: https://www.spigotmc.org/resources/advancedban.8695/ On Spigot there are always more informations about the current development proccess of my plugin
Hi, I realy appreciate this plugin, but i've somes problems with it. My server is a semi-rp server, and we've got a lot of grieffer / trolls who got banned. My problems is that the plugin send me errors for each player's connection, or each ban check. Tellin' that it can't check on mojang the UUID.
Here is a sample of my errors :
28.02 14:00:14 [Server] INFO [AdvancedBan] Failed while getting player's UUID 28.02 14:00:13 [Server] INFO Either the Mojang-Servers ran offline or this player does not exist 28.02 14:00:13 [Server] INFO [AdvancedBan] Failed while getting player's UUID 28.02 14:00:11 [Server] INFO Either the Mojang-Servers ran offline or this player does not exist 28.02 14:00:11 [Server] INFO [AdvancedBan] Failed while getting player's UUID
This error result on the fact somes players aren't ban anymore, and can reconnect by themselves. Can you tell me how can i fix this problems please? c:
PS: I've got a lot a banned player (around 650, on a flat file). Can it be the problem ?
1 requests. Can you make it so you can see who bans the player? I've tried many things that do not work, including the %OPERATOR% part. Here is what it looks like when I do it.