Advertisement
Guest User

Bungee skungee config

a guest
Jan 3rd, 2020
1,609
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 15.11 KB | None | 0 0
  1. # Skungee (Bungeecord) - The Skript addon for Bungeecord.
  2.  
  3. # The version is to help determine which version this configuration is.
  4. # Please do not modify this value, it may result in the configuration resetting!
  5. version: "1.0.11"
  6.  
  7. # This is the main port for the Skungee network system. Skungee will setup this port on this Bungeecord machine.
  8. # Make sure the port is "port forward/open" or that you have access to this port to be running, if not change this to an available port.
  9.  
  10. # If you don't know what ports you can access, contact your hosting company and ask for some ports.
  11. # You can say "May I get some Votifier ports" to make it more clear to them, and they should give you a few ports. Normally all 4 digit ports above 1000 are available to you.
  12. # Just be advised if it doesn't work, the ports aren't avalible or are already in use.
  13.  
  14. # Make sure all the port options of the Skungee's on the connected Spigot servers are matching this.
  15. port: 1337
  16.  
  17. # You can select which address to bind to, if you're on a shared host (i.e McProHosting) you should set this value to your Bungeecord IP address.
  18. # This will allow Skungee to know which IP to attach to.
  19. bind-to-address: "localhost"
  20.  
  21. # Prints additional information in the console. The developers of Skungee may ask you to enable this when reporting an error.
  22. debug: false
  23.  
  24. # Define packets to ignore in the debug.
  25. # Developers of Skungee may notify you to add or remove packets from this list when reporting an error.
  26. debug-ignored-packets:
  27. - "HEARTBEAT"
  28. - "GLOBALSCRIPTS"
  29.  
  30. # All security options to protect your Skungee on Bungeecord and Spigot from possible external sources.
  31. # Everything in this section must match the same values as the Skungee config.yml on the Spigot servers.
  32. security:
  33. # Debug option for security, a Skungee developer may ask you to enable this.
  34. debug: false
  35. # All strings get decoded in UTF_8, some symbols may not apply.
  36. password:
  37. # Should all packets require a password in order to be processed.
  38. enabled: false
  39. # Password can't be "hashed" unless instructed too (read below)
  40. password: "insert password"
  41. # Should Skungee add a protected hash to the password using a one-way encryption.
  42. # This makes the password nearly impossible to decode if an external source somehow gets their hands on the packet.
  43. hash: true
  44. # If the hashFile option is true, set the password and then restart the server.
  45. # Skungee will create a hashed file in the Skungee folder location containing your password in a hashed format.
  46. # Keep in mind that the hash option above needs to be set to true.
  47. # After the file has been generated, set the password option above to "hashed" (Case sensitive)
  48. # Skungee will remember your original password until you change the password to anything other than "hashed" and this will be repeated.
  49. # This creates a more secure system so that if someone invades your servers files, your Skungee password is protected and all your Skungee servers aswell.
  50. # If you require any assistance with this option, please contact a Skungee developer.
  51. hashFile: false
  52. # Choose which algorithm you would like to use for the hash.
  53. # Algorithms at the time this was written: MD5, SHA-1 and SHA-256 (Strongest)
  54. hashAlgorithm: "SHA-256"
  55. encryption:
  56. # Should Skungee encrypt all sent packets.
  57. enabled: false
  58. # Set which Cipher algorithm you would like to use.
  59. cipherAlgorithm: "AES/CBC/PKCS5Padding"
  60. # The cipher key is like another password.
  61. # Must match the key placed in the Skungee Spigot config.yml
  62. cipherKey: "insert 16 length"
  63. # Should Skungee print any errors that may happen.
  64. # If you come across any errors with encryption, make sure you message the developers of Skungee, and not to users in a public setting.
  65. printEncryptionErrors: true
  66. breaches:
  67. # Breaches are even more added security, Breaches require the password or encryption option to be enabled for this to work.
  68. # Breaches is a system designed to stop constant failed attempts. Since there is no threshold for how many packets can be sent a tick, this option aims to add
  69. # security for that. If a(n) IP/Server fails X amount of times, what should Skungee do to protect your server. Choose from the options below.
  70. enabled: false
  71. # The amount of times a(n) IP/Server can fail at successfully sending security details.
  72. attempts: 30
  73. # Should Skungee shutdown the server if there is such an issue of security breaching?
  74. # Keep in mind that someone could use this to shutdown your server, this option should only be used if you really trust the security of your server
  75. # or that you have files and data that you really want to protect. We suggest not enabling it, but it's here for anyone who wants hardcore security.
  76. # This option is also good to be used if your server is private.
  77. shutdown: false
  78. # Should Skungee block the IP/Server from sending packets if it fails X amount of times?
  79. # This only blocks the IP/Server until the server is restarted again.
  80. blockAddress: true
  81. # Should Skungee log all events that meet the settings above in a `log.txt` within the Skungee folder?
  82. log: true
  83. # If the log system has picked up any external sources address, you can put it in this list below, and Skungee will remember and always block that address.
  84. # Don't include the port as they could use a different port.
  85. blacklisted:
  86. - 123.456.7.890
  87. # Makes the blacklist a whitelist instead, meaning only addresses in the list above may send packets to this server.
  88. # This option doesn't exist on the Spigot Skungee as it has a tendency to cause massive errors.
  89. blacklist-is-whitelist: false
  90.  
  91. # Disables the message saying Skungee was enabled.
  92. DisableRegisteredInfo: false
  93.  
  94. # Disables all messages to the console. Only important stack traces and information logger will be sent.
  95. # If you don't like Skungee constantly notifing what is going on, you can disable this.
  96. DisableConsoleMessages: false
  97.  
  98. # Disables the colour in the console.
  99. DisableConsoleColour: false
  100.  
  101. # Change the allowed buffer size of the server sockets accepting all the packets.
  102. # NOTE: This number must be a byte cap size. Aka divisable by 8. (512, 1024, etc)
  103. # If you have lots of allocated ram, and lots of Skungee servers, you may want to increase this.
  104. # This is in bytes. A kilobyte is 1,024 bytes, your server is usally measured in mega or giga bytes.
  105. # Anything below 16k is usally fairly accepted, above is a bit overkill. The default in Java is 8,192
  106. # Since people use Skungee on hosters (not recommended), the default is increased to 10k.
  107. buffer-size: 10240
  108.  
  109. Recievers:
  110. # How many times should Skungee try to connect to a server's reciever?
  111. allowedTrys: 10
  112.  
  113. # The system that tracks and manages when servers go online and offline. This system determines many things and here are the configurations for it.
  114. Tracker:
  115. # How many times should Skungee (Bungeecord) check before determining a server is offline.
  116. # The lower this is, the faster the syntax can determine it's offline state on the Spigot server.
  117. allowedTrys: 4
  118. # If a spigot server goes unresponsive and this is true, Skungee will stop tracking it.
  119. DisableTracking: false
  120.  
  121. # If you have scripts in the folder Bungeecord/plugins/Skungee/scripts/
  122. # Skungee will relay these scripts to all connected servers.
  123. # This acts like global scripts to keep all servers up to date.
  124. # All connected servers need to have the "Reciever" option enabled in the Skungee settings.
  125. # If you place folders within the scripts folder, they will be routed to the server that the folder is named.
  126. # Example: Bungeecord/plugins/Skungee/scripts/Hub/ will only go to the server named "Hub" aswell as any scripts in Bungeecord/plugins/Skungee/scripts/
  127. GlobalScripts:
  128. Enabled: true
  129. # Charset is the set of characters to use. If you would like symbols and such, you can adjust that setting here.
  130. # By default special symbols outside of the UTF-8 aren't supported. It's the default of your Java machine.
  131. # Charsets are by follows:
  132. # default - The default charset of this Java virtual machine.
  133. # US-ASCII - Seven-bit ASCII, a.k.a. ISO646-US, a.k.a. the Basic Latin block of the Unicode character set
  134. # ISO-8859-1 - ISO Latin Alphabet No. 1, a.k.a. ISO-LATIN-1
  135. # UTF-8 - Eight-bit UCS Transformation Format
  136. # UTF-16BE - Sixteen-bit UCS Transformation Format, big-endian byte order
  137. # UTF-16LE - Sixteen-bit UCS Transformation Format, little-endian byte order
  138. # UTF-16 - Sixteen-bit UCS Transformation Format, byte order identified by an optional byte-order mark
  139. Charset: "default"
  140.  
  141. # Bungeecord events. This also needs to be disabled on the Spigot servers if you're disabling this option.
  142. Events: true
  143.  
  144. # To be honest the "[on] bungee[[ ]cord] [server list] ping" event can be very laggy on your server, if you have a high player database Skungee will be working hard.
  145. # Everytime a user clicks the "Refresh" button in the multiplayer server list or that lists updates, this event will get called as the client is trying to get the motd.
  146. # This can add up to be alot of event calls. If you have a high core machine you may not have to worry as Skungee handles most of itself in async threads.
  147. # But this configuration node also determines the Spigot side Skungee event handler, the event is handled async and Spigot handles it back to the synced thread.
  148. # So it's up to you, you have been informed about the side effects of using this event, it may also appear slower than normal in the server list for some users.
  149. # This slowness is something that can't really be changed due to how Skungee has to work with Skript. We have tested on a 1,000 player database which is small, and it kept up.
  150. DisablePingEvent: false
  151.  
  152. # Should Skungee use the UUID's that are incoming from Spigot servers.
  153. # If you run bungeecord in offline mode for cracked players, it's best to keep this on false.
  154. # If this option is false, only the name of players will be determined.
  155.  
  156. # NOTE: Please make sure you have the option `bungeecord` set to true in the spigot.yml of all the servers connected to this bungeecord.
  157. # You also need to have the option `ip_forward` set to true in the config.yml of Bungeecord for this to work properly.
  158. IncomingUUIDs: true
  159.  
  160. NetworkVariables:
  161. # Define the storage type for the variables.
  162. # Options are: CSV (FlatFile),
  163. StorageType: CSV
  164. # Backup the variable database.
  165. # Allow variables to be re-writen if a server calls for it.
  166. AllowOverrides: true
  167. # Automatic sharing means that Skungee will try to make Skungee's (Spigot side) variables
  168. # match the exact variables that the Skungee (Bungeecord) has.
  169. # So basically if you update a global variable, Skungee will make every Spigot server variables match that.
  170. # So all you need todo is
  171. #
  172. # set network variable {test} to "Hello world!"
  173. #
  174. # Then on every other server, the variable {test} will be be set to "Hello world!"
  175. #
  176. # WARNING: Keep in mind this will override any variable names that match Skungee's.
  177. # If this is enabled Skungee variable names will be priority!
  178. # It should be harmless if you don't care about your old data.
  179. # And last thing, this is cap sensitive, can't change or fix that. That's Skript. (Has been taken into consideration and fixed in Bensku's edit)
  180. AutomaticSharing: false
  181. Backups:
  182. Enabled: true
  183. # Should Skungee send a message in the console when the variables get saved?
  184. ConsoleMessage: true
  185. # Set the backup time in minutes. (Default is 5 hours)
  186. IntervalTime: 300
  187.  
  188. # Packets can be handled, read and managed from Skungee on the Bungeecord. Just let that settle in.
  189. Packets:
  190. # Should Skungee be allowed to intercept, inject and read packets from the Minecraft clients (players)?
  191. # If this is false some syntax that rely on packets will not be registered or return nothing.
  192. # If you have errors with the packets or a developer of Skungee instructed you to, you can do so here.
  193. Enabled: true
  194.  
  195. Misc:
  196. # Whenever a message isn't set in a syntax, should Skungee grab a funny message to say to the user when kicked.
  197. # This is best used if you make a Bungeecord ban manager lol.
  198. UseFunnyKickMessages: false
  199. FunnyKickMessages:
  200. - This bungeecord server can't contain you
  201. - What are you doing in my swamp!
  202. - Don't let the door kick you on the way out!
  203. - Have a nice flight!
  204. - Hope to hear back from you soon!
  205. - Bad news Batman.
  206. - You have been kicked from the network!
  207. - Bungeecord says no, you can't be here.
  208. - You're needed elsewhere.
  209. - Someones toy's in the water hole.
  210. - You have been kicked my friend.
  211. - I hope you find a good place in our heart.
  212. - Get rekt, you have beed kicked from the network!
  213. - We were playing hot potato and you lost.
  214. - Can I get your number so I can never call again.
  215. - When was the last time you washed your hands?\nWe keep it clean around here.
  216. - Heaven sent an angel to kick you from our network.
  217. - RIP you.
  218. - RIP, you have been kicked.
  219. - You have been kicked.
  220. - An operator has kicked your hard.
  221. - Someones not your friend.
  222. - The server had an internal error with you.
  223. - I guess that was the last straw.
  224. - K\nI\nC\nK\nE\nD
  225. - Your stupidity outweighs my inteligence
  226. - The network cannot contain high levels of uglyness
  227. - System overload with too much of you.
  228. - i'd hang a medal off your ass, but my boot fits better.
  229. - common sense eludes you doesn't it.
  230. - ever had a foot in your ass? YA DO NOW!
  231. - apparently you don't learn.... do you?
  232. - how about heres my finger hes my thumb this is my boot right up yer bum.
  233. - thankyou please call again.
  234. - I'm sorry but all our operators are busy at the moment, Try again later.
  235. - that word's a no no, ya do do.
  236. - This is a beauty parlour... you appear to have hit all 27 branches on the ugly tree... there is nothing we can do for you. Try the shop next door
  237. - God loves you"...............................wait.......NO I don't.
  238. - This is Alex from Target, You're not allowed in my store!
  239. - Have a ride on the short bus?
  240. - It's along walk home so grab your coat, yopur leaving.
  241. - don't say i never gave you nothin (swift kick)\
  242. - here a early Christmas prizent.
  243. - insert own kick message cos your not worht the effort
  244. - try that one again and il wear your ass for a slipper
  245. - Get the hell of my network!
  246. - My mother gave me life, i gave her the blues, my wife gave me hell i gave her herpies, youve given me nothing so consider this a gift
  247. - Congratulations, you have been promoted to the rank kicked.
  248. - You know what gives me depression? You.
  249. - Im sorry for this inconvenience of you getting kicked, if you require help, please contact us at 1-800 I don't care..
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement