Guest User

Untitled

a guest
Feb 3rd, 2023
110
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 12.95 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.gg/geysermc
  8. # --------------------------------
  9.  
  10. bedrock:
  11. # The IP address that will listen for connections.
  12. # Generally, you should only uncomment and change this if 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, it is recommended to keep this as "auto" so Geyser will automatically configure address, port, and auth-type.
  41. # Leave as "auto" if floodgate is installed.
  42. address: auto
  43. # The port of the remote (Java Edition) server
  44. # For plugin versions, if address has been set to "auto", the port will also follow the server's listening port.
  45. port: 19132
  46. # Authentication type. Can be offline, online, or floodgate (see https://github.com/GeyserMC/Geyser/wiki/Floodgate).
  47. # For plugin versions, it's recommended to keep the `address` field to "auto" so Floodgate support is automatically configured.
  48. # If Floodgate is installed and `address:` is set to "auto", then "auth-type: floodgate" will automatically be used.
  49. auth-type: floodgate
  50. # Allow for password-based authentication methods through Geyser. Only useful in online mode.
  51. # If this is false, users must authenticate to Microsoft using a code provided by Geyser on their desktop.
  52. allow-password-authentication: true
  53. # Whether to enable PROXY protocol or not while connecting to the server.
  54. # This is useful only when:
  55. # 1) Your server supports PROXY protocol (it probably doesn't)
  56. # 2) You run Velocity or BungeeCord with the option enabled in the proxy's main config.
  57. # IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
  58. use-proxy-protocol: false
  59. # Forward the hostname that the Bedrock client used to connect over to the Java server
  60. # This is designed to be used for forced hosts on proxies
  61. forward-hostname: false
  62.  
  63. # Floodgate uses encryption to ensure use from authorised sources.
  64. # This should point to the public key generated by Floodgate (BungeeCord, Spigot or Velocity)
  65. # You can ignore this when not using Floodgate.
  66. # If you're using a plugin version of Floodgate on the same server, the key will automatically be picked up from Floodgate.
  67. floodgate-key-file: key.pem
  68.  
  69. # For online mode authentication type only.
  70. # Stores a list of Bedrock players that should have their Java Edition account saved after login.
  71. # This saves a token that can be reused to authenticate the player later. This does not save emails or passwords,
  72. # but you should still be cautious when adding to this list and giving others access to this Geyser instance's files.
  73. # Removing a name from this list will delete its cached login information on the next Geyser startup.
  74. # The file that tokens will be saved in is in the same folder as this config, named "saved-refresh-tokens.json".
  75. saved-user-logins:
  76. - ThisExampleUsernameShouldBeLongEnoughToNeverBeAnXboxUsername
  77. - ThisOtherExampleUsernameShouldAlsoBeLongEnough
  78.  
  79. # Specify how many seconds to wait while user authorizes Geyser to access their Microsoft account.
  80. # User is allowed to disconnect from the server during this period.
  81. pending-authentication-timeout: 120
  82.  
  83. # Bedrock clients can freeze when opening up the command prompt for the first time if given a lot of commands.
  84. # Disabling this will prevent command suggestions from being sent and solve freezing for Bedrock clients.
  85. command-suggestions: true
  86.  
  87. # The following three options enable "ping passthrough" - the MOTD, player count and/or protocol name gets retrieved from the Java server.
  88. # Relay the MOTD from the remote server to Bedrock players.
  89. passthrough-motd: false
  90. # Relay the protocol name (e.g. BungeeCord [X.X], Paper 1.X) - only really useful when using a custom protocol name!
  91. # This will also show up on sites like MCSrvStatus. <mcsrvstat.us>
  92. passthrough-protocol-name: false
  93. # Relay the player count and max players from the remote server to Bedrock players.
  94. passthrough-player-counts: false
  95. # Enable LEGACY ping passthrough. There is no need to enable this unless your MOTD or player count does not appear properly.
  96. # This option does nothing on standalone.
  97. legacy-ping-passthrough: false
  98. # How often to ping the remote server, in seconds. Only relevant for standalone or legacy ping passthrough.
  99. # Increase if you are getting BrokenPipe errors.
  100. ping-passthrough-interval: 3
  101.  
  102. # Whether to forward player ping to the server. While enabling this will allow Bedrock players to have more accurate
  103. # ping, it may also cause players to time out more easily.
  104. forward-player-ping: false
  105.  
  106. # Maximum amount of players that can connect. This is only visual at this time and does not actually limit player count.
  107. max-players: 100
  108.  
  109. # If debug messages should be sent through console
  110. debug-mode: false
  111.  
  112. # Allow third party capes to be visible. Currently allowing:
  113. # OptiFine capes, LabyMod capes, 5Zig capes and MinecraftCapes
  114. allow-third-party-capes: false
  115.  
  116. # Allow third party deadmau5 ears to be visible. Currently allowing:
  117. # MinecraftCapes
  118. allow-third-party-ears: false
  119.  
  120. # Allow a fake cooldown indicator to be sent. Bedrock players otherwise do not see a cooldown as they still use 1.8 combat.
  121. # Please note: if the cooldown is enabled, some users may see a black box during the cooldown sequence, like below:
  122. # https://cdn.discordapp.com/attachments/613170125696270357/957075682230419466/Screenshot_from_2022-03-25_20-35-08.png
  123. # This can be disabled by going into Bedrock settings under the accessibility tab and setting "Text Background Opacity" to 0
  124. # This setting can be set to "title", "actionbar" or "false"
  125. show-cooldown: title
  126.  
  127. # Controls if coordinates are shown to players.
  128. show-coordinates: true
  129.  
  130. # Whether Bedrock players are blocked from performing their scaffolding-style bridging.
  131. disable-bedrock-scaffolding: false
  132.  
  133. # Whether Bedrock players can right-click outside of their inventory to replace armor in their inventory, even if the
  134. # armor slot is already occupied (which Java Edition doesn't allow)
  135. always-quick-change-armor: false
  136.  
  137. # If set, when a Bedrock player performs any emote, it will swap the offhand and mainhand items, just like the Java Edition keybind
  138. # There are three options this can be set to:
  139. # disabled - the default/fallback, which doesn't apply this workaround
  140. # no-emotes - emotes will NOT be sent to other Bedrock clients and offhand will be swapped. This effectively disables all emotes from being seen.
  141. # emotes-and-offhand - emotes will be sent to Bedrock clients and offhand will be swapped
  142. emote-offhand-workaround: "disabled"
  143.  
  144. # The default locale if we dont have the one the client requested. Uncomment to not use the default system language.
  145. # default-locale: en_us
  146.  
  147. # Specify how many days images will be cached to disk to save downloading them from the internet.
  148. # A value of 0 is disabled. (Default: 0)
  149. cache-images: 0
  150.  
  151. # Allows custom skulls to be displayed. Keeping them enabled may cause a performance decrease on older/weaker devices.
  152. allow-custom-skulls: true
  153.  
  154. # The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
  155. # Setting this to -1 will cause all custom skulls to be displayed regardless of distance or number.
  156. max-visible-custom-skulls: 128
  157.  
  158. # The radius in blocks around the player in which custom skulls are displayed.
  159. custom-skull-render-distance: 32
  160.  
  161. # 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.
  162. # This should only need to be disabled if using a proxy that does not use the "transfer packet" style of server switching.
  163. # If this is disabled, furnace minecart items will be mapped to hopper minecart items.
  164. # This option requires a restart of Geyser in order to change its setting.
  165. add-non-bedrock-items: true
  166.  
  167. # Bedrock prevents building and displaying blocks above Y127 in the Nether.
  168. # This config option works around that by changing the Nether dimension ID to the End ID.
  169. # The main downside to this is that the entire Nether will have the same red fog rather than having different fog for each biome.
  170. above-bedrock-nether-building: false
  171.  
  172. # Force clients to load all resource packs if there are any.
  173. # If set to false, it allows the user to connect to the server even if they don't
  174. # want to download the resource packs.
  175. force-resource-packs: true
  176.  
  177. # Allows Xbox achievements to be unlocked.
  178. # THIS DISABLES ALL COMMANDS FROM SUCCESSFULLY RUNNING FOR BEDROCK IN-GAME, as otherwise Bedrock thinks you are cheating.
  179. xbox-achievements-enabled: false
  180.  
  181. # Whether player IP addresses will be logged by the server.
  182. log-player-ip-addresses: true
  183.  
  184. # Whether to alert the console and operators that a new Geyser version is available that supports a Bedrock version
  185. # that this Geyser version does not support. It's recommended to keep this option enabled, as many Bedrock platforms
  186. # auto-update.
  187. notify-on-new-bedrock-update: true
  188.  
  189. # Which item to use to mark unavailable slots in a Bedrock player inventory. Examples of this are the 2x2 crafting grid while in creative,
  190. # or custom inventory menus with sizes different from the usual 3x9. A barrier block is the default item.
  191. unusable-space-block: minecraft:barrier
  192.  
  193. # bStats is a stat tracker that is entirely anonymous and tracks only basic information
  194. # about Geyser, such as how many people are online, how many servers are using Geyser,
  195. # what OS is being used, etc. You can learn more about bStats here: https://bstats.org/.
  196. # https://bstats.org/plugin/server-implementation/GeyserMC
  197. metrics:
  198. # If metrics should be enabled
  199. enabled: true
  200. # UUID of server, don't change!
  201. uuid: 31f3179d-9b95-4247-a58d-725f90798159
  202.  
  203. # ADVANCED OPTIONS - DO NOT TOUCH UNLESS YOU KNOW WHAT YOU ARE DOING!
  204.  
  205. # Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
  206. # a lot of scoreboard packets per second can cause serious lag.
  207. # This option allows you to specify after how many Scoreboard packets per seconds
  208. # the Scoreboard updates will be limited to four updates per second.
  209. scoreboard-packet-threshold: 20
  210.  
  211. # Allow connections from ProxyPass and Waterdog.
  212. # See https://www.spigotmc.org/wiki/firewall-guide/ for assistance - use UDP instead of TCP.
  213. enable-proxy-connections: false
  214.  
  215. # The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
  216. # 1400 is the default.
  217. mtu: 1400
  218.  
  219. # Whether to connect directly into the Java server without creating a TCP connection.
  220. # This should only be disabled if a plugin that interfaces with packets or the network does not work correctly with Geyser.
  221. # If enabled on plugin versions, the remote address and port sections are ignored
  222. # If disabled on plugin versions, expect performance decrease and latency increase
  223. use-direct-connection: true
  224.  
  225. # Whether Geyser should attempt to disable compression for Bedrock players. This should be a benefit as there is no need to compress data
  226. # when Java packets aren't being handled over the network.
  227. # This requires use-direct-connection to be true.
  228. disable-compression: true
  229.  
  230. config-version: 4
  231.  
Add Comment
Please, Sign In to add comment