API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Feb 5th, 2016
116
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 16.70 KB | None | 0 0
raw download clone embed print report
  1. # DeluxeMenus 1.4.1 main configuration file
  2. #
  3. # check_updates: <true/false>
  4. # Should DeluxeMenus check if there are any updates available on Spigot and inform ops there is an update available.
  5. #
  6. # click_menu_options.crouch_to_open: <true/false>
  7. # Should players need to sneak to open a click menu
  8. #
  9. # ==============================================================
  10. # Click menu configuration:
  11. #
  12. # You can create as many click menus you like.
  13. # Click menus are the only menus that require a priority set for each menu.
  14. # The highest priority menu you have permission for will be applied when you click a player.
  15. # Highest priority is 1, Lowest priority is 2147483647
  16. # Players must have permission for a click menu to open one!
  17. # All click menu permissions default to false so this even applies to Ops.
  18. # Permission for a click menu is: deluxemenus.clickmenu.<menuName>
  19. # Permission to open a click menu by command is: deluxemenus.clickmenucommand
  20. #
  21. # Click menus configuration layout:
  22. #
  23. # click_menus:
  24. # <menuName>:
  25. # menu_title: <title of menu goes here>
  26. # priority: <priority of this menu>
  27. # size: <size of this menu, increments of 9, max size is 54>
  28. # items:
  29. # <item identifier>:
  30. # material: <name or id>
  31. # data: <integer, used for data values for wool etc>
  32. # amount: <amount of this item to show>
  33. # slot: <slot number to put this item, slots start at 0 and end at 53 for a size 54 inventory>
  34. # priority: <this is used if you have multiple items set for the same slot>
  35. # permission: <the lowest priority item a player has permission for ex: 1, will be shown>
  36. # display_name: <display name to show for this item>
  37. # lore:
  38. # - 'placeholders can be used in the name and lore'
  39. # - '%viewer% shows the menu viewers name'
  40. # - '%<any placeholder from pAPI>% shows the targets values'
  41. # click_commands:
  42. # - '[player] runs this command as a player'
  43. # - '[player] tpa %player%'
  44. # - '[console] runs this command from the console'
  45. # - '[console] ban %player%'
  46. # - '[connect] connects the viewer to the specified bungee server'
  47. # - '[connect] Hub'
  48. # - '[close] closes the click menu'
  49. # - '[close]'
  50. #
  51. # You do not need to specify item options that you don't use!
  52. # The only required entries for a click menu item to be valid are:
  53. #
  54. # A valid material
  55. # A valid slot
  56. #
  57. # Every item in the items list must have a unique <item identifier>
  58. #
  59. # ==============================================================
  60. #
  61. # PER ITEM PERMISSION AND PRIORITY INFO:
  62. #
  63. # Per item permissions and priorities are optional.
  64. # High priority = 1, Lowest priority = 2147483647.
  65. # This allows you to show different items for a specific menu slot depending on the highest priority
  66. # item permission a player has. This makes your menus very dynamic :)
  67. #
  68. # You CAN NOT specify a permission without a priority!
  69. # You CAN specify a priority without a permission.
  70. # You should always create a low priority item without a permission which will act as the no permission
  71. # item if a player does not have permission for any of the items that require permission, otherwise
  72. # no item will be set in the slot if a player does not have permission for any of the permission items.
  73. #
  74. # ==============================================================
  75. #
  76. # GUI menu configuration:
  77. #
  78. # As of DeluxeMenus v1.4.1 GUI menus are a bit more advanced and
  79. # contain many more features than click menus. Most of these features will be implemented in click menus soon!
  80. #
  81. # You can create as many GUI menus you like.
  82. # Every menu name must be unique. There can not be duplicate menu names!
  83. # Players must have permission for a GUI menu to open one!
  84. # Ops should automatically have permission for any GUI menu.
  85. #
  86. # Permission to open a GUI menu is: deluxemenus.guimenu.<menuName>
  87. #
  88. # You specify the command which opens the GUI menu. Make sure this command
  89. # does not conflict with any existing commands on your server!
  90. # A GUI menu without an open command specified will not be loaded!
  91. #
  92. # GUI menus configuration layout:
  93. #
  94. # gui_menus:
  95. # <menuName>:
  96. # menu_title:
  97. # - '<title of menu goes here>'
  98. # - '<If using 1.8 you can specify many menu title frames and create animations>'
  99. # - '<in order for animations to work you must specify a menu_title_update_interval: ##>'
  100. # menu_title_update_interval: <amount of ticks to change title frames ex: 10, this is only needed if you have multiple frames>
  101. # command: <command to open this menu goes here>
  102. # size: <size of this menu, increments of 9, max size is 54>
  103. # update_interval: <time in seconds this gui should update for a player if an item is set to uodate placeholders>
  104. # items:
  105. # <item identifier>:
  106. # material: <name or id, for player heads use the format 'head;<players name/%player_name%>'>
  107. # data: <integer, used for data values for wool etc>
  108. # amount: <amount of this item to show>
  109. # slot: <slot number to put this item, slots start at 0 and end at 53 for a size 54 inventory>
  110. # priority: <this is used if you have multiple items set for the same slot>
  111. # view_requirement: <the lowest priority item a player meets this requirement for ex: 1, will be shown>
  112. # update: <true/false if this item should update placeholders on the interval set for the gui menu this item is in>
  113. # hide_attributes: <true/false if this item should display item attributes>
  114. # hide_enchantments: <true/false if this item should display item enchantment / level> (useful for 'enchantment glow' items)
  115. # hide_effects: <true/false if this item should display item effect attributes>
  116. # banner_meta: (this is used if you want to display a custom banner with specific patterns)
  117. # - <dyecolor>;<PatternType> (more information on where to find DyeColor and PatternType names below)
  118. # - 'RED;BASE'
  119. # - 'WHITE;CREEPER'
  120. # display_name: <display name to show for this item>
  121. # lore:
  122. # - 'placeholders can be used in the name and lore'
  123. # - '%<any placeholder from Papi>% shows the viewer values'
  124. # enchantments: valid enchantment names can be found here: https://hub.spigotmc.org/javadocs/spigot/org/bukkit/enchantments/Enchantment.html
  125. # - '<ENCHANTMENT>;<LEVEL>'
  126. # - 'SILK_TOUCH;1'
  127. # left_click_commands:
  128. # - '[close]'
  129. # right_click_commands:
  130. # - '[player] spawn'
  131. #
  132. #
  133. # You can specify if a GUI menu should be loaded from another file:
  134. #
  135. # gui_menus:
  136. # <menuName>:
  137. # file: 'menuName.yml'
  138. #
  139. # This allows you to keep your config clean and not have tons of GUI menus cluttering it.
  140. # The file format the GUI menu is loaded from must end in .yml
  141. # GUI menus loaded from other configuration files must follow a specific format as well...
  142. # To get started loading GUI menus from different files, simply create a GUI menu in this config and specify the file it will load from.
  143. # After that is done, use /dm reload and DeluxeMenus will create a folder and file specific to the GUI menu you specified.
  144. # If the file specified is created by DeluxeMenus (because it did not exist), a default GUI menu layout will be saved to that file.
  145. # From here you can edit it to your liking and use /dm reload to update your GUI menu!
  146. #
  147. # This loading from external config files is only available for gui menus and will not work for click menus yet....
  148. #
  149. # banner_meta must be listed with a specific format:
  150. # banner_meta:
  151. # - <DyeColor>;<PatternType>
  152. #
  153. # Valid DyeColor names can be found here: https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/DyeColor.html
  154. # Valid PatternTypes can be found here: https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/block/banner/PatternType.html
  155. # ==============================================================
  156. #
  157. # Click requirement information
  158. #
  159. # You can now add 'click requirements' to left and right click commands!'
  160. # These are defined per item and must follow a specific format:
  161. #
  162. # 'item_one':
  163. # material: DIAMOND
  164. # slot: 3
  165. # left_click_commands:
  166. # - '[close]'
  167. # - '[message] You were charged 100 dollars for clicking that item!'
  168. # - '[console] eco take %player% 100'
  169. # left_click_requirement:
  170. # expression: '%vaulteco_balance% > 100'
  171. # deny_commands:
  172. # - '[close]'
  173. # - '[message] &cYou dont have 100 dollars to click that item'
  174. # right_click_commands:
  175. # - '[close]'
  176. # - '[message] You had permission to click that item!'
  177. # right_click_requirement:
  178. # expression: 'BukkitPlayer.hasPermission("some.permission.toclick")'
  179. # deny_commands:
  180. # - '[close]'
  181. # - '[message] &cYou dont have permission to click that item'
  182. #
  183. # Every left/right_click_requirement MUST have an expression specified that would return a boolean (true/false)
  184. # These expressions must also follow JavaScript format as they are all javascript based!
  185. #
  186. # deny_commands: are optional and will be executed if the expression returns false.
  187. # You may use placeholders in your Javascript expressions to evaluate if the player meets the requirement or not.
  188. # You may also use a few keywords which give you access to the Player class and Bukkit.Server class if you understand the Bukkit API
  189. #
  190. # BukkitPlayer - references the Player object your expression is evaluating.
  191. # BukkitServer - references Bukkit.getServer() in the Bukkit API.
  192. #
  193. # The choice to use this system to evaluate if a player meets requirements to click an item was an easy choice.
  194. # This way I do not have to hook into every plugin to check if a player meets the requirement to click an item successfully.
  195. # You can simply use placeholders, or the keywords provided to give you access to the Player and Server objects.
  196. # If you want to check if a player has enough money, simply use an expression like so:
  197. #
  198. # expression: '%vaulteco_balance% >= 100' (checks if players balance is greater than or equal to 100)
  199. # If you want to charge the player, simply run the economy command to take the amount from the players balance in your click_commands
  200. # which will be executed if the player meets the requirement!
  201. # ==============================================================
  202. #
  203. # View requirement information
  204. #
  205. # You can add a 'view requirement' to an item if it has a priority value set for it
  206. # The view requirement has replaced the 'permission' entry for items
  207. # This allows you to specify a specific requirement in javascript for the item to be shown
  208. # In order to use view requirements, the item must have a priority value and a valid javascript expression
  209. # that returns true or false.
  210. #
  211. # 'item_one':
  212. # material: DIAMOND
  213. # slot: 3
  214. # priority: 1
  215. # view_requirement: '%vaulteco_balance% > 100'
  216. # 'item_two':
  217. # material: IRON_INGOT
  218. # slot: 3
  219. # priority: 2
  220. # view_requirement: 'BukkitPlayer.hasPermission("some.permission")'
  221. # 'item_three':
  222. # material: STONE
  223. # slot: 3
  224. # priority: 3
  225. #
  226. # In the example above, the priority 1 item view requirement will be checked first, if a player has over 100 dollars, that item will be shown.
  227. # If the player does not meet the requirement for the first item, the item with priority 2 will be checked. If the player does not have the permission
  228. # node some.permission, the final item 'item_three' will be set to slot 3 as the player did not meet the requirement for the first 2 items with
  229. # a higher priority.
  230. #
  231. # You may use placeholders in your Javascript expressions to evaluate if the player meets the requirement or not.
  232. # You may also use a few keywords which give you access to the Player class and Bukkit.Server class if you understand the Bukkit API
  233. #
  234. # BukkitPlayer - references the Player object your expression is evaluating.
  235. # BukkitServer - references Bukkit.getServer() in the Bukkit API.
  236. #
  237. # The choice to use this system to evaluate if a player meets requirements to click an item was an easy choice.
  238. # This way I do not have to hook into every plugin to check if a player meets the requirement to click an item successfully.
  239. # You can simply use placeholders, or the keywords provided to give you access to the Player and Server objects.
  240. # If you want to check if a player has enough money, simply use an expression like so:
  241. #
  242. # view_requirement: '%vaulteco_balance% >= 100' (checks if players balance is greater than or equal to 100)
  243. # ==============================================================
  244. #
  245. #
  246. # You do not need to specify item options that you don't use!
  247. # The only required entries for a gui menu item to be valid are:
  248. #
  249. # A valid material
  250. # A valid slot
  251. #
  252. # Every item in the items list must have a unique <item identifier>
  253. #
  254. # If you choose to update placeholders for a specific item, you must specify update_interval: <time>
  255. # in the GUI menu options for the specific GUI menu.
  256. # Only GUI menus with at least one item that has update: true will update those specific items placeholders.
  257. #
  258. # Every click_command must start with a specific identifier to know what to do for the execution.
  259. # Valid click_command identifiers:
  260. #
  261. # [console] - Execute a command from the console
  262. # Usage: - '[console] <command with no slash>'
  263. #
  264. # [player] - Execute a command for the menu viewer
  265. # Usage: - '[player] <command with no slash>'
  266. #
  267. # [message] - Send a message to the menu viewer
  268. # Usage: - [message] <message to send to the player
  269. #
  270. # [close] - Close the viewers open menu
  271. # Usage: - '[close]
  272. #
  273. # [openguimenu] - Open a GUI menu (can only be used in GUI menu click_commands)
  274. # Usage: - '[openguimenu] <guiMenuName>'
  275. #
  276. # [openclickmenu] - Open a different click menu for the viewer and target (can only be used in click menu click_commands)
  277. # Usage: - '[openclickmenu] <clickMenuName>'
  278. #
  279. # [connect] - Connect to the specified bungee server
  280. # Usage: - '[connect] <serverName>'
  281. #
  282. # [commandevent] - Fire a PlayerCommandPreprocessEvent for commands that do not use the bukkit command system
  283. # Usage: - '[commandevent] <command with no slash>'
  284. #
  285. #
  286. # A NOTE WHEN EDITING THIS OR ANY DeluxeMenus CONFIGURATION FILE:
  287. # This config is sensitive to yaml formatting errors
  288. # KEEP A BACKUP WHEN EDITING YOUR FILE BEFORE UPLOADING TO YOUR SERVER!!!
  289. # Make sure every String you modify or add is enclosed in 'apostrophes
  290. check_updates: true
  291. click_menu_options:
  292. sneak_to_open: true
  293. kits:
  294. - '&c&lKits &7[&8Click To Select&7]'
  295. menu_title_update_interval: 12
  296. open_command: kits
  297. size: 9
  298. update_interval: 1
  299. items:
  300. starteron:
  301. material: iron_sword
  302. slot: 1
  303. priority: 1
  304. update: true
  305. hide_attributes: true
  306. view_requirement: '"%essentials_kit_is_available_starter%".equalsIgnoreCase ("yes")'
  307. display_name: '&c&lStarter Kit'
  308. lore:
  309. - '&8+---------------------+'
  310. - '&7Starter kit with basic items.'
  311. left_click_commands:
  312. - '[player] kit starter'
  313. - '[close]'
  314. right_click_commands:
  315. - '[player] kit starter'
  316. - '[close]'
  317. starteroff:
  318. material: barrier
  319. slot: 1
  320. priority: 2
  321. update: true
  322. hide_enchantments: true
  323. enchantments:
  324. - DURABILITY;1
  325. display_name: '&8[&7Unavailable&8] &c&lStarter Kit'
  326. lore:
  327. - '&8+---------------------+'
  328. - '&7This kit is on cooldown!'
  329. - '&7You must wait &c%essentials_kit_time_until_available_starter%'
  330. - '&7Before using this kit again.'
  331. left_click_commands:
  332. - '[console] playsound mob.bat.takeoff %player_name% ~ ~ ~ 1 1.5 1'
  333. right_click_commands:
  334. - '[console] playsound mob.bat.takeoff %player_name% ~ ~ ~ 1 1.5 1'
  335. gui_menus:
  336. example:
  337. menu_title: '&aExample menu'
  338. priority: 1
  339. size: 9
  340. items:
  341. '1':
  342. material: DIAMOND_BLOCK
  343. data: 0
  344. amount: 1
  345. slot: 0
  346. display_name: '&aHey &f%viewer%'
  347. lore:
  348. - '&aYou opened a click menu'
  349. - '&afor player: &f%player_name%'
  350. click_commands:
  351. - '[close]'
  352. '2':
  353. material: 368
  354. data: 0
  355. amount: 1
  356. slot: 1
  357. priority: 1
  358. permission: examplemenu.item.teleport
  359. display_name: '&bTeleport to player'
  360. lore:
  361. - '&bClick to teleport to player &f%player_name%'
  362. click_commands:
  363. - '[player] tp %player_name%'
  364. - '[close]'
  365. '3':
  366. material: 381
  367. data: 0
  368. amount: 1
  369. slot: 1
  370. priority: 2
  371. permission: examplemenu.item.tpa
  372. display_name: '&bRequest teleport to player'
  373. lore:
  374. - '&bClick to request to'
  375. - '&bteleport to &f%player_name%'
  376. click_commands:
  377. - '[player] tpa %player_name%'
  378. - '[close]'
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
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
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!