Artem1212121

Untitled

Apr 26th, 2021
82
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.46 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. # If either of these are empty, the respective string will default to "Geyser"
  22. motd1: "Geyser"
  23. motd2: "Another Geyser server."
  24. # The Server Name that will be sent to Minecraft: Bedrock Edition clients. This is visible in both the pause menu and the settings menu.
  25. server-name: "Geyser"
  26. # How much to compress network traffic to the Bedrock client. The higher the number, the more CPU usage used, but
  27. # the smaller the bandwidth used. Does not have any effect below -1 or above 9. Set to -1 to disable.
  28. compression-level: 6
  29. # Whether to enable PROXY protocol or not for clients. You DO NOT WANT this feature unless you run UDP reverse proxy
  30. # in front of your Geyser instance.
  31. enable-proxy-protocol: false
  32. # A list of allowed PROXY protocol speaking proxy IP addresses/subnets. Only effective when "enable-proxy-protocol" is enabled, and
  33. # should really only be used when you are not able to use a proper firewall (usually true with shared hosting providers etc.).
  34. # Keeping this list empty means there is no IP address whitelist.
  35. # Both IP addresses and subnets are supported.
  36. #proxy-protocol-whitelisted-ips: [ "127.0.0.1", "172.18.0.0/16" ]
  37. remote:
  38. # The IP address of the remote (Java Edition) server
  39. # If it is "auto", for standalone version the remote address will be set to 127.0.0.1,
  40. # for plugin versions, Geyser will attempt to find the best address to connect to.
  41. address: 195.201.70.92
  42. # The port of the remote (Java Edition) server
  43. # For plugin versions, if address has been set to "auto", the port will also follow the server's listening port.
  44. port: 25565
  45. # Authentication type. Can be offline, online, or floodgate (see https://github.com/GeyserMC/Geyser/wiki/Floodgate).
  46. auth-type: online
  47. # Allow for password-based authentication methods through Geyser. Only useful in online mode.
  48. # If this is false, users must authenticate to Microsoft using a code provided by Geyser on their desktop.
  49. allow-password-authentication: true
  50. # Whether to enable PROXY protocol or not while connecting to the server.
  51. # This is useful only when:
  52. # 1) Your server supports PROXY protocol (it probably doesn't)
  53. # 2) You run Velocity or BungeeCord with the option enabled in the proxy's main config.
  54. # IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
  55. use-proxy-protocol: false
  56. # Forward the hostname that the Bedrock client used to connect over to the Java server
  57. # This is designed to be used for forced hosts on proxies
  58. forward-hostname: false
  59.  
  60. # Floodgate uses encryption to ensure use from authorised sources.
  61. # This should point to the public key generated by Floodgate (Bungee or CraftBukkit)
  62. # You can ignore this when not using Floodgate.
  63. floodgate-key-file: public-key.pem
  64.  
  65. # The Xbox/Minecraft Bedrock username is the key for the Java server auth-info.
  66. # This allows automatic configuration/login to the remote Java server.
  67. # If you are brave enough to put your Mojang account info into a config file.
  68. # Uncomment the lines below to enable this feature.
  69. #userAuths:
  70. # BedrockAccountUsername: # Your Minecraft: Bedrock Edition username
  71. # email: [email protected] # Your Minecraft: Java Edition email
  72. # password: javaccountpassword123 # Your Minecraft: Java Edition password
  73. # microsoft-account: true # Whether the account is a Mojang or Microsoft account.
  74. #
  75. # bluerkelp2:
  76. # password: "this isn't really my password"
  77. # microsoft-account: false
  78.  
  79. # Bedrock clients can freeze when opening up the command prompt for the first time if given a lot of commands.
  80. # Disabling this will prevent command suggestions from being sent and solve freezing for Bedrock clients.
  81. command-suggestions: true
  82.  
  83. # The following three options enable "ping passthrough" - the MOTD, player count and/or protocol name gets retrieved from the Java server.
  84. # Relay the MOTD from the remote server to Bedrock players.
  85. passthrough-motd: false
  86. # Relay the protocol name (e.g. BungeeCord [X.X], Paper 1.X) - only really useful when using a custom protocol name!
  87. # This will also show up on sites like MCSrvStatus. <mcsrvstat.us>
  88. passthrough-protocol-name: false
  89. # Relay the player count and max players from the remote server to Bedrock players.
  90. passthrough-player-counts: false
  91. # Enable LEGACY ping passthrough. There is no need to enable this unless your MOTD or player count does not appear properly.
  92. # This option does nothing on standalone.
  93. legacy-ping-passthrough: false
  94. # How often to ping the remote server, in seconds. Only relevant for standalone or legacy ping passthrough.
  95. # Increase if you are getting BrokenPipe errors.
  96. ping-passthrough-interval: 3
  97.  
  98. # Whether to forward player ping to the server. While enabling this will allow Bedrock players to have more accurate
  99. # ping, it may also cause players to time out more easily.
  100. forward-player-ping: false
  101.  
  102. # Maximum amount of players that can connect. This is only visual at this time and does not actually limit player count.
  103. max-players: 100
  104.  
  105. # If debug messages should be sent through console
  106. debug-mode: false
  107.  
  108. # Thread pool size
  109. general-thread-pool: 32
  110.  
  111. # Allow third party capes to be visible. Currently allowing:
  112. # OptiFine capes, LabyMod capes, 5Zig capes and MinecraftCapes
  113. allow-third-party-capes: true
  114.  
  115. # Allow third party deadmau5 ears to be visible. Currently allowing:
  116. # MinecraftCapes
  117. allow-third-party-ears: false
  118.  
  119. # Allow a fake cooldown indicator to be sent. Bedrock players do not see a cooldown as they still use 1.8 combat
  120. # Can be title, actionbar or false
  121. show-cooldown: title
  122.  
  123. # Controls if coordinates are shown to players.
  124. show-coordinates: true
  125.  
  126. # The default locale if we dont have the one the client requested. Uncomment to not use the default system language.
  127. # default-locale: en_us
  128.  
  129. # Configures if chunk caching should be enabled or not. This keeps an individual
  130. # record of each block the client loads in. This feature does allow for a few things
  131. # such as more accurate movement that causes less problems with anticheat (meaning
  132. # you're less likely to be banned) and allows block break animations to show up in
  133. # creative mode (and other features). Although this increases RAM usage, it likely
  134. # won't have much of an effect for the vast majority of people. However, if you're
  135. # running out of RAM or are in a RAM-sensitive environment, you may want to disable
  136. # this. When using the Spigot version of Geyser, support for features or
  137. # implementations this allows is automatically enabled without the additional caching
  138. # as Geyser has direct access to the server itself.
  139. cache-chunks: true
  140.  
  141. # Specify how many days images will be cached to disk to save downloading them from the internet.
  142. # A value of 0 is disabled. (Default: 0)
  143. cache-images: 0
  144.  
  145. # Allows custom skulls to be displayed. Keeping them enabled may cause a performance decrease on older/weaker devices.
  146. allow-custom-skulls: true
  147.  
  148. # Whether to add (at this time, only) the furnace minecart as a separate item in the game, which normally does not exist in Bedrock Edition.
  149. # This should only need to be disabled if using a proxy that does not use the "transfer packet" style of server switching.
  150. # If this is disabled, furnace minecart items will be mapped to hopper minecart items.
  151. # This option requires a restart of Geyser in order to change its setting.
  152. add-non-bedrock-items: true
  153.  
  154. # Bedrock prevents building and displaying blocks above Y127 in the Nether -
  155. # enabling this config option works around that by changing the Nether dimension ID
  156. # to the End ID. The main downside to this is that the sky will resemble that of
  157. # the end sky in the nether, but ultimately it's the only way for this feature to work.
  158. above-bedrock-nether-building: false
  159.  
  160. # Force clients to load all resource packs if there are any.
  161. # If set to false, it allows the user to connect to the server even if they don't
  162. # want to download the resource packs.
  163. force-resource-packs: true
  164.  
  165. # Allows Xbox achievements to be unlocked.
  166. # THIS DISABLES ALL COMMANDS FROM SUCCESSFULLY RUNNING FOR BEDROCK IN-GAME, as otherwise Bedrock thinks you are cheating.
  167. xbox-achievements-enabled: false
  168.  
  169. # bStats is a stat tracker that is entirely anonymous and tracks only basic information
  170. # about Geyser, such as how many people are online, how many servers are using Geyser,
  171. # what OS is being used, etc. You can learn more about bStats here: https://bstats.org/.
  172. # https://bstats.org/plugin/server-implementation/GeyserMC
  173. metrics:
  174. # If metrics should be enabled
  175. enabled: true
  176. # UUID of server, don't change!
  177. uuid: 1eef946a-687e-4bb9-8d47-be0d012cad3a
  178.  
  179. # ADVANCED OPTIONS - DO NOT TOUCH UNLESS YOU KNOW WHAT YOU ARE DOING!
  180.  
  181. # Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
  182. # a lot of scoreboard packets per second can cause serious lag.
  183. # This option allows you to specify after how many Scoreboard packets per seconds
  184. # the Scoreboard updates will be limited to four updates per second.
  185. scoreboard-packet-threshold: 20
  186.  
  187. # Allow connections from ProxyPass and Waterdog.
  188. # See https://www.spigotmc.org/wiki/firewall-guide/ for assistance - use UDP instead of TCP.
  189. enable-proxy-connections: false
  190.  
  191. # The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
  192. # 1400 is the default.
  193. # mtu: 1400
  194.  
  195. # Whether to use direct server methods to retrieve information such as block states.
  196. # Turning this off for Spigot will stop NMS from being used but will have a performance impact.
  197. use-adapters: true
  198.  
  199. config-version: 4
  200.  
Advertisement
Add Comment
Please, Sign In to add comment