-
Bug
-
Resolution: Invalid
-
Minor
-
None
-
None
-
None
-
Hello, assuming a specific ip with a port for GeyserMC, but this error came up
-
1.19.4
-
GeyserMC
-
Yes
Error:
[18:13:37] [ServerMain/INFO]: Loaded 7 recipes
[18:13:35] [ServerMain/INFO]: Environment: authHost='https://authserver.mojang.com', accountsHost='https://api.mojang.com', sessionHost='https://sessionserver.mojang.com', servicesHost='https://api.minecraftservices.com', name='PROD'
[18:13:37] [ServerMain/INFO]: Loaded 7 recipes
[18:13:37] [Server thread/INFO]: Starting minecraft server version 1.19.4
[18:13:37] [Server thread/INFO]: Loading properties
[18:13:38] [Server thread/INFO]: This server is running CraftBukkit version 3748-Spigot-7da74da-01b2e1a (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT)
[18:13:38] [Server thread/INFO]: Debug logging is disabled
[18:13:38] [Server thread/INFO]: Server Ping Player Sample Count: 12
[18:13:38] [Server thread/INFO]: Using 4 threads for Netty based IO
[18:13:38] [Server thread/INFO]: Default game type: SURVIVAL
[18:13:38] [Server thread/INFO]: Generating keypair
[18:13:38] [Server thread/INFO]: Starting Minecraft server on 0.0.0.0:25958
[18:13:38] [Server thread/INFO]: Using epoll channel type
[18:13:38] [Server thread/INFO]: [floodgate] Loading floodgate v2.2.2-SNAPSHOT (b??-1b9042e)
[18:13:39] [Server thread/WARN]: [floodgate] en_ is not a supported Floodgate language.
[18:13:39] [Server thread/INFO]: [floodgate] Took 390ms to boot Floodgate
[18:13:39] [Server thread/INFO]: [Geyser-Spigot] Loading Geyser-Spigot v2.1.0-SNAPSHOT
[18:13:39] [Server thread/INFO]: [Geyser-Spigot] Loading extensions...
[18:13:39] [Server thread/INFO]: [Geyser-Spigot] Loaded 0 extension(s)
[18:13:39] [Server thread/WARN]: **** SERVER IS RUNNING IN OFFLINE/INSECURE MODE!
[18:13:39] [Server thread/WARN]: The server will make no attempt to authenticate usernames. Beware.
[18:13:39] [Server thread/WARN]: While this makes the game possible to play without internet access, it also opens up the ability for hackers to connect with any username they choose.
[18:13:39] [Server thread/WARN]: To change this, set "online-mode" to "true" in the server.properties file.
[18:13:39] [Server thread/INFO]: Preparing level "world"
[18:13:41] [Server thread/INFO]: Preparing start region for dimension minecraft:overworld
[18:13:47] [Worker-Main-3/INFO]: Preparing spawn area: 0%
[18:13:47] [Worker-Main-1/INFO]: Preparing spawn area: 0%
[18:13:47] [Worker-Main-3/INFO]: Preparing spawn area: 0%
[18:13:47] [Worker-Main-1/INFO]: Preparing spawn area: 0%
[18:13:47] [Worker-Main-3/INFO]: Preparing spawn area: 0%
[18:13:47] [Worker-Main-3/INFO]: Preparing spawn area: 0%
[18:13:47] [Worker-Main-2/INFO]: Preparing spawn area: 0%
[18:13:47] [Worker-Main-1/INFO]: Preparing spawn area: 0%
[18:13:47] [Worker-Main-3/INFO]: Preparing spawn area: 0%
[18:13:47] [Worker-Main-1/INFO]: Preparing spawn area: 0%
[18:13:47] [Worker-Main-2/INFO]: Preparing spawn area: 0%
[18:13:47] [Worker-Main-2/INFO]: Preparing spawn area: 9%
[18:13:47] [Worker-Main-1/INFO]: Preparing spawn area: 38%
[18:13:48] [Server thread/INFO]: Time elapsed: 6510 ms
[18:13:48] [Server thread/INFO]: Preparing start region for dimension minecraft:the_nether
[18:13:53] [Worker-Main-2/INFO]: Preparing spawn area: 0%
[18:13:53] [Worker-Main-1/INFO]: Preparing spawn area: 0%
[18:13:53] [Worker-Main-3/INFO]: Preparing spawn area: 0%
[18:13:53] [Worker-Main-3/INFO]: Preparing spawn area: 0%
[18:13:53] [Worker-Main-3/INFO]: Preparing spawn area: 0%
[18:13:53] [Worker-Main-1/INFO]: Preparing spawn area: 0%
[18:13:53] [Worker-Main-2/INFO]: Preparing spawn area: 0%
[18:13:53] [Worker-Main-1/INFO]: Preparing spawn area: 0%
[18:13:53] [Worker-Main-1/INFO]: Preparing spawn area: 0%
[18:13:53] [Worker-Main-1/INFO]: Preparing spawn area: 0%
[18:13:53] [Worker-Main-3/INFO]: Preparing spawn area: 0%
[18:13:54] [Worker-Main-1/INFO]: Preparing spawn area: 44%
[18:13:54] [Server thread/INFO]: Time elapsed: 5900 ms
[18:13:54] [Server thread/INFO]: Preparing start region for dimension minecraft:the_end
[18:13:56] [Worker-Main-1/INFO]: Preparing spawn area: 0%
[18:13:56] [Worker-Main-2/INFO]: Preparing spawn area: 0%
[18:13:56] [Worker-Main-1/INFO]: Preparing spawn area: 0%
[18:13:56] [Worker-Main-1/INFO]: Preparing spawn area: 0%
[18:13:56] [Worker-Main-2/INFO]: Preparing spawn area: 0%
[18:13:57] [Worker-Main-1/INFO]: Preparing spawn area: 2%
[18:13:57] [Worker-Main-3/INFO]: Preparing spawn area: 4%
[18:13:57] [Worker-Main-3/INFO]: Preparing spawn area: 70%
[18:13:58] [Server thread/INFO]: Time elapsed: 3737 ms
[18:13:58] [Server thread/INFO]: [floodgate] Enabling floodgate v2.2.2-SNAPSHOT (b??-1b9042e)
[18:13:58] [Server thread/INFO]: [Geyser-Spigot] Enabling Geyser-Spigot v2.1.0-SNAPSHOT
[18:13:58] [Server thread/INFO]: Server permissions file permissions.yml is empty, ignoring it
[18:13:58] [Server thread/INFO]: [Geyser-Spigot] ******************************************
[18:13:58] [Server thread/INFO]: [Geyser-Spigot]
[18:13:58] [Server thread/INFO]: [Geyser-Spigot] Loading Geyser version 2.1.0-SNAPSHOT (git-master-d93f3dd)
[18:13:58] [Server thread/INFO]: [Geyser-Spigot]
[18:13:58] [Server thread/INFO]: [Geyser-Spigot] ******************************************
[18:14:02] [epollEventLoopGroup-3-1/ERROR]: [Geyser-Spigot] Failed to start Geyser on ( MY IP )
[18:14:02] [epollEventLoopGroup-3-1/INFO]: [Geyser-Spigot] §aSuggestion: try setting `address` under `bedrock` in the Geyser config back to 0.0.0.0
[18:14:02] [epollEventLoopGroup-3-1/INFO]: [Geyser-Spigot] §aThen, restart this server.
[18:14:02] [Server thread/ERROR]: Could not pass event ServerLoadEvent to Geyser-Spigot v2.1.0-SNAPSHOT
org.bukkit.event.EventException: null
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:310) ~[spigot-api-1.19.4-R0.1-SNAPSHOT.jar:?]
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:70) ~[spigot-api-1.19.4-R0.1-SNAPSHOT.jar:?]
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:589) ~[spigot-api-1.19.4-R0.1-SNAPSHOT.jar:?]
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:576) ~[spigot-api-1.19.4-R0.1-SNAPSHOT.jar:?]
at net.minecraft.server.MinecraftServer.loadWorld0(MinecraftServer.java:590) ~[spigot-1.19.4-R0.1-SNAPSHOT.jar:3748-Spigot-7da74da-01b2e1a]
at net.minecraft.server.MinecraftServer.loadLevel(MinecraftServer.java:414) ~[spigot-1.19.4-R0.1-SNAPSHOT.jar:3748-Spigot-7da74da-01b2e1a]
at net.minecraft.server.dedicated.DedicatedServer.e(DedicatedServer.java:250) ~[spigot-1.19.4-R0.1-SNAPSHOT.jar:3748-Spigot-7da74da-01b2e1a]
at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:975) ~[spigot-1.19.4-R0.1-SNAPSHOT.jar:3748-Spigot-7da74da-01b2e1a]
at net.minecraft.server.MinecraftServer.lambda$0(MinecraftServer.java:304) ~[spigot-1.19.4-R0.1-SNAPSHOT.jar:3748-Spigot-7da74da-01b2e1a]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
Caused by: java.util.concurrent.CompletionException: io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Cannot assign requested address
at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332) ~[?:?]
at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:347) ~[?:?]
at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:874) ~[?:?]
at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841) ~[?:?]
at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510) ~[?:?]
at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162) ~[?:?]
at org.geysermc.geyser.network.netty.GeyserServer.lambda$bind$0(GeyserServer.java:113) ~[?:?]
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:552) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:609) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at org.cloudburstmc.netty.channel.proxy.ProxyChannel.lambda$correctPromise$0(ProxyChannel.java:57) ~[?:?]
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:552) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:609) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.channel.AbstractChannel$AbstractUnsafe.safeSetFailure(AbstractChannel.java:999) ~[netty-transport-4.1.82.Final.jar:4.1.82.Final]
at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:564) ~[netty-transport-4.1.82.Final.jar:4.1.82.Final]
at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1334) ~[netty-transport-4.1.82.Final.jar:4.1.82.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:506) ~[netty-transport-4.1.82.Final.jar:4.1.82.Final]
at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:491) ~[netty-transport-4.1.82.Final.jar:4.1.82.Final]
at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:973) ~[netty-transport-4.1.82.Final.jar:4.1.82.Final]
at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:260) ~[netty-transport-4.1.82.Final.jar:4.1.82.Final]
at org.cloudburstmc.netty.handler.codec.raknet.ProxyOutboundRouter.bind(ProxyOutboundRouter.java:48) ~[?:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:506) ~[netty-transport-4.1.82.Final.jar:4.1.82.Final]
at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:491) ~[netty-transport-4.1.82.Final.jar:4.1.82.Final]
at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:973) ~[netty-transport-4.1.82.Final.jar:4.1.82.Final]
at org.cloudburstmc.netty.channel.proxy.ProxyChannel.bind(ProxyChannel.java:188) ~[?:?]
at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:356) ~[netty-transport-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:406) ~[netty-transport-classes-epoll-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.82.Final.jar:4.1.82.Final]
... 1 more
Caused by: io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Cannot assign requested address
[18:14:02] [Server thread/INFO]: Done (22.509s)! For help, type "help
Configuration file:
- --------------------------------
- Geyser Configuration File
# - A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
# - GitHub: https://github.com/GeyserMC/Geyser
- Discord: https://discord.gg/geysermc
- --------------------------------
bedrock:
# The IP address that will listen for connections.
# Generally, you should only uncomment and change this if you want to limit what IPs can connect to your server.
address: MY IP
# The port that will listen for connections
port: MY PORT
# Some hosting services change your Java port everytime you start the server and require the same port to be used for Bedrock.
# This option makes the Bedrock port the same as the Java port every time you start the server.
# This option is for the plugin version only.
clone-remote-port: false
# The MOTD that will be broadcasted to Minecraft: Bedrock Edition clients. This is irrelevant if "passthrough-motd" is set to true
# If either of these are empty, the respective string will default to "Geyser"
motd1: "Geyser"
motd2: "Another Geyser server."
# The Server Name that will be sent to Minecraft: Bedrock Edition clients. This is visible in both the pause menu and the settings menu.
server-name: "Geyser"
# How much to compress network traffic to the Bedrock client. The higher the number, the more CPU usage used, but
# the smaller the bandwidth used. Does not have any effect below -1 or above 9. Set to -1 to disable.
compression-level: 6
# Whether to enable PROXY protocol or not for clients. You DO NOT WANT this feature unless you run UDP reverse proxy
# in front of your Geyser instance.
enable-proxy-protocol: false
# A list of allowed PROXY protocol speaking proxy IP addresses/subnets. Only effective when "enable-proxy-protocol" is enabled, and
# should really only be used when you are not able to use a proper firewall (usually true with shared hosting providers etc.).
# Keeping this list empty means there is no IP address whitelist.
# Both IP addresses and subnets are supported.
#proxy-protocol-whitelisted-ips: [ "127.0.0.1", "172.18.0.0/16" ]
remote:
# The IP address of the remote (Java Edition) server
# If it is "auto", for standalone version the remote address will be set to 127.0.0.1,
# for plugin versions, it is recommended to keep this as "auto" so Geyser will automatically configure address, port, and auth-type.
# Leave as "auto" if floodgate is installed.
address: auto
# The port of the remote (Java Edition) server
# For plugin versions, if address has been set to "auto", the port will also follow the server's listening port.
port: MY PORT
# Authentication type. Can be offline, online, or floodgate (see https://github.com/GeyserMC/Geyser/wiki/Floodgate).
# For plugin versions, it's recommended to keep the `address` field to "auto" so Floodgate support is automatically configured.
# If Floodgate is installed and `address:` is set to "auto", then "auth-type: floodgate" will automatically be used.
auth-type: online
# Allow for password-based authentication methods through Geyser. Only useful in online mode.
# If this is false, users must authenticate to Microsoft using a code provided by Geyser on their desktop.
allow-password-authentication: true
# Whether to enable PROXY protocol or not while connecting to the server.
# This is useful only when:
# 1) Your server supports PROXY protocol (it probably doesn't)
# 2) You run Velocity or BungeeCord with the option enabled in the proxy's main config.
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
use-proxy-protocol: false
# Forward the hostname that the Bedrock client used to connect over to the Java server
# This is designed to be used for forced hosts on proxies
forward-hostname: false
- Floodgate uses encryption to ensure use from authorised sources.
- This should point to the public key generated by Floodgate (BungeeCord, Spigot or Velocity)
- You can ignore this when not using Floodgate.
- If you're using a plugin version of Floodgate on the same server, the key will automatically be picked up from Floodgate.
floodgate-key-file: key.pem
- For online mode authentication type only.
- Stores a list of Bedrock players that should have their Java Edition account saved after login.
- This saves a token that can be reused to authenticate the player later. This does not save emails or passwords,
- but you should still be cautious when adding to this list and giving others access to this Geyser instance's files.
- Removing a name from this list will delete its cached login information on the next Geyser startup.
- The file that tokens will be saved in is in the same folder as this config, named "saved-refresh-tokens.json".
saved-user-logins:
- ThisExampleUsernameShouldBeLongEnoughToNeverBeAnXboxUsername
- ThisOtherExampleUsernameShouldAlsoBeLongEnough
- Specify how many seconds to wait while user authorizes Geyser to access their Microsoft account.
- User is allowed to disconnect from the server during this period.
pending-authentication-timeout: 120
- Bedrock clients can freeze when opening up the command prompt for the first time if given a lot of commands.
- Disabling this will prevent command suggestions from being sent and solve freezing for Bedrock clients.
command-suggestions: true
- The following three options enable "ping passthrough" - the MOTD, player count and/or protocol name gets retrieved from the Java server.
- Relay the MOTD from the remote server to Bedrock players.
passthrough-motd: false - Relay the protocol name (e.g. BungeeCord [X.X], Paper 1.X) - only really useful when using a custom protocol name!
- This will also show up on sites like MCSrvStatus. <mcsrvstat.us>
passthrough-protocol-name: false - Relay the player count and max players from the remote server to Bedrock players.
passthrough-player-counts: false - Enable LEGACY ping passthrough. There is no need to enable this unless your MOTD or player count does not appear properly.
- This option does nothing on standalone.
legacy-ping-passthrough: false - How often to ping the remote server, in seconds. Only relevant for standalone or legacy ping passthrough.
- Increase if you are getting BrokenPipe errors.
ping-passthrough-interval: 3
- Whether to forward player ping to the server. While enabling this will allow Bedrock players to have more accurate
- ping, it may also cause players to time out more easily.
forward-player-ping: false
- Maximum amount of players that can connect. This is only visual at this time and does not actually limit player count.
max-players: 100
- If debug messages should be sent through console
debug-mode: false
- Allow third party capes to be visible. Currently allowing:
- OptiFine capes, LabyMod capes, 5Zig capes and MinecraftCapes
allow-third-party-capes: false
- Allow third party deadmau5 ears to be visible. Currently allowing:
- MinecraftCapes
allow-third-party-ears: false
- Allow a fake cooldown indicator to be sent. Bedrock players otherwise do not see a cooldown as they still use 1.8 combat.
- Please note: if the cooldown is enabled, some users may see a black box during the cooldown sequence, like below:
- https://cdn.discordapp.com/attachments/613170125696270357/957075682230419466/Screenshot_from_2022-03-25_20-35-08.png
- This can be disabled by going into Bedrock settings under the accessibility tab and setting "Text Background Opacity" to 0
- This setting can be set to "title", "actionbar" or "false"
show-cooldown: title
- Controls if coordinates are shown to players.
show-coordinates: true
- Whether Bedrock players are blocked from performing their scaffolding-style bridging.
disable-bedrock-scaffolding: false
- If set, when a Bedrock player performs any emote, it will swap the offhand and mainhand items, just like the Java Edition keybind
- There are three options this can be set to:
- disabled - the default/fallback, which doesn't apply this workaround
- no-emotes - emotes will NOT be sent to other Bedrock clients and offhand will be swapped. This effectively disables all emotes from being seen.
- emotes-and-offhand - emotes will be sent to Bedrock clients and offhand will be swapped
emote-offhand-workaround: "disabled"
- The default locale if we dont have the one the client requested. Uncomment to not use the default system language.
- default-locale: en_us
- Specify how many days images will be cached to disk to save downloading them from the internet.
- A value of 0 is disabled. (Default: 0)
cache-images: 0
- Allows custom skulls to be displayed. Keeping them enabled may cause a performance decrease on older/weaker devices.
allow-custom-skulls: true
- The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
- Setting this to -1 will cause all custom skulls to be displayed regardless of distance or number.
max-visible-custom-skulls: 128
- The radius in blocks around the player in which custom skulls are displayed.
custom-skull-render-distance: 32
- 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.
- This should only need to be disabled if using a proxy that does not use the "transfer packet" style of server switching.
- If this is disabled, furnace minecart items will be mapped to hopper minecart items.
- This option requires a restart of Geyser in order to change its setting.
add-non-bedrock-items: true
- Bedrock prevents building and displaying blocks above Y127 in the Nether.
- This config option works around that by changing the Nether dimension ID to the End ID.
- The main downside to this is that the entire Nether will have the same red fog rather than having different fog for each biome.
above-bedrock-nether-building: false
- Force clients to load all resource packs if there are any.
- If set to false, it allows the user to connect to the server even if they don't
- want to download the resource packs.
force-resource-packs: true
- Allows Xbox achievements to be unlocked.
- THIS DISABLES ALL COMMANDS FROM SUCCESSFULLY RUNNING FOR BEDROCK IN-GAME, as otherwise Bedrock thinks you are cheating.
xbox-achievements-enabled: true
- Whether player IP addresses will be logged by the server.
log-player-ip-addresses: true
- Whether to alert the console and operators that a new Geyser version is available that supports a Bedrock version
- that this Geyser version does not support. It's recommended to keep this option enabled, as many Bedrock platforms
- auto-update.
notify-on-new-bedrock-update: true
- Which item to use to mark unavailable slots in a Bedrock player inventory. Examples of this are the 2x2 crafting grid while in creative,
- or custom inventory menus with sizes different from the usual 3x9. A barrier block is the default item.
unusable-space-block: minecraft:barrier
- bStats is a stat tracker that is entirely anonymous and tracks only basic information
- about Geyser, such as how many people are online, how many servers are using Geyser,
- what OS is being used, etc. You can learn more about bStats here: https://bstats.org/.
- https://bstats.org/plugin/server-implementation/GeyserMC
metrics:
# If metrics should be enabled
enabled: true
# UUID of server, don't change!
uuid: 9fc25e5b-77f9-40ec-a4f0-8f3f80efb6e2
- ADVANCED OPTIONS - DO NOT TOUCH UNLESS YOU KNOW WHAT YOU ARE DOING!
- Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
- a lot of scoreboard packets per second can cause serious lag.
- This option allows you to specify after how many Scoreboard packets per seconds
- the Scoreboard updates will be limited to four updates per second.
scoreboard-packet-threshold: 20
- Allow connections from ProxyPass and Waterdog.
- See https://www.spigotmc.org/wiki/firewall-guide/ for assistance - use UDP instead of TCP.
enable-proxy-connections: false
- The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
- 1400 is the default.
mtu: 1400
- Whether to connect directly into the Java server without creating a TCP connection.
- This should only be disabled if a plugin that interfaces with packets or the network does not work correctly with Geyser.
- If enabled on plugin versions, the remote address and port sections are ignored
- If disabled on plugin versions, expect performance decrease and latency increase
use-direct-connection: true
- Whether Geyser should attempt to disable compression for Bedrock players. This should be a benefit as there is no need to compress data
- when Java packets aren't being handled over the network.
- This requires use-direct-connection to be true.
disable-compression: true
config-version: 4