Advertisement
Guest User

main-config.yml

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