Advertisement
Guest User

FeatherBoard config.yml

a guest
Feb 15th, 2018
148
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 12.37 KB | None | 0 0
  1. # ------------------------------------ #
  2. #
  3. # FeatherBoard 4
  4. # Runs like a feather on your server
  5. # (c) Maxim Van de Wynckel
  6. #
  7. # ------------------------------------ #
  8.  
  9. # Plugin requirements:
  10. # (Required) MVdWPlaceholderAPI 2 or higher
  11.  
  12. # Permissions: To use the action groups give them the permission
  13. # featherboard.group.<group>
  14. # Make sure to remove them from the other groups
  15. # when giving a new permission.
  16.  
  17. # Variables: These variables can be used in the TEXT section
  18. # of both the header as the footer.
  19. #
  20. # {PLAYER} - Player name
  21. # {PLAYERNICK} - Player nickname
  22. # {SERVER} - Server name
  23. # {PLAYERCOUNT} - Server player count
  24. # {BUNGEECOUNT} - Bungee network player count
  25. # 5000+ more ... see spigot page
  26.  
  27. # Formatting: These are formatting tags allowing you to format the animations
  28. # or placeholders.
  29. #
  30. # Substring: This allows you to split a word (even a placeholder) in lines
  31. # example: <substring begin=0 end=3>Hello World</substring> = Hel
  32. # usage: This can be used to split placeholders when creating a typewriter
  33. # or to split the colors in a placeholder.
  34. #
  35. # Scroll: This creates a scrolling animation of the text inside it. It accepts
  36. # two arguments (the length and space between scrolls).
  37. # example: <scroll width=20 spaces=20>&2This is a &atest</scroll>
  38. #
  39. # PLENTY MORE! See spigot page
  40.  
  41. #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
  42. # GENERAL PLUGIN SETTINGS
  43. #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
  44.  
  45. ## Config version (DO NOT EDIT)
  46. config: 4
  47.  
  48. ## Language file
  49. lang: 'en'
  50.  
  51. ## Debug mode
  52. debug: false
  53.  
  54. ## Log to file
  55. log:
  56. enabled: true
  57. # Reset log on startup
  58. reset: true
  59.  
  60. ## Update checking
  61. update:
  62. # RECOMMENDED YOU LEAVE THIS TRUE
  63. # Support for older versions is not provided
  64. check: false
  65.  
  66. #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
  67. # PLUGIN SPECIFIC SETTINGS
  68. #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
  69.  
  70. # Toggling allows you to disable the scoreboard
  71. database:
  72. # If you want the toggle to stay even when your users
  73. # log off you can enable this. Keep in mind that this requires a
  74. # MySQL or SQLite database.
  75. # If you are configuring the plugin for the first time it is advised
  76. # to stay away from these settings until you managed the scoreboard
  77. # set up.
  78. persistent: false
  79. # Database configuration is SIMILAR to http://wiki.bukkit.org/Bukkit.yml#database
  80. # with isolation, url, driver, ...
  81. # Database name
  82. database: "featherboard"
  83. # Database username
  84. username: bukkit
  85. # Database password
  86. password: walrus
  87. # Database driver URL
  88. # {DIR} will be replaced with the plugin directory
  89. # {NAME} will be replaced wit the plugin name
  90. url: jdbc:sqlite:{DIR}{NAME}.db
  91. # Save interval in ticks
  92. save-interval: 6000
  93.  
  94. # Disabled worlds. Add your world name in this list to disable it.
  95. disabled-worlds:
  96. - 'MiniGames'
  97. - 'Hub_the_end'
  98. - 'Hub_nether'
  99.  
  100. # Scoreboard assigning. The boards can be assigned by various ways.
  101. # default the scoreboards will be assigned by permissions.
  102. # You can have multiple ways of assigning a scoreboard, but
  103. # keep in mind that it uses a "first come first served" principal
  104. # Multiple assign methods is only recommended when using things like
  105. # TIME or WORLD in combination with something else.
  106. #
  107. # PERMISSION - Assign scoreboards based on permissions
  108. # This is the default setting (since 2014)
  109. # featherboard.group.<scoreboard>
  110. #
  111. # GROUP - Assign scoreboards based on Vault groups
  112. # this means the scoreboard name has to
  113. # have the name of your Vault group.
  114. #
  115. # WORLD - Assign scoreboards based on the world
  116. # the player is in.
  117. #
  118. # TIME - Assign the scoreboard based on the day.
  119. # "day" for Day and "night" for night.
  120. #
  121. # NONE - Do no assign scoreboards and just rely on
  122. # manual assigning (triggers, etc...)
  123. #
  124. # LANGUAGE - Client language (en,nl,fr) Two letter language code
  125. #
  126. # PLACEHOLDER:* - Assign the scoreboard based on a placeholder
  127. # this method can be very intensive for certain non cached
  128. # placeholders.
  129. # It will look for scoreboardname.yml files matching the result
  130. # of the placeholder.
  131. # Replace "*" with an actual placeholder (ex. "PLACEHOLDER:{isflying}" )
  132. # KEEP IN MIND: Fast switching scoreboards is not a good thing.
  133. #
  134. # SPAWN_DISTANCE - Assign the scoreboard based on the distance to the world's spawn
  135. # Name your scoreboard: "spawn_distance_*" where * is a number
  136. # representing the distance. (ex. "spawn_distance_10")
  137. # The example would math the scoreboard if you are within 10 blocks
  138. # to the spawn.
  139. scoreboard-assigning:
  140. - 'PERMISSION'
  141.  
  142. # GUI: This is a feature enabling a GUI to select a specific scoreboard
  143. # The GUI will show all scoreboards you have permission to. It is not very
  144. # configurable in the way you can't control the location or order of the scoreboards
  145. # For a more configurable GUI I recommend DeluxeMenus
  146. gui:
  147. # This is the title of the GUI
  148. title: "Scoreboards"
  149. # Size of the GUI (leave to -1 to make it dynamic)
  150. # Sizes: 9,27,54
  151. size: -1
  152.  
  153. #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
  154. # ADVANCED SETTINGS
  155. #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#
  156.  
  157. # Placeholder settings
  158. placeholder:
  159. # Placeholder update method
  160. # COMPATIBLE - Only downloads compatible placeholders.
  161. # FORCE - Force download all placeholders.
  162. # UPDATE_ONLY - Only update existing downloaded placeholders.
  163. update-method: "COMPATIBLE"
  164. # Clear unused placeholders that are not enabled.
  165. clear-unused: true
  166. # Config cache only
  167. # This will only keep placeholders you use in the config
  168. # This breaks:
  169. # 1) MVdWPlaceholderAPI hooked plugins that make you use placeholders
  170. # in their plugins.
  171. # 2) Plugins that add custom placeholders to MVdWPlaceholderAPI
  172. config-cache: false
  173.  
  174. # Scoreboards file path. This is the folder path containing the .yml files containing
  175. # the scoreboards.
  176. scoreboards-location: "scoreboards"
  177.  
  178. # Modules file path. This is the folder path containing the JAR files for additional
  179. # placeholder or featherboard modules.
  180. modules-location: "modules"
  181.  
  182. # Tweaks to increase or tune performance
  183. tweaks:
  184. # Reset all scoreboard on startup
  185. # this is similar to manually deleting the scoreboard.dat
  186. reset-scoreboard-data: false
  187. # This option does not send scoreboard remove packets
  188. # to the client on join.
  189. keep-scoreboard-join: false
  190. # This option does not send scoreboard remove packets
  191. # to the client on quit. This can increase performance on servers
  192. # where players quit a lot (hubs, ...)
  193. #
  194. # Removal of the plugin requires you to manually delete the scoreboard.dat in the worlds
  195. # /data folder
  196. #
  197. # Enabling this can cause the scoreboard not to work anymore. Use at your own risk
  198. keep-scoreboard-quit: false
  199. # Trust or do not trust scoreboard scripts.
  200. # Normally you leave this to true
  201. # When disabled scoreboard scripts will be disabled
  202. trust-scoreboard-scripts: true
  203. # Some placeholders have a slow process behind them. Meaning they might contact a database
  204. # and take a while to 'resolve'. This will never cause lag since the placeholders are loaded
  205. # separate from the sending. But can slow down the animation because it has to wait
  206. # for the placeholder to be loaded. When having multiple lines like a text that shows
  207. # the information about the placeholders you put below it, this can cause problems.
  208. # Enabling this will output a message in the console and ingame to operators
  209. # saying when a placeholder is causing delays.
  210. detect-animation-lag: false
  211. # Putting this to true will SPAM your console with timings report per placeholder/animation
  212. # refresh. Used for debugging purposes.
  213. # This requires detect-placeholderdelay to true
  214. verbose-animation-timings: false
  215. # Show delay on join. Useful if you wish to let the user
  216. # enjoy a Title MOTD without having the scoreboard obstructing
  217. # the view.
  218. # Please note that there is a static show-delay build in of 5 ticks that you can
  219. # not change. This is because a lot of data is send in the first moment a player
  220. # joins.
  221. show-delay: 0
  222. # The update speed multiplier can increase the update speed of the scoreboard
  223. # A normal scoreboard would have a max refresh rate of 20 ticks per second
  224. # When changing this multiplier you can make this slower or faster.
  225. # Support for faster multipliers is not provided as it depends on your server
  226. # hardware if it can handle it.
  227. # This feature is mostly meant for advanced users that want to create something unique
  228. # or when stress testing.
  229. speed-multiplier: 1.0
  230. # Scoreboard script engine to use
  231. scoreboard-script-engine: "JavaScript"
  232. scoreboard-update:
  233. # Scoreboard update method
  234. # This is the method used to send the scoreboard.
  235. # ANTI_FLICKER_V1 - This method works for 1.7-1.13. It will prevent the
  236. # scoreboard lines from jumping.
  237. # This is the only supported method for Cauldron servers.
  238. # Pros:
  239. # - No flickering or jumping lines
  240. # - Fast animations
  241. # - Less packets after the scoreboard is loaded
  242. # - Static line support with ~72 characters
  243. # Cons:
  244. # - This method sends more packets when the scoreboard first loads
  245. # - Maximum of 28 characters with colors
  246. # ANTI_FLICKER_V2 - This method works for 1.9-1.13. It will prevent the
  247. # scoreboard lines from jumping.
  248. # This method is in BETA
  249. # Pros:
  250. # - No flickering or jumping lines
  251. # - Fast animations
  252. # - Full 68-70 character animations
  253. # Cons:
  254. # - More CPU/RAM usage than V1 due to frame buffer
  255. # - Scoreboards will have a delay of 3 ticks (not really noticeable)
  256. # - Does not work with Team plugins, 'especially' those that use packets
  257. #
  258. #
  259. # SWITCH_LINES - This method works for 1.7-1.13. It will reset individual
  260. # scoreboard lines that need updating. Causing jumping lines.
  261. # DISCONTINUED - NO LONGER OFFICIALLY SUPPORTED
  262. # SWITCH_OBJECTIVE - This method works for 1.9-1.13. It will swap out
  263. # the scoreboard objective. Causing flicker.
  264. # DISCONTINUED - NO LONGER OFFICIALLY SUPPORTED
  265. method: 'ANTI_FLICKER_V1'
  266. animation-update:
  267. # Animation update method
  268. # This is the method used to update the line animations
  269. # (Updating the frames, placeholders ,...)
  270. # EFFICIENT - Will update the scoreboards using X workers.
  271. # The advantage is that it makes optimal use of the
  272. # processor to update the animations.
  273. # The downside is that some placeholders
  274. # may delay the scoreboard.
  275. # Use this if you have many scoreboards
  276. # OPTIMAL - This default option will assign a dedicated worker
  277. # per scoreboard config. Lines are therefor synchronized.
  278. # If you have no idea what the other strategies do, use this
  279. # SYNCHRONOUS - This option will update all scoreboard lines of all
  280. # scoreboards in a single worker. Meaning that for many
  281. # boards this can cause delays.
  282. # Use this if you have no more than 2 different scoreboards
  283. # ASYNCHRONOUS - This option will create a task for each scoreboard line
  284. # it was default for FeatherBoard 3 and previous versions.
  285. # However it is not really optimized.
  286. method: 'OPTIMAL'
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement