Advertisement
Guest User

Untitled

a guest
Aug 19th, 2017
99
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 17.11 KB | None | 0 0
  1. server: 1.12.1RC.spigot
  2. console output:
  3.  
  4. 16:56:41 [WARNING] Exception encountered when loading plugin: LuckPerms java.lang.NoSuchMethodError: net.md_5.bungee.config.Configuration.contains(Ljava/lang/String;)Z at me.lucko.luckperms.bungee.BungeeConfig.contains(BungeeConfig.java:80) at me.lucko.luckperms.common.config.ConfigKeys.lambda$static$0(ConfigKeys.java:116) at me.lucko.luckperms.common.config.keys.AbstractKey.get(AbstractKey.java:41) at me.lucko.luckperms.common.config.AbstractConfiguration.loadKeyValue(AbstractConfiguration.java:83) at com.github.benmanes.caffeine.cache.UnboundedLocalCache$UnboundedLocalLoadingCache.lambda$new$0(UnboundedLocalCache.java:922) at com.github.benmanes.caffeine.cache.UnboundedLocalCache.lambda$computeIfAbsent$2(UnboundedLocalCache.java:235) at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660) at com.github.benmanes.caffeine.cache.UnboundedLocalCache.computeIfAbsent(UnboundedLocalCache.java:231) at com.github.benmanes.caffeine.cache.LocalCache.computeIfAbsent(LocalCache.java:113) at com.github.benmanes.caffeine.cache.LocalLoadingCache.get(LocalLoadingCache.java:67) at java.lang.Iterable.forEach(Iterable.java:75) at me.lucko.luckperms.common.config.AbstractConfiguration.loadAll(AbstractConfiguration.java:67) at me.lucko.luckperms.bungee.LPBungeePlugin.onEnable(LPBungeePlugin.java:141) at net.md_5.bungee.api.plugin.PluginManager.enablePlugins(PluginManager.java:227) at net.md_5.bungee.BungeeCord.start(BungeeCord.java:267) at net.md_5.bungee.BungeeCordLauncher.main(BungeeCordLauncher.java:55) at net.md_5.bungee.Bootstrap.main(Bootstrap.java:15)
  5.  
  6. full config below:
  7.  
  8. ####################################################################################################
  9. # +----------------------------------------------------------------------------------------------+ #
  10. # | __ __ ___ __ __ | #
  11. # | | | | / ` |__/ |__) |__ |__) |\/| /__` | #
  12. # | |___ \__/ \__, | \ | |___ | \ | | .__/ | #
  13. # | | #
  14. # | | #
  15. # | SOURCE CODE: https://github.com/lucko/LuckPerms | #
  16. # | WIKI: https://github.com/lucko/LuckPerms/wiki | #
  17. # | BUG REPORTS: https://github.com/lucko/LuckPerms/issues | #
  18. # | | #
  19. # | Each option in this file is documented and explained here: | #
  20. # | ==> https://github.com/lucko/LuckPerms/wiki/Configuration | #
  21. # | | #
  22. # | New options are not added to this file automatically. Default values are used if an | #
  23. # | option cannot be found. The latest config versions can be obtained at the link above. | #
  24. # +----------------------------------------------------------------------------------------------+ #
  25. ####################################################################################################
  26.  
  27. # +----------------------------------------------------------------------------------------------+ #
  28. # | General | #
  29. # +----------------------------------------------------------------------------------------------+ #
  30.  
  31. # The name of the server, used for server specific permissions. Set to 'global' to disable.
  32. server: bungee
  33.  
  34. # If users on this server should have their global permissions applied.
  35. # If set to false, only server specific permissions will apply for users on this server
  36. include-global: true
  37.  
  38. # If users on this server should have their global world permissions applied.
  39. # If set to false, only world specific permissions will apply for users on this server
  40. include-global-world: true
  41.  
  42. # If users on this server should have global (non-server specific) groups applied
  43. apply-global-groups: true
  44.  
  45. # If users on this server should have global (non-world specific) groups applied
  46. apply-global-world-groups: true
  47.  
  48. # If UUIDs should be pulled from the server, or looked up by username based upon previous
  49. # connections.
  50. #
  51. # This option should be set to true in most cases. When set to false, in order to get a player's
  52. # UUID, LuckPerms will:
  53. #
  54. # 1. Check if a player with the given username has joined before, if they have, use the UUID they
  55. # used on their previous login.
  56. # 2. Save and return the players "current" uuid.
  57. #
  58. # For offline mode (cracked) servers, a players UUID is generated based upon their username.
  59. #
  60. # IMPORTANT:
  61. # If you are using BungeeCord proxy running in online mode, it is important that "online-mode=false"
  62. # is set in server.properties, but "bungeecord: true" is set in the spigot.yml. You also need to set
  63. # "ip_forward: true" in BungeeCord's config.yml.
  64. #
  65. # If for whatever reason you are not able to do this, and do not have ip-forward enabled, then you
  66. # may need to set "use-server-uuids" to false.
  67. #
  68. # If your proxy is running in offline mode, you should still be setting up ip-forwarding as
  69. # described above, but may also find that you need to set "bungee-online-mode" to false in
  70. # paper.yml, if you are using Paper. (https://ci.destroystokyo.com/job/PaperSpigot/)
  71. #
  72. # This option only really exists for networks who for whatever reason cannot setup proper ip
  73. # forwarding.
  74. use-server-uuids: true
  75.  
  76. # If the servers own UUID cache/lookup facility should be used when there is no record for a player
  77. # in the LuckPerms cache.
  78. #
  79. # Since BungeeCord doesn't maintain it's own UUID cache, when this option is true, LuckPerms will
  80. # try to find a uuid for a username using RedisBungee, if installed.
  81. use-server-uuid-cache: false
  82.  
  83. # If the plugin should send log notifications to users whenever permissions are modified.
  84. log-notify: true
  85.  
  86. # Mirrors world names. Whenever LuckPerms checks what world a user is in, if the world name is in
  87. # this list, the value assigned will be sent forward for permission calculation instead.
  88. world-rewrite:
  89. # world_nether: world
  90. # world_the_end: world
  91.  
  92. # Rewrites group names. The underlying name of the group does not change, just the output in
  93. # commands / placeholders / Vault.
  94. group-name-rewrite:
  95. # default: Member
  96.  
  97. # Controls how temporary permissions/parents/meta should be accumulated
  98. #
  99. # The default behaviour is "deny"
  100. # If "accumulate": durations will be added to the existing expiry time
  101. # If "replace": durations will be replaced if the new duration is later than the current expiration
  102. # If "deny": the command will just fail if you try to add another node with the same expiry
  103. temporary-add-behaviour: deny
  104.  
  105. # How should LuckPerms determine a users "primary" group.
  106. #
  107. # Available Options:
  108. # -> stored use the value stored against the users record in the file/database
  109. # -> parents-by-weight just use the users most highly weighted parent
  110. # -> all-parents-by-weight same as above, but calculates based upon all parents inherited from both
  111. # directly and indirectly
  112. primary-group-calculation: stored
  113.  
  114. # If the plugin should check for "extra" permissions with users run LP commands.
  115. #
  116. # These extra permissions allow finer control over what users can do with each command, and
  117. # who they have access to edit.
  118. #
  119. # The permissions are *not* static, unlike the 'base' permisssions, and will depend upon the
  120. # arguments given within the command.
  121. argument-based-command-permissions: false
  122.  
  123.  
  124.  
  125.  
  126. # +----------------------------------------------------------------------------------------------+ #
  127. # | Permission Calculation | #
  128. # +----------------------------------------------------------------------------------------------+ #
  129.  
  130. # If the plugin should apply wildcard permissions.
  131. # If set to true, LuckPerms will detect wildcard permissions, and resolve & apply all registered
  132. # permissions matching the wildcard.
  133. apply-wildcards: true
  134.  
  135. # If the plugin should parse regex permissions.
  136. # If set to true, LuckPerms will detect regex permissions, marked with "r=" at the start of the
  137. # node, and resolve & apply all registered permissions matching the regex.
  138. apply-regex: true
  139.  
  140. # If the plugin should complete and apply shorthand permissions.
  141. # If set to true, LuckPerms will detect and expand shorthand node patterns.
  142. apply-shorthand: true
  143.  
  144. # If the plugin should apply the permissions & groups defined in the BungeeCord config.yml
  145. # If set to false, LuckPerms will ignore these values.
  146. apply-bungee-config-permissions: false
  147.  
  148. # Define special group weights for this server.
  149. # Default is just 0.
  150. group-weight:
  151. # admin: 10
  152.  
  153.  
  154.  
  155.  
  156. # +----------------------------------------------------------------------------------------------+ #
  157. # | Meta Formatting & Stacking | #
  158. # +----------------------------------------------------------------------------------------------+ #
  159.  
  160. # Allows you to setup prefix/suffix stacking options.
  161. #
  162. # Available formats:
  163. # - highest
  164. # - lowest
  165. # - highest_own
  166. # - lowest_own
  167. # - highest_on_track_<track>
  168. # - lowest_on_track_<track>
  169. # - highest_not_on_track_<track>
  170. # - lowest_not_on_track_<track>
  171. #
  172. # Each element is added in the order listed.
  173. meta-formatting:
  174. prefix:
  175. format:
  176. - "highest"
  177. start-spacer: ""
  178. middle-spacer: " "
  179. end-spacer: ""
  180. suffix:
  181. format:
  182. - "highest"
  183. start-spacer: ""
  184. middle-spacer: " "
  185. end-spacer: ""
  186.  
  187.  
  188.  
  189.  
  190. # +----------------------------------------------------------------------------------------------+ #
  191. # | Storage | #
  192. # +----------------------------------------------------------------------------------------------+ #
  193.  
  194. # Which storage method the plugin should use.
  195. #
  196. # See: https://github.com/lucko/LuckPerms/wiki/Choosing-a-Storage-type
  197. # Currently supported: mysql, mariadb, postgresql, sqlite, h2, json, yaml, mongodb
  198. #
  199. # Fill out connection info below if you're using MySQL, MariaDB, PostgreSQL or MongoDB
  200. # If your MySQL server supports it, the "mariadb" option is preferred over "mysql".
  201. storage-method: mysql
  202.  
  203. # When using a file-based storage type, LuckPerms can monitor the data files for changes, and then
  204. # schedule automatic updates when changes are detected.
  205. #
  206. # If you don't want this to happen, set this option to false.
  207. watch-files: true
  208.  
  209. # This block enables support for split datastores.
  210. split-storage:
  211. enabled: false
  212. methods:
  213. user: h2
  214. group: h2
  215. track: h2
  216. uuid: h2
  217. log: h2
  218.  
  219. data:
  220. # Uses standard DB engine port by default
  221. # MySQL: 3306, PostgreSQL: 5432, MongoDB: 27017
  222. # Specify as "host:port" if differs
  223. address: xxxxxxx
  224.  
  225. database: xxxx
  226. username: xxxx
  227. password: xxxxxxxxx
  228. pool-size: 10 # The size of the MySQL connection pool.
  229.  
  230. # The prefix for all LuckPerms tables. Change this is you want to use different tables for
  231. # different servers.
  232. #
  233. # This should *not* be set to "lp_" if you have previously ran LuckPerms v2.16.81 or earlier with
  234. # this database.
  235. table_prefix: 'luckperms_'
  236.  
  237. # The prefix to use for all LuckPerms collections. Change this if you want to use different
  238. # collections for different servers. The default is no prefix.
  239. mongodb_collection_prefix: ''
  240.  
  241. # This option controls how frequently LuckPerms will perform a sync task.
  242. # A sync task will refresh all data from the storage, and ensure that the most up-to-date data is
  243. # being used by the plugin.
  244. #
  245. # This is disabled by default, as most users will not need it. However, if you're using a remote
  246. # storage type without a messaging service setup, you may wish to set this value to something like
  247. # 3.
  248. #
  249. # Set to -1 to disable the task completely.
  250. sync-minutes: 3
  251.  
  252. # Settings for the messaging service
  253. #
  254. # If enabled and configured, LuckPerms will use the messaging system to inform other
  255. # connected servers of changes. Use the command "/luckpermsbungee networksync" to push changes.
  256. # Data is NOT stored using this service. It is only used as a messaging platform.
  257. #
  258. # If you decide to enable this feature, you should set "sync-minutes" to -1, as there is no need for
  259. # LuckPerms to poll the database for changes.
  260. #
  261. # Available options:
  262. # -> bungee uses the plugin messaging channels. Must be enabled on all connected servers to
  263. # work.
  264. # -> redis uses redis pub sub to push changes. Your redis server must be configured below.
  265. # -> redisbungee uses redis pub sub to push changes, using RedisBungee's API. You need to have the
  266. # RedisBungee plugin installed.
  267. # -> none nothing
  268. messaging-service: bungee
  269.  
  270. # If LuckPerms should automatically push updates after a change has been made with a command.
  271. auto-push-updates: true
  272.  
  273. # Settings for Redis.
  274. # Port 6379 is used by default; set address to "host:port" if differs
  275. redis:
  276. enabled: false
  277. address: localhost
  278. password: ''
  279.  
  280.  
  281.  
  282.  
  283. # +----------------------------------------------------------------------------------------------+ #
  284. # | Default Assignments | #
  285. # +----------------------------------------------------------------------------------------------+ #
  286.  
  287. # This section allows you to define defaults to give users whenever they connect to the server.
  288. # The default assignments are highly configurable and conditional.
  289. #
  290. # There is one default assignment built into LuckPerms, which will add all users to the "default"
  291. # group if they are not a member of any other group. This setting cannot be disabled. However, you
  292. # can use this section to add more of your own.
  293. #
  294. # IMPORTANT:
  295. # In order to save storage space, LuckPerms does not store users who have no permissions defined,
  296. # and are only a member of the default group. Adding default assignments to this section will negate
  297. # this effect. It is HIGHLY RECCOMENDED that instead of assigning defaults here, you add permissions
  298. # to the "default" group, or set the "default" group to inherit other groups, and then use the
  299. # group-name-rewrite rule above.
  300. #
  301. # It is also important to note that these rules are considered every time a player logs into the
  302. # server, and are applied directly to the user's data. Simply removing a rule here will not reverse
  303. # the effect of that rule on any users who have already had it applied to them.
  304. #
  305. # The "has" and "lacks" conditions below support standard boolean logic, using the 'and' & 'or'
  306. # characters used in Java.
  307. # e.g. "(some.other.permission | some.permission.other) & some.thing.else" == a user has
  308. # 'some.other.permission', or 'some.permission.other', and they also have 'some.thing.else'
  309. #
  310. # Groups are represented by the permission node: group.<group name>
  311. # Per server and per world nodes are represented by "server-world/permission" or "server/permission"
  312. #
  313. # Within conditions, permission nodes MUST be escaped using "<" and ">". See the example below.
  314. #
  315. # Explanation of the examples below: (they're just to demonstrate the features & use cases)
  316. #
  317. # rule1:
  318. # If a user is either in the vip or vip+ group, and they have the "titles.titlecollector" permission
  319. # set to true, and the "some.random.permission" set to false... if they're not in the group
  320. # "prison_titlepack" on the "prison" server, then give add them to the "prison_titlepack" group on
  321. # the "prison" server, and remove "some.random.permission".
  322. #
  323. # rule2:
  324. # If the user isn't in any of the following groups on the skyblock server: sb_level1, sb_level2,
  325. # sb_level3, then add them to sb_level1 on the skyblock server.
  326. #
  327. # rule3:
  328. # If the user is a member of the default group, remove them from default, add them to member, and
  329. # set their primary group to member.
  330. #
  331. # WARNING: Unlike internal commands, this system does not ensure that a group exists before adding
  332. # a user to it. It also does not unsure that a user is a member of a group before making that group
  333. # their primary group.
  334. #
  335. # Before you use "give: group.<name>" or "set-primary-group", make sure that the group exists, and
  336. # that the user is a member of the group.
  337. default-assignments:
  338. # rule1:
  339. # if:
  340. # has-true: (<group.vip> | <group.vip+>) & <titles.tilecollector>
  341. # has-false: <some.random.permission>
  342. # lacks: <prison/group.prison_titlepack>
  343. # give:
  344. # - prison/group.prison_titlepack
  345. # take:
  346. # - some.random.permission
  347. # rule2:
  348. # if:
  349. # lacks: <skyblock/group.sb_level1> & <skyblock/group.sb_level2> & <skyblock/group.sb_level3>
  350. # give:
  351. # - skyblock/group.sb_level1
  352. # rule3:
  353. # if:
  354. # has-true: <group.default>
  355. # take:
  356. # - group.default
  357. # give:
  358. # - group.member
  359. # set-primary-group: member
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement