Advertisement
Guest User

Untitled

a guest
Aug 9th, 2017
106
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 13.26 KB | None | 0 0
  1. # This is the configuration version. Unless you really want to mess up your
  2. # configuration, you should not change this.
  3. config-version: 2
  4.  
  5. # Whether or not to enable debug mode. In debug mode, SkyWars will print a
  6. # huge amount of information to the server console. There is usually no need
  7. # to enable this unless you are asked to by the developer.
  8. debug: false
  9.  
  10. # When enabled, SkyWars will report statistics to https://dabo.guru, using the
  11. # custom "plugin-statistics" system. This is similar to PluginMetrics/MCStats,
  12. # but reports vastly less data, and does not use any persistent GUID for the
  13. # server.
  14. #
  15. # If enabled, every hour, starting one hour from server startup, the plugin
  16. # will send the plugin version, server version, online player count, and an
  17. # instance UUID to https://dabo.guru/statistics/skywars/. The instance UUID is
  18. # reset every server startup, and is not stored in any persistent files.
  19. #
  20. # If disabled, no data will be sent.
  21. #
  22. # For more information, see https://github.com/daboross/plugin-statistics.
  23. report-statistics: true
  24.  
  25. # This represents the order that the arenas are started in. Whenever enough
  26. # people join the queue, a new arena is chosen either at RANDOM, or ORDERED.
  27. #
  28. # Setting this value to RANDOM will make a random arena be chosen from
  29. # enabled-arenas when a new game starts. Setting it to ORDERED will make each
  30. # enabled arena be started in sequence.
  31. arena-order: RANDOM
  32.  
  33. # This is the string that will prefix all SkyWars announcements.
  34. message-prefix: '&8[&cSkyWars&8]&a '
  35.  
  36. # Whether or not to save inventories of players who are joining SkyWars games.
  37. #
  38. # When this is false, each player's inventory will be wiped when the join a
  39. # game and when the leave a game. When this is true the inventory is stored in
  40. # memory and then wiped when the join a game, then restored when they leave.
  41. #
  42. # Note that if the server crashes when games are running, or SkyWars is
  43. # forcefully stopped, the inventories of the players in any game running at
  44. # that time will not be recoverable.
  45. save-inventory: true
  46.  
  47. # Whether or not experience level will be saved along with inventory.
  48. #
  49. # This won't work without save-inventory also being true. See save-inventory
  50. # for more information.
  51. save-experience: true
  52.  
  53. # Whether or not position, gamemode, health, hunger, and other survival player
  54. # properties are saved when joining a SkyWars games (and restored upon leaving).
  55. #
  56. # This will teleport players back to their original locations, instead of
  57. # going to a lobby when finished - and will restore their gamemode, health,
  58. # hunger, exhaustion and stamina. This won't work without save-inventory also
  59. # being true.
  60. #
  61. # If this is false, players are teleported to the lobby, and only their
  62. # inventory (and experience) are restored. If false, gamemode, health and
  63. # hunger are completely reset upon leaving a game.
  64. save-position-gamemode-health: true
  65.  
  66. # A list of enabled arenas. Each of the items in this list corresponds to a
  67. # file in the arenas/ folder. When SkyWars loads, it will take each item in
  68. # this list, look for a file in the arenas/ folder who's name is this followed
  69. # by '.yml', then load it into the enabled arenas list.
  70. enabled-arenas:
  71. - skyblock-warriors
  72. - water-warriors
  73. - Skyblock1
  74.  
  75. # Locale to use for all player messages. Currently available locales:
  76. # cz, de, dk, en, es, fr, nl, pl, pt and ru.
  77. # Note that some translations are incomplete. You can also modify
  78. # `messages.yml` to make your own translation (if you do, be sure to set
  79. # auto-update to false in messages.yml).
  80. locale: en
  81.  
  82. # A list of minecraft gamerules to set in the world where arenas are run. By
  83. # default, only 'doDaylightCycle' is set - this stops day and night from
  84. # changing in the arena world.
  85. skywars-arena-gamerules:
  86. doDaylightCycle: 'false'
  87.  
  88. # Whether or not players should be immediately respawned after dying. If true,
  89. # the death/respawn screen is skipped and players are teleported immediately
  90. # after dying. If false, players will have the respawn screen shown as normal.
  91. # When false, players will still be force respawned when the game ends if they
  92. # haven't clicked the respawn button by then.
  93. skip-respawn-screen: true
  94.  
  95. # Sub section for score storage
  96. points:
  97.  
  98. # Whether to enable point storage or not. If point storage is not enabled,
  99. # none of the following settings will take effect
  100. enable-points: true
  101.  
  102. # The number of points to add to a player's score when they win a game.
  103. win-point-diff: 7
  104.  
  105. # The number of points to add to a player's score when they die in a game.
  106. death-point-diff: -2
  107.  
  108. # The number of points to add to a player's score when they kill someone in
  109. # a game
  110. kill-point-diff: 1
  111.  
  112. # Number of seconds between saving the score to hard disk
  113. # In JSON storage, this is the number of seconds between saving the entire
  114. # score file to the hard disk.
  115. #
  116. # In SQL storage, this is the number of seconds between saving only
  117. # uncommitted data to the SQL server. In SQL, this is also the number of
  118. # seconds between leaderboard updates.
  119. #
  120. # Recommended to be set to values 10-30 if using SQL. 200-500 for JSON.
  121. max-save-interval: 300
  122.  
  123. # If true, use the SQL storage backend. If false, the JSON storage is used.
  124. #
  125. # Note: When using SQL backend, for most efficiency, set max-save-interval
  126. # to 20 SQL saving works differently than json saving, so max-save-interval
  127. # values from 20-100 seconds work best.
  128. use-sql: true
  129.  
  130. # SQL login info
  131. sql:
  132. # Host to connect to
  133. host: 127.0.0.1
  134. # Port to connect to
  135. port: 3306
  136. # Database to store on. Data is stored in a `skywars_user` table in this
  137. # database.
  138. database: minecraft
  139. # Username to login as. Using `root` is not recommended. Instead you
  140. # should set up a more restricted user.
  141. username: root
  142. # Password to login with.
  143. password: aComplexPassword
  144.  
  145. # Time in seconds between updating the ranks of each individual. This is
  146. # the rank shown in `/sw rank`, and this will update the ranks of everyone
  147. # on the server at the given interval. However, updating each individual's
  148. # rank is a more costly operation than updating the top 10 ranks, so it is
  149. # done on a separate timer. (top 10 ranks are updated according to
  150. # max-save-interval).
  151. individual-rank-update-interval: 120
  152.  
  153. # Subsection for the economy Vault hook
  154. economy:
  155.  
  156. # Whether or not to enable hooking into Vault for economy.
  157. # If disabled, no rewards will be given, and kits with costs will also be
  158. # disabled.
  159. enable-economy: true
  160.  
  161. # Amount of money to give a player when they kill someone in a game.
  162. kill-reward: 10
  163.  
  164. # Amount of money to give s player when they win a game.
  165. win-reward: 10
  166.  
  167. # Whether or not to tell players when they get a win reward.
  168. reward-messages: true
  169.  
  170. # The distance apart arenas will be in the SkyWarsArenaWorld. If you have
  171. # created bigger arenas, such as ones that are bigger than 100 blocks, you may
  172. # want to increase this value.
  173. #
  174. # Note that this is the distance from the center of one arena to the center of
  175. # the next, not the inner edges.
  176. arena-distance-apart: 200
  177.  
  178. arena-copying:
  179. # If a multi-operation arena copy is enabled, this will be how many blocks
  180. # each copy operation copies. If you feel that SkyWars is causing your server
  181. # lag on game start and game end, adjusting this value and/or
  182. # time-before-start-to-start-arena-copy-operation may help.
  183. number-of-blocks-to-copy-at-once: 500
  184.  
  185. # Command whitelist sub-section
  186. command-whitelist:
  187.  
  188. # Whether or not to enable the command whitelist. If enabled, commands use
  189. # will be restricted when in a game.
  190. whitelist-enabled: true
  191.  
  192. # If true, treat the values in `whitelist` as a blacklist, blocking them and
  193. # only them in game.
  194. # If false, treat the values in `whitelist` as a whitelist, blocking all
  195. # commands *except them* in game.
  196. treated-as-blacklist: false
  197.  
  198. # Commands to whitelist/blacklist in game
  199. whitelist:
  200. - /skywars
  201. - /sw
  202. - /me
  203.  
  204. # Join sign appearance
  205. #
  206. # When the queue length changes or a game is started, every sign is updated
  207. # with "{name}" set to the next arena's name, "{count}" set to the number of
  208. # players in the queue, and "{max}" set to the maximum number of players to
  209. # join the arena before SkyWars will start the game.
  210. #
  211. # This must be a list of four lines used for the four lines on the sign. If you
  212. # want less than four lines, simply have the last lines be blank.
  213. #
  214. # When placing a sign, the sign will turn into a SkyWars Join Sign if the first
  215. # "static" line of the template matches. "static" in this case means there are
  216. # no changing elements such as "{name}", "{count}" and "{max}".
  217. #
  218. # For example, if you have the following configuration:
  219. # join-sign-lines:
  220. # - 'Players: {count}'
  221. # - 'Arena: {name}'
  222. # - 'Waiting for: {max}'
  223. # - 'Click to join!'
  224. #
  225. # Then in order to create a join sign, you would have to write a sign with the
  226. # first three lines blank, and the last line with "Click to join!" in it.
  227. #
  228. # With the default configuration, simply make a sign with the first line being
  229. # "[SkyWars]" and it will turn into a join sign.
  230. #
  231. # NOTE! When you change this setting, all currently existing join signs will
  232. # no longer function or update - SkyWars uses the lines in this setting to
  233. # tell which signs are still join signs when updating. (all signs are also
  234. # stored in locations.yml, but SkyWars double-checks them with the join sign
  235. # line format to avoid overwriting changed signs).
  236. join-sign-lines:
  237. - '&8[&cSkyWars&8]'
  238. - '&8Next Game: &c{name}'
  239. - '&8Players: &2{count}&3/&2{max}'
  240. - '&cClick to join!'
  241.  
  242. # Message limiting - only broadcasting some messages to players who are
  243. # involved in the game the message is about.
  244. only-broadcast-to-players-in-arena:
  245. # If true, game starting messages will only be shown to those in the game
  246. # which is starting.
  247. start: false
  248. # If true, death messages of players in a game will only be shown to alive
  249. # players in that game.
  250. death: true
  251. # If true, end/winning messages for games will only be shown to the
  252. # player(s) who won the game, and the last player who died.
  253. end: false
  254. # If true, "start timer" messages will only be shown to to the players who
  255. # are already in the arena queue.
  256. starting-in-start-timer: false
  257.  
  258. # Kit GUI subsection
  259. kit-gui:
  260. # The Kit GUI is an visual "inventory" menu shown which contains one "totem"
  261. # item per kit.
  262.  
  263. # If true, kits unavailable to the player (either due to lack of permission
  264. # or lack of funds) will be shown in the bottom of the kit GUI, with a
  265. # 9-space row separating them from the available kits.
  266. show-unavailable-kits: true
  267.  
  268. # By default, the kit GUI is accessible via a command: `/sw kitgui`. If this
  269. # is enabled, the `kitgui` command will no longer exist, and `/sw kit` will
  270. # launch the kit GUI rather than show a list of kits available.
  271. replace-kit-command: false
  272.  
  273. # If this is true, the kit GUI will be launched (shown to the player)
  274. # whenever the player joins the queue or clicks a join sign. Note that the
  275. # GUI will be shown even if the player is already in the queue: if this is
  276. # enabled, join signs can also be used as a "kit sign" which launches the
  277. # kit GUI when clicked.
  278. auto-show-on-join: true
  279.  
  280. # Settings related to the game timer, the SkyWars start timer.
  281. # All sub-settings under 'game-timer' are in seconds
  282. game-timer:
  283. # Time before the game starts after the maximum number of players have joined.
  284. time-till-start-after-max-join: 30
  285. # Time before the game starts after the minimum number of players have joined.
  286. time-till-start-after-any-join: 200
  287. # Time before the game starts to start copying the arena, in preparation of the game starting.
  288. time-before-start-to-start-arena-copy-operation: 45
  289. # Currently unused. In the future, this will be how long after players are teleported into the arena before they are
  290. # allowed to move.
  291. time-after-start-to-freeze-players: 5
  292. # This is a list of times, in seconds, to broadcast "game starting in X minutes/seconds" messages.
  293. #
  294. # Each of these times is in seconds before the game starts.
  295. #
  296. # For each time, if the time is divisible by 60, the message will be displayed as "start in X minutes". If it isn't,
  297. # the message will be "starting in X seconds."
  298. times-to-message-before-start:
  299. - 600
  300. - 300
  301. - 180
  302. - 60
  303. - 45
  304. - 30
  305. - 15
  306. - 5
  307. - 3
  308. - 2
  309. - 1
  310.  
  311. # Hooks available to hook into separate plugins
  312. hooks:
  313. # This hook is supposed to be for hooking into the Multiverse plugin, but it
  314. # has not yet been added. This setting has no effect.
  315. multiverse-core-hook: false
  316.  
  317. # This toggles the WorldEdit hook. SkyWars supports starting arenas both
  318. # using an integrated Bukkit method, and a faster WorldEdit method.
  319. #
  320. # If this is true, and the WorldEdit plugin is enabled on the server,
  321. # WorldEdit will be used to copy arena blocks.
  322. #
  323. # If this is false, or the WorldEdit plugin is not installed, the integrated
  324. # Bukkit method will be used to copy arena blocks.
  325. #
  326. # Note that if the WorldEdit hook is enabled, and WorldEdit is installed,
  327. # SkyWars depends on WorldEdit being up-to-date to work correctly. If
  328. # WorldEdit is out of date, arenas will not be copied correctly.
  329. worldedit-hook: false
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement