AdvancedBan

ab.kick.use - /kick
ab.kick.exempt - Odporne na wyrzucenie
ab.kick.notify - Otrzymuje powiadomienie

ab.ban.perma - /ban
ab.ban.temp - /tempban
ab.ban.exempt - Odporne na bana
ab.ban.notify - Otrzymuje powiadomienie
ab.ban.undo - /unban

ab.tempban.exempt - Odporne na tempban
ab.tempban.notify - Otrzymuje powiadomienie

ab.ipban.perma - /ipban

# 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 your 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

# 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'

• Wersja AdvancedBan 2.0.0 lub nowsza
• Serwer MySQL dostępny spoza localhost
• Włączony MySQL, a nie plik

• Bezpieczny system logowania (sha1 i brak wstrzykiwania SQL)
• Optymalizowany pod urządzenia mobilne
• Płaski design
• Własna subdomena [NAME.banpanel.eu]
• Własne wiadomości i design [wkrótce]
• Możliwość integracji ze stroną internetową