Geyser config MIA Server.

Jun 20th, 2021
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  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. # --------------------------------
  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:
  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: "MIA Sky"
  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: "M.I.A. Skyblock Survival Creative Freedom"
  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: 5
  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: [ "", "" ]
  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,
  40.   # for plugin versions, Geyser will attempt to find the best address to connect to.
  41.   address: auto
  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.
  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
  60. # Floodgate uses encryption to ensure use from authorised sources.
  61. # This should point to the public key generated by Floodgate (BungeeCord, Spigot or Velocity)
  62. # You can ignore this when not using Floodgate.
  63. floodgate-key-file: key.pem
  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: javaccountemail@example.com # 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. #    email: not_really_my_email_address_mr_minecrafter53267@gmail.com
  77. #    password: "this isn't really my password"
  78. #    microsoft-account: false
  80. # Bedrock clients can freeze when opening up the command prompt for the first time if given a lot of commands.
  81. # Disabling this will prevent command suggestions from being sent and solve freezing for Bedrock clients.
  82. command-suggestions: true
  84. # The following three options enable "ping passthrough" - the MOTD, player count and/or protocol name gets retrieved from the Java server.
  85. # Relay the MOTD from the remote server to Bedrock players.
  86. passthrough-motd: true
  87. # Relay the protocol name (e.g. BungeeCord [X.X], Paper 1.X) - only really useful when using a custom protocol name!
  88. # This will also show up on sites like MCSrvStatus. <mcsrvstat.us>
  89. passthrough-protocol-name: false
  90. # Relay the player count and max players from the remote server to Bedrock players.
  91. passthrough-player-counts: false
  92. # Enable LEGACY ping passthrough. There is no need to enable this unless your MOTD or player count does not appear properly.
  93. # This option does nothing on standalone.
  94. legacy-ping-passthrough: false
  95. # How often to ping the remote server, in seconds. Only relevant for standalone or legacy ping passthrough.
  96. # Increase if you are getting BrokenPipe errors.
  97. ping-passthrough-interval: 3
  99. # Whether to forward player ping to the server. While enabling this will allow Bedrock players to have more accurate
  100. # ping, it may also cause players to time out more easily.
  101. forward-player-ping: false
  103. # Maximum amount of players that can connect. This is only visual at this time and does not actually limit player count.
  104. max-players: 200
  106. # If debug messages should be sent through console
  107. debug-mode: false
  109. # Thread pool size
  110. general-thread-pool: 32
  112. # Allow third party capes to be visible. Currently allowing:
  113. # OptiFine capes, LabyMod capes, 5Zig capes and MinecraftCapes
  114. allow-third-party-capes: true
  116. # Allow third party deadmau5 ears to be visible. Currently allowing:
  117. # MinecraftCapes
  118. allow-third-party-ears: false
  120. # Allow a fake cooldown indicator to be sent. Bedrock players do not see a cooldown as they still use 1.8 combat
  121. # Can be title, actionbar or false
  122. show-cooldown: title
  124. # Controls if coordinates are shown to players.
  125. show-coordinates: true
  127. # If set, when a Bedrock player performs any emote, it will swap the offhand and mainhand items, just like the Java Edition keybind
  128. # There are three options this can be set to:
  129. # disabled - the default/fallback, which doesn't apply this workaround
  130. # no-emotes - emotes will NOT be sent to other Bedrock clients and offhand will be swapped. This effectively disables all emotes from being seen.
  131. # emotes-and-offhand - emotes will be sent to Bedrock clients and offhand will be swapped
  132. emote-offhand-workaround: "disabled"
  134. # The default locale if we dont have the one the client requested. Uncomment to not use the default system language.
  135. # default-locale: en_us
  137. # Specify how many days images will be cached to disk to save downloading them from the internet.
  138. # A value of 0 is disabled. (Default: 0)
  139. cache-images: 0
  141. # Allows custom skulls to be displayed. Keeping them enabled may cause a performance decrease on older/weaker devices.
  142. allow-custom-skulls: true
  144. # 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.
  145. # This should only need to be disabled if using a proxy that does not use the "transfer packet" style of server switching.
  146. # If this is disabled, furnace minecart items will be mapped to hopper minecart items.
  147. # This option requires a restart of Geyser in order to change its setting.
  148. add-non-bedrock-items: true
  150. # Bedrock prevents building and displaying blocks above Y127 in the Nether -
  151. # enabling this config option works around that by changing the Nether dimension ID
  152. # to the End ID. The main downside to this is that the sky will resemble that of
  153. # the end sky in the nether, but ultimately it's the only way for this feature to work.
  154. above-bedrock-nether-building: false
  156. # Force clients to load all resource packs if there are any.
  157. # If set to false, it allows the user to connect to the server even if they don't
  158. # want to download the resource packs.
  159. force-resource-packs: false
  161. # Allows Xbox achievements to be unlocked.
  162. # THIS DISABLES ALL COMMANDS FROM SUCCESSFULLY RUNNING FOR BEDROCK IN-GAME, as otherwise Bedrock thinks you are cheating.
  163. xbox-achievements-enabled: false
  165. # bStats is a stat tracker that is entirely anonymous and tracks only basic information
  166. # about Geyser, such as how many people are online, how many servers are using Geyser,
  167. # what OS is being used, etc. You can learn more about bStats here: https://bstats.org/.
  168. # https://bstats.org/plugin/server-implementation/GeyserMC
  169. metrics:
  170.  # If metrics should be enabled
  171.   enabled: true
  172.   # UUID of server, don't change!
  173.   uuid: f58c614a-beac-4ae4-94a1-086fb4f5122d
  177. # Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
  178. # a lot of scoreboard packets per second can cause serious lag.
  179. # This option allows you to specify after how many Scoreboard packets per seconds
  180. # the Scoreboard updates will be limited to four updates per second.
  181. scoreboard-packet-threshold: 20
  183. # Allow connections from ProxyPass and Waterdog.
  184. # See https://www.spigotmc.org/wiki/firewall-guide/ for assistance - use UDP instead of TCP.
  185. enable-proxy-connections: false
  187. # The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
  188. # 1400 is the default.
  189. # mtu: 1400
  191. # Whether to use direct server methods to retrieve information such as block states.
  192. # Turning this off for Spigot will stop NMS from being used but will have a performance impact.
  193. use-adapters: true
  195. config-version: 4
RAW Paste Data