########################################################################################################################
########################################################################################################################
###############################                                                          ###############################
###############################                   DynamicAuth                            ###############################
###############################               By: Zumorik(DynamicJk)                     ###############################
###############################         Tested by: UraharaNZ, ItsPandemic                ###############################
###############################                                                          ###############################
###############################                                                          ###############################
########################################################################################################################
########################################################################################################################

#MYSQL DATABASE
#host: Ip address of the MySQL Server (We recommend using the numbered ip, if MySQL IS NOT hosted on the same machine)
#Note: If MySQL Is hosted on the same machine keep localhost there.
#username: The username of the MySQL login, often named "root"
#database: The name of the MySQL database which will store all of the plugins data.
#port: The port the MySQL Database runs of on. If you do not know the port keep the port on 3306
host: localhost
username: root
password: w2RQa6
database: authlogin
port: 3306
#=== WE RECOMMEND TO RUN THE MYSQL DATABASE ON THE SAME MACHINE AS THE SERVERS USING THE AUTH PLUGIN
#=== LAG IS POSSIBLE IF YOU RUN MYSQL ON A DIFFRENT SERVER/MACHINE
#=== WE ARE NOT RESPONSIBLE FOR THIS KIND OF LAG
#=== IF YOUR SERVER HAS GOOD UPLOAD AND DOWNLOAD SPEEDS, INCLUDING A FAST HARDDRIVE OR SSD DO NOT WORRY ABOUT THE ABOVE

#Change the UUID of premium players
#true = offline uuid
#false = online uuid
#This will change premium player UUIDs to offline player UUIDS (cracked uuids)
Do-not-Use-PremiumUuid: false

minimum-password-length: 6

#The player will require to verify their email in order to login
#This requires a SMTP server, and the email.yml file must be configured.
requireVerifiedEmail: false
#If you do not want the player to require a verified email, but want it to be optional enable that option within the email.yml
#Please note that all SMTP servers are not supported (Works best with amazon smpt servers)

#Premium players do not require to register or login
#CHANGING THIS FEATURE TO FALSE OR TRUE REQUIRES A BUNGEECORD RESTART
#If you are using Auth lobby balancers, Make sure you set LobbyServer as one of your Auth Lobbies.
PremiumBypass: true

#Disables the check that insures a player has not logged in with a premium player name
#For example if disabled a cracked/offline player cannot connect with the name ItsPandemic, since it is premium.
#If this is enabled enabled a cracked/offline player can login with the premiumPlayer name ItsPandemic
#WARNING: Disable PremiumBypass so players cannot automatically login with premium player names.
#We do not give support for not using PremiumBypass, use this at your own risk. (We have not tested this well)
#READ THE WARNING ABOVE BEFORE ATTEMPTING TO REPORT ANY ISSUE THIS THIS FEATURE
modifyPremiumNameCheck: false

#If enabled this will disable the legacy check that checks if a fake player has already used the name of the premium player
#This feature blocks premium players from stealing fake player accounts for instance:
#A cracked player with the name Jerry logs in and registers their account however, later someone buys a premium player account with
#the name Jerry and they attemp to login to your server, they will not automatically login instead they will be asked for the cracked players password
#This feature keeps premium players from stealing cracked player accounts.
IgnoreLegacyCheck: false

#THIS IS BASICALLY THE NAME OF YOUR DEFAULT AUTH LOBBY, IF YOU ARE NOT USING AN AUTH LOBBY SET THIS AS YOUR DEFAULT LOBBY SERVER.
#READ THE COMMENTS BELOW OR YOU COULD CAUSE WEIRD GLITCHES
LobbyServer: auth
#If you are using auth lobby balancers set this as your first auth lobby
#This is the lobby the player will be sent back to if they attempt to switch servers without logging in or registering
#If the server does not exist the player will be able to switch servers without registering (please setup correctly).

#The time the player has to register before being kicked (Seconds)
registerTime: 120

#The time the player has to login before being kicked (Seconds)
loginTime: 120

#Sends the player to the server they last were on when they login.
#Players that require to login will be sent to the lobby or auth lobby, then the server they were last on.
#This feature gets disabled if using the following features: (Lobby Balancer, Always Lobby)
returnServer: true
#This will enable the return to last login server even if the lobby balancer is enabled
#Requires returnServer to the true.
force_enable_with_lobby_balancer: false

#Session time out, how long a player has to be offline before they have to run /login again (minutes)
session: -1

#The type of encryption used to store passwords
#Currently only supporting the following types:
#default - Hash and Salt
#SHA512 - Our custom SHA512
#SHA-512 - Default Sha-512 (difference is the dash)
encryptionType: 'default'

#Maxs accounts connected at the same time with the same IP
#This can help stop spam bots with the same IP address
maxIP: 1500

#IMPORTANT -READ NO MATTER WHAT
#We recommend to use this feature even if you only have 1 lobby and 1 auth lobby

