Advertisement
RootI

Untitled

Feb 3rd, 2021
56
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.12 KB | None | 0 0
  1. #+------------------------------------------------------------------------------------------------------+#
  2. #| |#
  3. #| |#
  4. #| J P R E M I U M |#
  5. #| C O N F I G U R A T I O N |#
  6. #| |#
  7. #| |#
  8. #+------------------------------------------------------------------------------------------------------+#
  9.  
  10. version: 'CLEARED-Bungee-1.8.0'
  11.  
  12. # JPremium currently supports only MySQL databases.
  13. # When JPremium cannot connect your database, issues are always produced by your database or the connection between your BungeeCord and your database!
  14. # If you have issues, please see this wiki page: https://github.com/Jakubson/JPremiumCleared/wiki#database-issues
  15. storageHost: '127.0.0.1'
  16. storagePort: 3306
  17. storageDatabase: ''
  18. storageUser: ''
  19. storagePassword: ''
  20. storageProperties: [useSSL=true, verifyServerCertificate=true]
  21.  
  22. # Storage connection pool settings.
  23. # Do not change these settings unless you know what you are doing!
  24. connectionPoolSize: 10
  25. connectionPoolIdle: 10
  26. connectionPoolTimeout: 5000
  27. connectionPoolLifetime: 1800000
  28.  
  29. # The mail server which is used to send mails.
  30. # Please enter data only if you want to use the passwords recovery system.
  31. # If you do not want to use it, please also disable the change mail address and recovery password commands.
  32. mailHost: ''
  33. mailPort: 25
  34. mailUser: ''
  35. mailPassword: ''
  36. mailUseTLS: true
  37.  
  38. # The access token which is used to verify connections on your Spigot servers whether connections come from your BungeeCord.
  39. # Please enter fully random unique value! Not: 'your-server-name-jpremium'!
  40. # The same token you have to enter on all your Spigot servers.
  41. accessToken: ''
  42.  
  43. # The limbo server names in your BungeeCord network.
  44. # Not authorised players are redirected to the servers.
  45. limboServerNames: [lobby]
  46.  
  47. # The main server names in your BungeeCord network.
  48. # Authorised players are redirected to the servers.
  49. mainServerNames: [hub]
  50.  
  51. # What unique ids should JPremium assign for players.
  52. # There are three options and each option has different restrictions.
  53. # It is not recommended changing this option when some players are already registered.
  54. # For more information, please read this wiki page: https://github.com/Jakubson/JPremiumCleared/wiki#fixed-unique-ids
  55. uniqueIdsType: OFFLINE
  56.  
  57. # Should JPremium force new players to register on your server, website or both side.
  58. # There are three options to choose: 0 - server, 1 - server and website, 2 - website.
  59. registerOnWebsite: 0
  60.  
  61. # Should JPremium register new premium players.
  62. # When it is enabled, cracked players with premium nickname cannot join to your server.
  63. registerPremiumUsers: false
  64.  
  65. # Should JPremium redirect players to their last server where they were before quit.
  66. lastServerRedirection: false
  67.  
  68. # The server names in your BungeeCord network.
  69. # Players will not be redirected to the servers as their last server.
  70. lastServerRestrictions: [kback]
  71.  
  72. # Should JPremium redirect players to one of the main server from the server which is shutting down.
  73. disconnectRedirection: false
  74.  
  75. # Should JPremium disconnect cracked players who enter wrong password during login.
  76. disconnectWhenWrongPassword: true
  77.  
  78. # Should JPremium recognise Bedrock players and alters their unique ids to bedrock.
  79. # Works only when you install GeyserMC and Floodgate on your server.
  80. # For more information, please read this wiki page: https://github.com/Jakubson/JPremiumCleared/wiki#bedrock-support
  81. floodgateSupport: false
  82.  
  83. # Should JPremium require to confirm a password in the register, change password and cracked commands?
  84. # If you enable it, please do not forget to change the usage messages in the message file.
  85. confirmPassword: true
  86.  
  87. # Should JPremium verify captcha codes which are entered by cracked players.
  88. # If you set disable it, please also set 'captchaMapSlot' to '-1' in your JPremium configuration files on all your Spigot servers.
  89. verifyCaptchaCode: false
  90.  
  91. # Should JPremium show a boss bar with remain time to authorisation for cracked players.
  92. showBossBarRemainAuthorisationTimer: true
  93.  
  94. # Should JPremium keep a password when players change an account type for premium.
  95. keepPremiumUserPasswords: false
  96.  
  97. # Should JPremium check server statuses and connect players only with online servers.
  98. checkServerStatuses: false
  99.  
  100. # Should JPremium use the backup server when the official server is down to authorise players.
  101. # As the backup server JPremium use CouldFlare Workers.
  102. useBackupServer: false
  103.  
  104. # Should JPremium load user data during the login stage.
  105. # It is an experimental feature.
  106. loadUserProfileDataOnJoin: false
  107.  
  108. # The maximum quantity of user profiles which cracked players can register using the same IP addresses.
  109. # When 'registerPremiumUsers' option is enabled, the limit is not apply for premium players.
  110. maximumUserProfilesPerAddress: 3
  111.  
  112. # The maximum time (in seconds) which cracked players have for login or register.
  113. maximumAuthorisationTime: 90
  114.  
  115. # The maximum time (in minutes) for which cracked players can start sessions?
  116. # Sessions work only when cracked players have the same IP addresses, so it is not recommended to set the value too high.
  117. maximumSessionTime: 10440
  118.  
  119. # The session time (in minutes) which is automatically started after cracked players login or register.
  120. autoSessionTime: 10440
  121.  
  122. # The absent time (is days) after which cracked players are automatically unregistered.
  123. automaticUnregisterTime: 0
  124.  
  125. # The hashing algorithm which is used to hash cracked player passwords.
  126. # There are two options: SHA256, SHA512, BCRYPT.
  127. # All of algorithms are salted.
  128. passwordHashingAlgorithm: SHA256
  129.  
  130. # The maximum quantity of join requests which can be processed within 3 minutes.
  131. # If it is exceed, the next join requests are rejected.
  132. antiBotSensitive: 99999
  133.  
  134. # The safe password pattern (in regular expression). Cracked player passwords have to match to it.
  135. safePasswordPattern: '[\S]{3,25}'
  136.  
  137. # The hostnames which players can use to connect with your BungeeCord server.
  138. # If you want to disable it, please set the value to '[]'.
  139. # All host names have to have ports, for example: 'acceptedHostnames: [mc.example:25565]'.
  140. acceptedHostnames: []
  141.  
  142. # The commands which not logged cracked players can execute.
  143. logoutUserCommands: [login, register, recoverypassword, reg, l]
  144.  
  145. # The command aliases.
  146. # To add more aliases for commands, please add new values using this format '<command>CommandAliases: [<alias>, <alias>, ...]', for example: 'changePasswordCommandAliases: [chpass]'.
  147. # If you want to disable a command, you have to enter the command to the 'disabled_commands' list in your BungeeCord configuration file.
  148. loginCommandAliases: [l]
  149. registerCommandAliases: [reg, req]
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement