SHARE
TWEET

Untitled

a guest Dec 31st, 2018 64 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. # FastLogin config
  2. # Project site: https://www.spigotmc.org/resources/fastlogin.14153
  3. # Source code: https://github.com/games647/FastLogin
  4. #
  5. # You can access the newest config here:
  6. # https://github.com/games647/FastLogin/blob/master/core/src/main/resources/config.yml
  7.  
  8. # Request a premium login without forcing the player to type a command
  9. #
  10. # If you activate autoRegister, this plugin will check/do these points on login:
  11. # 1. An existing cracked account shouldn't exist
  12. # -> paid accounts cannot steal the existing account of cracked players
  13. # - (Already registered players could still use the /premium command to activate premium checks)
  14. # 2. Automatically registers an account with a strong random generated password
  15. # -> cracked player cannot register an account for the premium player and so cannot the steal the account
  16. #
  17. # Furthermore the premium player check have to be made based on the player name
  18. # This means if a cracked player connects to the server and we request a paid account login from this player
  19. # the player just disconnect and sees the message: 'bad login' or 'invalid session'
  20. # There is no way to change this message
  21. # For more information: https://github.com/games647/FastLogin#why-do-players-have-to-invoke-a-command
  22. autoRegister: true
  23.  
  24. # This is extra configuration option to the feature above. If we request a premium authentication from a player who
  25. # isn't actual premium but used a premium username, the player will disconnect with the reason "invalid session" or
  26. # "bad login".
  27. #
  28. # If you activate this, we are remembering this player and do not force another premium authentication if the player
  29. # tries to join again, so the player could join as cracked player.
  30. secondAttemptCracked: true
  31.  
  32. # New cracked players will be kicked from server. Good if you want switch from offline-mode to online-mode without
  33. # losing players!
  34. #
  35. # Existing cracked and premium players could still join your server. Moreover you could add playernames to a whitelist.
  36. # So that these cracked players could join too although they are new players.
  37. switchMode: false
  38.  
  39. # If this plugin detected that a player has a premium, it can also set the associated
  40. # uuid from that account. So if the player changes the username, they will still have
  41. # the same player data (inventory, permissions, ...)
  42. #
  43. # Warning: This also means that the UUID will be different if the player is connecting
  44. # through a offline mode connection. This **could** cause plugin compatibility issues.
  45. #
  46. # This is a example and doesn't apply for every plugin.
  47. # Example: If you want to ban players who aren't online at the moment, the ban plugin will look
  48. # after a offline uuid associated to the player, because the server is in offline mode. Then the premium
  49. # players could still join the server, because they have different UUID.
  50. #
  51. # Moreover you may want to convert the offline UUID to a premium UUID. This will ensure that the player
  52. # will have the same inventory, permissions, ... if they switched to premium authentication from offline/cracked
  53. # authentication.
  54. #
  55. # This feature requires Cauldron, Spigot or a fork of Spigot (Paper)
  56. premiumUuid: true
  57.  
  58. # This will make an additional check (only for player names which are not in the database) against the mojang servers
  59. # in order to get the premium UUID. If that premium UUID is in the database, we can assume on successful login that the
  60. # player changed it's  username and we just update the name in the database.
  61. # Examples:
  62. # #### Case 1
  63. # nameChangeCheck = false ----- autoRegister = false
  64. #
  65. # Player logins as cracked until the player invoked the command /premium. Then we could override the existing database
  66. # record.
  67. #
  68. # #### Case 2
  69. #
  70. # nameChangeCheck = true ----- autoRegister = false
  71. #
  72. # Connect the Mojang API and check what UUID the player has (UUID exists => Paid Minecraft account). If that UUID is in
  73. # the database it's an **existing player** and FastLogin can **assume** the player is premium and changed the username.
  74. # If it's not in the database, it's a new player and **could be a cracked player**. So we just use a offline mode
  75. # authentication for this player.
  76. #
  77. # **Limitation**: Cracked players who uses the new username of a paid account cannot join the server if the database
  78. # contains the old name. (Example: The owner of the paid account no longer plays on the server, but changed the username
  79. # in the meanwhile).
  80. #
  81. # #### Case 3
  82. #
  83. # nameChangeCheck = false ----- autoRegister = true
  84. #
  85. # We will always request a premium authentication if the username is unknown to us, but is in use by a paid minecraft
  86. # account. This means it's kind of a more aggressive check like nameChangeCheck = true and autoRegister = false, because
  87. # it request a premium authentication which are completely new to us, that even the premium UUID is not in our database.
  88. #
  89. # **Limitation**: see below
  90. #
  91. # #### Case 4
  92. #
  93. # nameChangeCheck = true ----- autoRegister = true
  94. #
  95. # Based on autoRegister it checks if the player name is premium and login using a premium authentication. After that
  96. # fastlogin receives the premium UUID and can update the database record.
  97. #
  98. # **Limitation from autoRegister**: New offline players who uses the username of an existing minecraft cannot join the
  99. # server.
  100. nameChangeCheck: true
  101.  
  102. # If your players have a premium account and a skin associated to their account, this plugin
  103. # can download the data and set it to the online player.
  104. #
  105. # Keep in mind that this will only works if the player:
  106. # * is the owner of the premium account
  107. # * the server connection is established through a premium connection (paid account authentication)
  108. # * has a skin
  109. #
  110. # This means this plugin doesn't need to create a new connection to the Mojang servers, because
  111. # the skin data is included in the Auth-Verification-Response sent by Mojang. If you want to use for other
  112. # players like cracked player, you have to use other plugins.
  113. #
  114. # If you want to use skins for your cracked player, you need an additional plugin like
  115. # ChangeSkin, SkinRestorer, ...
  116. forwardSkin: false
  117.  
  118. # Displays a warning message that this message SHOULD only be invoked by
  119. # users who actually are the owner of this account. So not by cracked players
  120. #
  121. # If they still want to invoke the command, they have to invoke /premium again
  122. premium-warning: false
  123.  
  124. # If you have autoRegister or nameChangeCheck enabled, you could be rate-limited by Mojang.
  125. # The requests of the both options will be only made by FastLogin if the username is unknown to the server
  126. # You are allowed to make 600 requests per 10-minutes (60 per minute)
  127. # If you own a big server this value could be too low
  128. # Once the limit is reached, new players are always logged in as cracked until the rate-limit is expired.
  129. # (to the next ten minutes)
  130. #
  131. # The limit is IP-wide. If you have multiple IPv4-addresses you specify them here. FastLogin will then use it in rotating
  132. # order --> 5 different IP-addresses 5 * 600 per 10 minutes
  133. # If this list is empty only the default one will be used
  134. #
  135. # Lists are created like this:
  136. #ip-addresses:
  137. #    - 192-168-0-2
  138. ip-addresses: []
  139.  
  140. # How many requests should be established to the Mojang API for Name -> UUID requests. Some other plugins as well
  141. # as the head minecraft block make such requests as well. Using this option you can limit the amount requests this
  142. # plugin should make.
  143. #
  144. # If you lower this value, other plugins could still make requests while FastLogin cannot.
  145. # Mojang limits the amount of request to 600 per 10 minutes per IPv4-address.
  146. mojang-request-limit: 600
  147.  
  148. # This option automatically registers players which are in the FastLogin database, but not in the auth plugin database.
  149. # This can happen if you switch your auth plugin or cleared the database of the auth plugin.
  150. # https://github.com/games647/FastLogin/issues/85
  151. auto-register-unknown: false
  152.  
  153. # This disables the auto login from fastlogin. So a premium (like a paid account) authentication is requested, but
  154. # the player won't be auto logged into the account.
  155. #
  156. # This can be used as 2Factor authentication for better security of your accounts. A hacker then needs both passwords.
  157. # The password of your minecraft and the password to login in with your auth plugin
  158. autoLogin: true
  159.  
  160. # Database configuration
  161. # Recommended is the use of MariaDB (a better version of MySQL)
  162.  
  163. # Single file SQLite database
  164. driver: org.sqlite.JDBC
  165. # File location
  166. database: '{pluginDir}/FastLogin.db'
  167.  
  168. # MySQL/MariaDB
  169. #driver: com.mysql.jdbc.Driver
  170. #host: localhost
  171. #port: 3306
  172. #database: fastlogin
  173. #username: myUser
  174. #password: myPassword
  175.  
  176. # It's strongly recommended to enable SSL and setup a SSL certificate if the MySQL server isn't running on the same
  177. # machine
  178. #useSSL: false
  179.  
  180. # HTTP proxies for connecting to the Mojang servers in order to check if the username of a player is premium.
  181. # This is a workaround to prevent rate-limiting by Mojang. These proxies will only be used once your server hit
  182. # the rate-limit or the custom value above.
  183. # Please make sure you use reliable proxies.
  184. proxies:
  185.   # 'IP:Port' or 'Domain:Port'
  186.   # - 'xyz.com:1337'
  187.   # - 'test.com:5131'
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top