forked from kaboomserver/server
192 lines
9.7 KiB
YAML
192 lines
9.7 KiB
YAML
# --------------------------------
|
|
# Geyser Configuration File
|
|
#
|
|
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
|
#
|
|
# GitHub: https://github.com/GeyserMC/Geyser
|
|
# Discord: https://discord.geysermc.org/
|
|
# --------------------------------
|
|
|
|
bedrock:
|
|
# The IP address that will listen for connections.
|
|
# There is no reason to change this unless you want to limit what IPs can connect to your server.
|
|
address: 0.0.0.0
|
|
# The port that will listen for connections
|
|
port: 19132
|
|
# 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. Irrelevant if "passthrough-motd" is set to true
|
|
# If either of these are empty, the respective string will default to "Geyser"
|
|
motd1: "§7§lKaboom > §rFree OP - Anarchy"
|
|
motd2: "§7§lKaboom > §rFree OP - Anarchy"
|
|
# 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: "Kaboom"
|
|
# 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, Geyser will attempt to find the best address to connect to.
|
|
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: 25565
|
|
# Authentication type. Can be offline, online, or floodgate (see https://github.com/GeyserMC/Geyser/wiki/Floodgate).
|
|
auth-type: offline
|
|
# 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
|
|
|
|
# Floodgate uses encryption to ensure use from authorised sources.
|
|
# This should point to the public key generated by Floodgate (Bungee or CraftBukkit)
|
|
# You can ignore this when not using Floodgate.
|
|
floodgate-key-file: public-key.pem
|
|
|
|
# The Xbox/Minecraft Bedrock username is the key for the Java server auth-info.
|
|
# This allows automatic configuration/login to the remote Java server.
|
|
# If you are brave enough to put your Mojang account info into a config file.
|
|
# Uncomment the lines below to enable this feature.
|
|
#userAuths:
|
|
# BedrockAccountUsername: # Your Minecraft: Bedrock Edition username
|
|
# email: javaccountemail@example.com # Your Minecraft: Java Edition email
|
|
# password: javaccountpassword123 # Your Minecraft: Java Edition password
|
|
# microsoft-account: true # Whether the account is a Mojang or Microsoft account.
|
|
#
|
|
# bluerkelp2:
|
|
# email: not_really_my_email_address_mr_minecrafter53267@gmail.com
|
|
# password: "this isn't really my password"
|
|
# microsoft-account: false
|
|
|
|
# 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: false
|
|
|
|
# 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: 10000
|
|
|
|
# If debug messages should be sent through console
|
|
debug-mode: false
|
|
|
|
# Thread pool size
|
|
general-thread-pool: 32
|
|
|
|
# Allow third party capes to be visible. Currently allowing:
|
|
# OptiFine capes, LabyMod capes, 5Zig capes and MinecraftCapes
|
|
allow-third-party-capes: false # Removed from Geyser
|
|
|
|
# Allow third party deadmau5 ears to be visible. Currently allowing:
|
|
# MinecraftCapes
|
|
allow-third-party-ears: false # Removed from Geyser
|
|
|
|
# Allow a fake cooldown indicator to be sent. Bedrock players do not see a cooldown as they still use 1.8 combat
|
|
show-cooldown: true
|
|
|
|
# Controls if coordinates are shown to players.
|
|
show-coordinates: true
|
|
|
|
# The default locale if we dont have the one the client requested. Uncomment to not use the default system language.
|
|
# default-locale: en_us
|
|
|
|
# Configures if chunk caching should be enabled or not. This keeps an individual
|
|
# record of each block the client loads in. This feature does allow for a few things
|
|
# such as more accurate movement that causes less problems with anticheat (meaning
|
|
# you're less likely to be banned) and allows block break animations to show up in
|
|
# creative mode (and other features). Although this increases RAM usage, it likely
|
|
# won't have much of an effect for the vast majority of people. However, if you're
|
|
# running out of RAM or are in a RAM-sensitive environment, you may want to disable
|
|
# this. When using the Spigot version of Geyser, support for features or
|
|
# implementations this allows is automatically enabled without the additional caching
|
|
# as Geyser has direct access to the server itself.
|
|
cache-chunks: false
|
|
|
|
# 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
|
|
|
|
# Bedrock prevents building and displaying blocks above Y127 in the Nether -
|
|
# enabling this config option works around that by changing the Nether dimension ID
|
|
# to the End ID. The main downside to this is that the sky will resemble that of
|
|
# the end sky in the nether, but ultimately it's the only way for this feature to work.
|
|
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: false
|
|
|
|
# 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: false
|
|
|
|
# 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: false
|
|
# UUID of server, don't change!
|
|
uuid:
|
|
|
|
# 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 use direct server methods to retrieve information such as block states.
|
|
# Turning this off for Spigot will stop NMS from being used but will have a performance impact.
|
|
use-adapters: true
|
|
|
|
config-version: 4
|