Advertisement
Anston06

Config.yml

Nov 15th, 2020
141
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.06 KB | None | 0 0
  1. # --------------------------------
  2. # Geyser Configuration File
  3. #
  4. # A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
  5. #
  6. # GitHub: https://github.com/GeyserMC/Geyser
  7. # Discord: https://discord.geysermc.org/
  8. # --------------------------------
  9.  
  10. bedrock:
  11. # The IP address that will listen for connections.
  12. # There is no reason to change this unless you want to limit what IPs can connect to your server.
  13. address: 0.0.0.0
  14. # The port that will listen for connections
  15. port: 19132
  16. # Some hosting services change your Java port everytime you start the server and require the same port to be used for Bedrock.
  17. # This option makes the Bedrock port the same as the Java port every time you start the server.
  18. # This option is for the plugin version only.
  19. clone-remote-port: false
  20. # The MOTD that will be broadcasted to Minecraft: Bedrock Edition clients. This is irrelevant if "passthrough-motd" is set to true
  21. motd1: "AC Clash Bedrock Server"
  22. motd2: "Play Minecraft Survival & Mini-games"
  23. # The Server Name that will be sent to Minecraft: Bedrock Edition clients. This is visible in both the pause menu and the settings menu.
  24. server-name: "AC Clash Bedrock"
  25. remote:
  26. # The IP address of the remote (Java Edition) server
  27. # If it is "auto", for standalone version the remote address will be set to 127.0.0.1,
  28. # for plugin versions, Geyser will attempt to find the best address to connect to.
  29. address: auto
  30. # The port of the remote (Java Edition) server
  31. # For plugin versions, if address has been set to "auto", the port will also follow the server's listening port.
  32. port: 25565
  33. # Authentication type. Can be offline, online, or floodgate (see https://github.com/GeyserMC/Geyser/wiki/Floodgate).
  34. auth-type: online
  35.  
  36. # Floodgate uses encryption to ensure use from authorised sources.
  37. # This should point to the public key generated by Floodgate (Bungee or CraftBukkit)
  38. # You can ignore this when not using Floodgate.
  39. floodgate-key-file: public-key.pem
  40.  
  41. # The Xbox/Minecraft Bedrock username is the key for the Java server auth-info.
  42. # This allows automatic configuration/login to the remote Java server.
  43. # If you are brave enough to put your Mojang account info into a config file.
  44. # Uncomment the lines below to enable this feature.
  45. #userAuths:
  46. # BedrockAccountUsername: # Your Minecraft: Bedrock Edition username
  47. # email: javaccountemail@example.com # Your Minecraft: Java Edition email
  48. # password: javaccountpassword123 # Your Minecraft: Java Edition password
  49. #
  50. # bluerkelp2:
  51. # email: not_really_my_email_address_mr_minecrafter53267@gmail.com
  52. # password: "this isn't really my password"
  53.  
  54. # Bedrock clients can freeze when opening up the command prompt for the first time if given a lot of commands.
  55. # Disabling this will prevent command suggestions from being sent and solve freezing for Bedrock clients.
  56. command-suggestions: true
  57.  
  58. # The following three options enable "ping passthrough" - the MOTD, player count and/or protocol name gets retrieved from the Java server.
  59. # Relay the MOTD from the remote server to Bedrock players.
  60. passthrough-motd: false
  61. # Relay the protocol name (e.g. BungeeCord [X.X], Paper 1.X) - only really useful when using a custom protocol name!
  62. # This will also show up on sites like MCSrvStatus. <mcsrvstat.us>
  63. passthrough-protocol-name: false
  64. # Relay the player count and max players from the remote server to Bedrock players.
  65. passthrough-player-counts: false
  66. # Enable LEGACY ping passthrough. There is no need to enable this unless your MOTD or player count does not appear properly.
  67. # This option does nothing on standalone.
  68. legacy-ping-passthrough: false
  69. # How often to ping the remote server, in seconds. Only relevant for standalone or legacy ping passthrough.
  70. # Increase if you are getting BrokenPipe errors.
  71. ping-passthrough-interval: 3
  72.  
  73. # Maximum amount of players that can connect
  74. max-players: 100
  75.  
  76. # If debug messages should be sent through console
  77. debug-mode: false
  78.  
  79. # Thread pool size
  80. general-thread-pool: 32
  81.  
  82. # Allow third party capes to be visible. Currently allowing:
  83. # OptiFine capes, LabyMod capes, 5Zig capes and MinecraftCapes
  84. allow-third-party-capes: true
  85.  
  86. # Allow third party deadmau5 ears to be visible. Currently allowing:
  87. # MinecraftCapes
  88. allow-third-party-ears: false
  89.  
  90. # Allow a fake cooldown indicator to be sent. Bedrock players do not see a cooldown as they still use 1.8 combat
  91. show-cooldown: true
  92.  
  93. # The default locale if we dont have the one the client requested. Uncomment to not use the default system language.
  94. # default-locale: en_us
  95.  
  96. # Configures if chunk caching should be enabled or not. This keeps an individual
  97. # record of each block the client loads in. While this feature does allow for a few
  98. # things such as block break animations to show up in creative mode and among others,
  99. # it is HIGHLY recommended you disable this on a production environment as it can eat
  100. # up a lot of RAM. However, when using the Spigot version of Geyser, support for features
  101. # or implementations this allows is automatically enabled without the additional caching as
  102. # Geyser has direct access to the server itself.
  103. cache-chunks: false
  104.  
  105. # Specify how many days images will be cached to disk to save downloading them from the internet.
  106. # A value of 0 is disabled. (Default: 0)
  107. cache-images: 0
  108.  
  109. # Bedrock prevents building and displaying blocks above Y127 in the Nether -
  110. # enabling this config option works around that by changing the Nether dimension ID
  111. # to the End ID. The main downside to this is that the sky will resemble that of
  112. # the end sky in the nether, but ultimately it's the only way for this feature to work.
  113. above-bedrock-nether-building: false
  114.  
  115. # Force clients to load all resource packs if there are any.
  116. # If set to false it allows the user to disconnect from the server if they don't
  117. # want to download the resource packs
  118. force-resource-packs: true
  119.  
  120. # bStats is a stat tracker that is entirely anonymous and tracks only basic information
  121. # about Geyser, such as how many people are online, how many servers are using Geyser,
  122. # what OS is being used, etc. You can learn more about bStats here: https://bstats.org/.
  123. # https://bstats.org/plugin/server-implementation/GeyserMC
  124. metrics:
  125. # If metrics should be enabled
  126. enabled: true
  127. # UUID of server, don't change!
  128. uuid: 675346f8-59a6-4348-983f-a4b7733a3c88
  129.  
  130. # ADVANCED OPTIONS - DO NOT TOUCH UNLESS YOU KNOW WHAT YOU ARE DOING!
  131.  
  132. # Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
  133. # a lot of scoreboard packets per second can cause serious lag.
  134. # This option allows you to specify after how many Scoreboard packets per seconds
  135. # the Scoreboard updates will be limited to four updates per second.
  136. scoreboard-packet-threshold: 20
  137.  
  138. # Allow connections from ProxyPass and Waterdog.
  139. # See https://www.spigotmc.org/wiki/firewall-guide/ for assistance - use UDP instead of TCP.
  140. enable-proxy-connections: false
  141.  
  142. # The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
  143. # 1400 is the default.
  144. # mtu: 1400
  145.  
  146. config-version: 4
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement