Minecraft 1.14 కోసం 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

• Download the Plugin

• Put it in your Plugin folder. [either in the one of your BungeeCord-Server or in the one of the Bukkit/Spigot]

• Reload/Restart your Server [if BungeeCord you have to restart it with /end]

• Check with /advancedban if the plugin is loaded.

• 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.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

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.