#This feature allows you balance the amount of players within your login/auth servers
#This feature will override the returnServer feature, unless forcibly enabled.
useLoginServerBalancer: false
#This feature redirects players from the login servers, to a lobby with a balanced player amount
#This feature CAN override the returnServer feature, unless forcibly enabled.
#LobbyServer Balancer can work with or without the auth server balancer, but is recommended to use both at the same time.
useLobbyServerBalancer: false
LoginBalance:
   LoginServers:
     - authlobby01
LobbyBalance:
   LobbyServers:
     - lobby01

#Any time a player connects they will be sent to lobby server
#If balancer is enabled, player will be sent to one of the Lobby servers with your lobby balancer, (useLobbyServerBalancer enabled)
#If balancer is not enabled they will be sent to the LobbyServer
#Over rides return Server, unless forcibly enabled.
#TO SET THIS UP EFFICIENTLY, SET YOUR DEFAULT SERVER AS YOUR PRIMARY LOBBY SERVER
#ALSO MAKE THE LOBBY YOUR MAIN PRIORITY SERVER WITHIN THE BUNGEECORD CONFIG
alwaysLobby: true

#The name of the language file being used.
#defaults: en and es (en - English, es - Spanish)
messages:
  language: en
#You can create your own language file and name with whatever, just add the name to this section of the config and your good to go!

#If the players IP does not match the IP within the database, they will require to relogin.
bindCheck: true
#WARNING YOU MUST SET THE FOLLOWING SETTINGS WITH IN YOUR BUNGEECORD TO SETUP BindCheck CORRECTLY.
#1 First go within bungeecord and set ip_forward: false to ip_forward: true
#2 Go inside all Servers and within the spigot.yml set bungeecord: true
#3 Save and restart all servers.
#4 YOU CAN DO THIS EVEN IF YOU ARE RUNNING AN OFFLINE SERVER "Cracked Server."

#ENABLE IF YOU ARE USING BOTH BUNGEECORD AND SPIGOT/BUKKIT PLUGINS.
#IF YOU ARE ONLY USING BUNGEECORD SET TO FALSE.
#IF YOU KEEP THIS ENABLED, AND YOU ARE NOT USING IT "UNKNOWN COMMAND ERROR," WILL APPEAR.
serverSide: true

#Send to lobby server delay
#This only works if you are using the Lobby & Login Balancers
#Feature requested to help handle Async logins
#This feature is recommended to use, as it insure a stable login
delaylogin: false

#System to enable or disable wether to send premium players to their own lobby
#and send fake players to a fake player lobby.
#Also enable delayLogin in order to override return to auth lobby check
#If you would like to use multi-lobby and multi login remove set Premium-lobby and fake-lobby to just ''
premium-lobby:
  enabled: true
  premium-lobby: 'survival'
  fake-lobby: 'auth'
  premium-lobby-multi:
   - 'survival'
  fake-lobby-multi:
   - 'auth'

#This feature allows certain players to connect with specific names however, require their ip to match
#a set ip within the ipmanager.yml
#Example: only the IP 127.0.0.1 can use the account "Zumorik". that way only users with my IP can use my account: hackers cannot connect to a staff account without a matching IP!
ipmanager:
  enabled: false

#Setup a system where only x amount of accounts can be created on an IP
#For example, the max Ip is set to 1, and Zumorik created the account with the IP 127.0.0.2
#Now 127.0.0.2 has been assigned to Zumorik's account, and that ip can only be used once
#IF Zumorik was banned and he tried to make another account, when he tries to do /register <password> <password>
#He will be denied registration and kicked if option is enabled.
ip-registration:
   enabled: false
   maxIP: 3
   kick: false

#Enabled /hub command
#If Premium player and fake player servers are enabled, the player will be sent to a lobby corresponding to your premium-lobby system
#Ex: Premium player will be sent to premium lobby, Non premium player will be sent to non premium lobby
#If lobby balancer is enabled, the player will be sent to a lobby corresponding to your LobbyBalance System (Least active lobby or only lobby)
#If none of the above is enabled the player will be sent to the LobbyServer as defined above.
#If you enable or disable this command, the server will require a RESTART
HubCommand:
  enabled: false

#If a server goes down this feature will redirect the player to your defined lobby system
#Supported lobby systems
# - Premium player lobbies / cracked player lobbies
# - Login/Lobby server balancers
# - Normal LobbyServer system
returnLobby:
  enabled: false
  reasons:
    - Server Closed
#This feature helps prevent mass bot attacks by blocking cracked logins if the current amount of
#logins exceds the maximum amount of cracked logins per minute.
#Note: since we cannot change client messages the message will display as Failed Session login when enabled
MaxLoginRate:
  enabled: true
  maximum: 300
  minutes: 1
  motd:
    enabled: false
    message: '&cServer currently experiencing mass login rates, please wait 1 minute'