mirror of
https://github.com/GeyserMC/Geyser.git
synced 2026-01-04 15:31:36 +00:00
Switch config system to Configurate (#5010)
* Start implementing Configurate config system * More development * Start migrating to Gson only * Progress * Update usage of WebUtils * Most things now use Gson for JSON * Allow tests to succeed by using new Gson version * Use slightly cleaner version for Version deserializer * Work around older Gson versions without record support * GeyserCustomSkullConfiguration uses Configurate * Fix regression in properties get * New config used in core * The configuration is gone. Long live the config. * More changes and migrations away from Jackson * Improve node ordering when updating configs * typo * Better check for ignoring non-configurate configs for considering comment moving * Ensure metrics UUID is valid * Initial advanced config * Remove Jackson; finish config value placements * Remove duplicate relocate declarations * Let annotations work * Renaming to PluginSpecific * Use global bStats config where possible * Fix test * Re-introduce asterisk behavior in configs * Remove GeyserPluginBootstrap as it's no longer necessary * Remove old config.yml file * Update Xbox achievement comment * Apply suggestions from code review Co-authored-by: chris <github@onechris.mozmail.com> * No need to remove values anymore * Fix: disable bstats relocation on platforms where it is not needed * ensure it builds * Update custom unavailable slot comment Co-authored-by: chris <github@onechris.mozmail.com> * Update cooldown image * Logger message for direct-compression still being enabled * oops * More explicit RuntimeException message Co-authored-by: Konicai <71294714+Konicai@users.noreply.github.com> * Constant for 'system' locale * Better config JSON encoding (something is broken with Cloudflare; we'll figure it out * Fix broadcast port default * Add this file too * Update configurate branch * fix build * Fix: Allow using custom config file on Standalone, add relocation comment * Move config loading to GeyserBootstrap interface * Add and rename some config options, add section notes (#5390) * Add and rename some config options, add section notes * adjust message * Update core/src/main/java/org/geysermc/geyser/command/defaults/ConnectionTestCommand.java Co-authored-by: Eclipse <eclipse@eclipseisoffline.xyz> * Update core/src/main/java/org/geysermc/geyser/configuration/GeyserConfig.java Co-authored-by: Eclipse <eclipse@eclipseisoffline.xyz> * Update ConfigLoader.java * Update AdvancedConfig.java * clarify that we're talking about the HAProxy protocol * rename config option to use-haproxy-protocol * remove ominous warning sign on xbox auth warning * adjust wording --------- Co-authored-by: Eclipse <eclipse@eclipseisoffline.xyz> * Back to one config file * Some minor touchups * Configurate: Sectionification (#5904) * Init: config sections * Start on adding tests, move migrations over to ConfigMigrations class * Get rid of auth section again, rename that one config option, fix mtu migration * Move custom skulls config options to the bottom of the gameplay settings * Add more tests * Rename and migrate proxy-protocol-whitelisted-ips to haproxy-protocol-whitelisted-ips * Add automatic downloading of the GeyserOptionalPack * Revert "Add automatic downloading of the GeyserOptionalPack" This reverts commit65b96208fb. * Add more invalid config tests * Warn about emote-offhand-workaround removal * Add automatic loading of the GeyserOptionalPack (feature/configurate) (#5964) * Add automatic downloading of the GeyserOptionalPack * Warn about including the OptionalPack from extensions when Geyser is already including it instead of throwing. * Copy optional pack instead of downloading --------- Co-authored-by: onebeastchris <github@onechris.mozmail.com> * Remove unused variable * Start warning users not running Java 21 * Update tests, temporarily remove NumericRanges test * Remove duplicate advanced section from Geyser dump * Address some "reviews" * yeet md5 hash from geyser dump * Add info about number of resource packs / amount of mappings into Geyser dump * Re-enable invalid config loading test * Fix: allow-custom-skulls migration * Fix test * Add "enable-emotes" configuration option * Rename "emotes-enabled" to "show-emotes" * Only enable integrated pack when optional pack isn't present * Update integrated pack * Exclude jackson annotations, remove leftover debug print * Remove one-time config migration warnings as we don't have access to the logger at that stage * Throw more detailed descriptive error when loading resource packs from the "packs" folder, add another legacy config test * Fix NeoForge's fun module conflict * Re-add warning about moved functionality, fix Geyser-ViaProxy This reverts commitfbadfa574a. * oops * Move GeyserLegacyPingPassthrough to separate thread to avoid Standalone command locking issues --------- Co-authored-by: Konicai <71294714+Konicai@users.noreply.github.com> Co-authored-by: chris <github@onechris.mozmail.com> Co-authored-by: Eclipse <eclipse@eclipseisoffline.xyz> Co-authored-by: Aurora <auroranova8756@gmail.com>
This commit is contained in:
Camotoy
@@ -0,0 +1,179 @@
|
||||
/*
|
||||
* Copyright (c) 2024 GeyserMC. http://geysermc.org
|
||||
*
|
||||
* Permission is hereby granted, free of charge, to any person obtaining a copy
|
||||
* of this software and associated documentation files (the "Software"), to deal
|
||||
* in the Software without restriction, including without limitation the rights
|
||||
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
||||
* copies of the Software, and to permit persons to whom the Software is
|
||||
* furnished to do so, subject to the following conditions:
|
||||
*
|
||||
* The above copyright notice and this permission notice shall be included in
|
||||
* all copies or substantial portions of the Software.
|
||||
*
|
||||
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
||||
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
||||
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
||||
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
||||
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
||||
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
||||
* THE SOFTWARE.
|
||||
*
|
||||
* @author GeyserMC
|
||||
* @link https://github.com/GeyserMC/Geyser
|
||||
*/
|
||||
|
||||
package org.geysermc.geyser.configuration;
|
||||
|
||||
import lombok.SneakyThrows;
|
||||
import org.geysermc.geyser.api.util.PlatformType;
|
||||
import org.junit.jupiter.api.Test;
|
||||
import org.junit.jupiter.api.io.TempDir;
|
||||
import org.spongepowered.configurate.CommentedConfigurationNode;
|
||||
import org.spongepowered.configurate.ConfigurateException;
|
||||
import org.spongepowered.configurate.util.CheckedConsumer;
|
||||
|
||||
import java.io.File;
|
||||
import java.io.IOException;
|
||||
import java.net.URISyntaxException;
|
||||
import java.net.URL;
|
||||
import java.nio.file.Files;
|
||||
import java.nio.file.Path;
|
||||
import java.nio.file.StandardCopyOption;
|
||||
import java.util.List;
|
||||
import java.util.Objects;
|
||||
import java.util.stream.Stream;
|
||||
|
||||
import static org.junit.jupiter.api.Assertions.assertEquals;
|
||||
import static org.junit.jupiter.api.Assertions.assertThrows;
|
||||
import static org.junit.jupiter.api.Assertions.assertTrue;
|
||||
|
||||
public class ConfigLoaderTest {
|
||||
|
||||
private static final String CONFIG_PREFIX = "configuration";
|
||||
|
||||
@TempDir
|
||||
Path tempDirectory;
|
||||
|
||||
@Test
|
||||
void testCreateNewConfig() throws Exception {
|
||||
// Test that the result of generating a config, and the result of reading it back after writing it, is the same
|
||||
|
||||
File file = tempDirectory.resolve("config.yml").toFile();
|
||||
|
||||
forAllConfigs(type -> {
|
||||
CommentedConfigurationNode config1 = new ConfigLoader(file).loadConfigurationNode(type, PlatformType.STANDALONE);
|
||||
|
||||
long initialModification = file.lastModified();
|
||||
assertTrue(file.exists()); // should have been created
|
||||
List<String> firstContents = Files.readAllLines(file.toPath());
|
||||
|
||||
CommentedConfigurationNode config2 = new ConfigLoader(file).loadConfigurationNode(type, PlatformType.STANDALONE);
|
||||
List<String> secondContents = Files.readAllLines(file.toPath());
|
||||
|
||||
assertEquals(initialModification, file.lastModified()); // should not have been touched
|
||||
assertEquals(firstContents, secondContents);
|
||||
|
||||
// Must ignore this, as when the config is read back, the header is interpreted as a comment on the first node in the map
|
||||
config1.node("java").comment(null);
|
||||
config2.node("java").comment(null);
|
||||
assertEquals(config1, config2);
|
||||
});
|
||||
}
|
||||
|
||||
@Test
|
||||
void testDefaultConfigMigration() throws Exception {
|
||||
testConfiguration("default");
|
||||
}
|
||||
|
||||
@Test
|
||||
void testAllChangedConfigMigration() throws Exception {
|
||||
testConfiguration("all-changed");
|
||||
}
|
||||
|
||||
@Test
|
||||
void testLegacyConfigMigration() throws Exception {
|
||||
testConfiguration("legacy");
|
||||
}
|
||||
|
||||
@Test
|
||||
void allowCustomSkullsMigration() throws Exception {
|
||||
testConfiguration("allow-custom-skulls");
|
||||
}
|
||||
|
||||
@Test
|
||||
void testNoEmotesMigration() throws Exception {
|
||||
testConfiguration("migrate-no-emotes");
|
||||
}
|
||||
|
||||
@Test
|
||||
void testChewsOldConfig() throws Exception {
|
||||
testConfiguration("chew");
|
||||
}
|
||||
|
||||
@Test
|
||||
void testInvalidConfig() throws Exception {
|
||||
streamResourceFiles(CONFIG_PREFIX + "/invalid").forEach(resource -> {
|
||||
try {
|
||||
forAllConfigs(type -> {
|
||||
assertThrows(ConfigurateException.class,
|
||||
() -> new ConfigLoader(resource).loadConfigurationNode(type, getPlatformType(type)),
|
||||
"Did not get exception while loading %s (file: %s)".formatted(type.getSimpleName(), resource.getName()));
|
||||
});
|
||||
} catch (Exception e) {
|
||||
throw new RuntimeException(e);
|
||||
}
|
||||
});
|
||||
}
|
||||
|
||||
public void testConfiguration(String folder) throws Exception {
|
||||
forAllConfigs(type -> {
|
||||
CommentedConfigurationNode oldTransformed = new ConfigLoader(copyResourceToTempFile(folder, "before.yml"))
|
||||
.loadConfigurationNode(type, getPlatformType(type));
|
||||
|
||||
String configName = type == GeyserRemoteConfig.class ? "remote" : "plugin";
|
||||
CommentedConfigurationNode newTransformed = new ConfigLoader(copyResourceToTempFile(folder, configName + ".yml"))
|
||||
.loadConfigurationNode(type, getPlatformType(type));
|
||||
|
||||
assertEquals(oldTransformed, newTransformed);
|
||||
});
|
||||
}
|
||||
|
||||
File copyResourceToTempFile(String... path) throws Exception {
|
||||
File resource = getConfigResource(CONFIG_PREFIX + "/" + String.join("/", path));
|
||||
return Files.copy(resource.toPath(), tempDirectory.resolve(resource.getName()), StandardCopyOption.REPLACE_EXISTING).toFile();
|
||||
}
|
||||
|
||||
PlatformType getPlatformType(Class<? extends GeyserConfig> configClass) {
|
||||
if (configClass == GeyserRemoteConfig.class) {
|
||||
return PlatformType.STANDALONE;
|
||||
}
|
||||
if (configClass == GeyserPluginConfig.class) {
|
||||
return PlatformType.SPIGOT;
|
||||
}
|
||||
throw new IllegalArgumentException("Unsupported config class " + configClass);
|
||||
}
|
||||
|
||||
void forAllConfigs(CheckedConsumer<Class<? extends GeyserConfig>, Exception> consumer) throws Exception {
|
||||
consumer.accept(GeyserPluginConfig.class);
|
||||
consumer.accept(GeyserRemoteConfig.class);
|
||||
}
|
||||
|
||||
private static Stream<File> streamResourceFiles(String directory) throws IOException, URISyntaxException {
|
||||
URL resourceUrl = ConfigLoaderTest.class.getClassLoader().getResource(directory);
|
||||
Objects.requireNonNull(resourceUrl, "Resource directory not found: " + directory);
|
||||
|
||||
Path resourcePath = Path.of(resourceUrl.toURI());
|
||||
// Walk the directory, but don't go into subdirectories (maxDepth = 1)
|
||||
return Files.walk(resourcePath, 1)
|
||||
.filter(path -> !path.equals(resourcePath)) // Exclude the directory itself
|
||||
.filter(Files::isRegularFile) // Ensure we only get files
|
||||
.map(Path::toFile);
|
||||
}
|
||||
|
||||
@SneakyThrows
|
||||
private File getConfigResource(String name) {
|
||||
URL url = Objects.requireNonNull(getClass().getClassLoader().getResource(name), "No resource for name: " + name);
|
||||
return Path.of(url.toURI()).toFile();
|
||||
}
|
||||
}
|
||||
@@ -25,20 +25,20 @@
|
||||
|
||||
package org.geysermc.geyser.scoreboard.network.util;
|
||||
|
||||
import static org.mockito.Mockito.mockStatic;
|
||||
import static org.mockito.Mockito.when;
|
||||
import org.cloudburstmc.protocol.bedrock.packet.BedrockPacket;
|
||||
import org.geysermc.geyser.GeyserImpl;
|
||||
import org.geysermc.geyser.configuration.GeyserConfig;
|
||||
import org.geysermc.geyser.session.GeyserSession;
|
||||
import org.geysermc.geyser.translator.protocol.PacketTranslator;
|
||||
import org.mockito.Mockito;
|
||||
|
||||
import java.util.ArrayList;
|
||||
import java.util.Collections;
|
||||
import java.util.List;
|
||||
import java.util.function.Consumer;
|
||||
import org.cloudburstmc.protocol.bedrock.packet.BedrockPacket;
|
||||
import org.geysermc.geyser.GeyserImpl;
|
||||
import org.geysermc.geyser.configuration.GeyserConfiguration;
|
||||
import org.geysermc.geyser.registry.Registries;
|
||||
import org.geysermc.geyser.session.GeyserSession;
|
||||
import org.geysermc.geyser.translator.protocol.PacketTranslator;
|
||||
import org.mockito.Mockito;
|
||||
|
||||
import static org.mockito.Mockito.mockStatic;
|
||||
import static org.mockito.Mockito.when;
|
||||
|
||||
public class GeyserMockContext {
|
||||
private final List<Object> mocksAndSpies = new ArrayList<>();
|
||||
@@ -49,11 +49,11 @@ public class GeyserMockContext {
|
||||
var context = new GeyserMockContext();
|
||||
|
||||
var geyserImpl = context.mock(GeyserImpl.class);
|
||||
var config = context.mock(GeyserConfiguration.class);
|
||||
|
||||
when(config.getScoreboardPacketThreshold()).thenReturn(1_000);
|
||||
|
||||
when(geyserImpl.getConfig()).thenReturn(config);
|
||||
var config = context.mock(GeyserConfig.class);
|
||||
when(geyserImpl.config()).thenReturn(config);
|
||||
var advancedConfig = context.mock(GeyserConfig.AdvancedConfig.class);
|
||||
when(config.advanced()).thenReturn(advancedConfig);
|
||||
when(advancedConfig.scoreboardPacketThreshold()).thenReturn(1_000);
|
||||
|
||||
var logger = context.storeObject(new EmptyGeyserLogger());
|
||||
when(geyserImpl.getLogger()).thenReturn(logger);
|
||||
|
||||
219
core/src/test/resources/configuration/all-changed/before.yml
Normal file
219
core/src/test/resources/configuration/all-changed/before.yml
Normal file
@@ -0,0 +1,219 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://wiki.geysermc.org/
|
||||
#
|
||||
# NOTICE: See https://wiki.geysermc.org/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
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: 127.0.0.1
|
||||
# The port that will listen for connections
|
||||
port: 19122
|
||||
# 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: true
|
||||
# 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: "Gayser"
|
||||
motd2: "Another Gayser 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: "Gayser"
|
||||
# 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: 5
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# DO NOT uncomment and change this unless Geyser runs on a different internal port than the one that is used to connect.
|
||||
broadcast-port: 19133
|
||||
# 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: true
|
||||
# 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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
proxy-protocol-whitelisted-ips: [ "127.0.0.1", "172.18.0.0/13" ]
|
||||
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: test.geysermc.org
|
||||
# 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: 25564
|
||||
# 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: floodgate
|
||||
# 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: true
|
||||
# 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: true
|
||||
|
||||
# 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: keyyy.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:
|
||||
- ThisExampleUsername
|
||||
- ThisOther
|
||||
|
||||
# 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: 111
|
||||
|
||||
# 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 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: true
|
||||
# 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: 2
|
||||
|
||||
# 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: true
|
||||
|
||||
# Maximum amount of players that can connect. This is only visual at this time and does not actually limit player count.
|
||||
max-players: 99
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: true
|
||||
|
||||
# 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: actionbar
|
||||
|
||||
# Controls if coordinates are shown to players.
|
||||
show-coordinates: false
|
||||
|
||||
# Whether Bedrock players are blocked from performing their scaffolding-style bridging.
|
||||
disable-bedrock-scaffolding: true
|
||||
|
||||
# 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: "emotes-and-offhand"
|
||||
|
||||
# The default locale if we dont have the one the client requested. Uncomment to not use the default system language.
|
||||
default-locale: en_uk
|
||||
|
||||
# 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: 10
|
||||
|
||||
# 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: 111
|
||||
|
||||
# The radius in blocks around the player in which custom skulls are displayed.
|
||||
custom-skull-render-distance: 19
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
add-non-bedrock-items: false
|
||||
|
||||
# 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: true
|
||||
|
||||
# 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: false
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
xbox-achievements-enabled: true
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: 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
|
||||
|
||||
# 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:apple
|
||||
|
||||
# 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: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# 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: 10
|
||||
|
||||
# Allow connections from ProxyPass and Waterdog.
|
||||
# See https://www.spigotmc.org/wiki/firewall-guide/ for assistance - use UDP instead of TCP.
|
||||
enable-proxy-connections: true
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1399
|
||||
|
||||
# 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: false
|
||||
|
||||
# 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: false
|
||||
|
||||
config-version: 4
|
||||
239
core/src/test/resources/configuration/all-changed/plugin.yml
Normal file
239
core/src/test/resources/configuration/all-changed/plugin.yml
Normal file
@@ -0,0 +1,239 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://geysermc.org/wiki
|
||||
#
|
||||
# NOTICE: See https://geysermc.org/wiki/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
# Network settings for the Bedrock listener
|
||||
bedrock:
|
||||
# The IP address that Geyser will bind on to listen for incoming Bedrock connections.
|
||||
# Generally, you should only change this if you want to limit what IPs can connect to your server.
|
||||
address: 127.0.0.1
|
||||
|
||||
# The port that will Geyser will listen on for incoming Bedrock connections.
|
||||
# Since Minecraft: Bedrock Edition uses UDP, this port must allow UDP traffic.
|
||||
port: 19122
|
||||
|
||||
# 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.
|
||||
clone-remote-port: true
|
||||
|
||||
# Network settings for the Java server connection
|
||||
java:
|
||||
# What type of authentication Bedrock players will be checked against when logging into the Java server.
|
||||
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
|
||||
auth-type: floodgate
|
||||
|
||||
# MOTD settings
|
||||
motd:
|
||||
# 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"
|
||||
primary-motd: Gayser
|
||||
secondary-motd: Another Gayser server.
|
||||
|
||||
# Whether Geyser should relay the MOTD from the Java server to Bedrock players.
|
||||
passthrough-motd: false
|
||||
|
||||
# Maximum amount of players that can connect.
|
||||
# This is only visual, and is only applied if passthrough-motd is disabled.
|
||||
max-players: 99
|
||||
|
||||
# Whether to relay the player count and max players from the Java server to Bedrock players.
|
||||
passthrough-player-counts: false
|
||||
|
||||
# Whether to use server API methods to determine the Java server's MOTD and ping passthrough.
|
||||
# There is no need to disable this unless your MOTD or player count does not appear properly.
|
||||
integrated-ping-passthrough: false
|
||||
|
||||
# How often to ping the Java server to refresh MOTD and player count, in seconds.
|
||||
# Only relevant if integrated-ping-passthrough is disabled.
|
||||
ping-passthrough-interval: 2
|
||||
|
||||
# Gameplay options that affect Bedrock players
|
||||
gameplay:
|
||||
# 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: Gayser
|
||||
|
||||
# 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://geysermc.org/img/external/cooldown_indicator.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: actionbar
|
||||
|
||||
# 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
|
||||
|
||||
# Controls if coordinates are shown to players.
|
||||
show-coordinates: false
|
||||
|
||||
# Whether Bedrock players are blocked from performing their scaffolding-style bridging.
|
||||
disable-bedrock-scaffolding: 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.
|
||||
nether-roof-workaround: true
|
||||
|
||||
# Whether to show Bedrock Edition emotes to other Bedrock Edition players.
|
||||
show-emotes: 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.
|
||||
# This config option can be set to any Bedrock item identifier. If you want to set this to a custom item, make sure that you specify the item in the following format: "geyser_custom:<mapping-name>"
|
||||
unusable-space-block: minecraft:apple
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
enable-custom-content: 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: false
|
||||
|
||||
# Whether to automatically serve a resource pack that is required for some Geyser features to all connecting Bedrock players.
|
||||
# If enabled, force-resource-packs will be enabled.
|
||||
enable-integrated-pack: true
|
||||
|
||||
# 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: true
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
# If a player types in an unknown command, they will receive a message that states cheats are disabled.
|
||||
# Otherwise, commands work as expected.
|
||||
xbox-achievements-enabled: true
|
||||
|
||||
# The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
|
||||
# A value of 0 will disable all custom skulls.
|
||||
# Setting this to -1 will cause all custom skulls to be displayed regardless of distance or number.
|
||||
max-visible-custom-skulls: 111
|
||||
|
||||
# The radius in blocks around the player in which custom skulls are displayed.
|
||||
custom-skull-render-distance: 19
|
||||
|
||||
# The default locale if we don't have the one the client requested. If set to "system", the system's language will be used.
|
||||
default-locale: en_uk
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: false
|
||||
|
||||
# For online mode authentication type only.
|
||||
# Stores a list of Bedrock player usernames 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:
|
||||
- ThisExampleUsername
|
||||
- ThisOther
|
||||
|
||||
# For online mode authentication type only.
|
||||
# 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: 111
|
||||
|
||||
# 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
|
||||
|
||||
# Advanced configuration options. These usually do not need modifications.
|
||||
advanced:
|
||||
# Specify how many days player skin images will be cached to disk to save downloading them from the internet.
|
||||
# A value of 0 is disabled. (Default: 0)
|
||||
cache-images: 10
|
||||
|
||||
# Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
|
||||
# a lot of scoreboard packets per second, this 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: 10
|
||||
|
||||
# Whether Geyser should send team names in command suggestions.
|
||||
# Disable this if you have a lot of teams used that you don't need as suggestions.
|
||||
add-team-suggestions: true
|
||||
|
||||
# A list of remote resource pack urls to send to the Bedrock client for downloading.
|
||||
# The Bedrock client is very picky about how these are delivered - please see our wiki page for further info: https://geysermc.org/wiki/geyser/packs/
|
||||
resource-pack-urls: []
|
||||
|
||||
# Floodgate uses encryption to ensure use from authorized 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: keyyy.pem
|
||||
|
||||
# Advanced networking options for the Geyser to Java server connection
|
||||
java:
|
||||
# Whether to enable HAPROXY protocol when connecting to the Java server.
|
||||
# This is useful only when:
|
||||
# 1) Your Java server supports HAPROXY 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-haproxy-protocol: true
|
||||
|
||||
# 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, the remote address and port sections are ignored.
|
||||
# If disabled, expect performance decrease and latency increase.
|
||||
use-direct-connection: false
|
||||
|
||||
# Whether Geyser should attempt to disable packet compression (from the Java Server to Geyser) 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: false
|
||||
|
||||
# Advanced networking options for Geyser's Bedrock listener
|
||||
bedrock:
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# A value of 0 will broadcast the port specified above.
|
||||
# DO NOT change this unless Geyser runs on a different port than the one that is used to connect.
|
||||
broadcast-port: 19133
|
||||
|
||||
# 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: 5
|
||||
|
||||
# Whether to expect HAPROXY protocol for connecting Bedrock clients.
|
||||
# This is useful only when you are running a UDP reverse proxy in front of your Geyser instance.
|
||||
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
|
||||
use-haproxy-protocol: true
|
||||
|
||||
# A list of allowed HAPROXY protocol speaking proxy IP addresses/subnets. Only effective when "use-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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
haproxy-protocol-whitelisted-ips:
|
||||
- 127.0.0.1
|
||||
- 172.18.0.0/13
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1399
|
||||
|
||||
# This option disables the auth step Geyser performs for connecting Bedrock players.
|
||||
# It can be used to allow connections from ProxyPass and WaterdogPE. In these cases, make sure that users
|
||||
# cannot directly connect to this Geyser instance. See https://www.spigotmc.org/wiki/firewall-guide/ for
|
||||
# assistance - and use UDP instead of TCP.
|
||||
# Disabling Bedrock authentication for other use-cases is NOT SUPPORTED, as it allows anyone to spoof usernames, and is therefore a security risk.
|
||||
# All Floodgate functionality (including skin uploading and account linking) will also not work when this option is disabled.
|
||||
validate-bedrock-login: true
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: true
|
||||
|
||||
# Do not change!
|
||||
config-version: 5
|
||||
238
core/src/test/resources/configuration/all-changed/remote.yml
Normal file
238
core/src/test/resources/configuration/all-changed/remote.yml
Normal file
@@ -0,0 +1,238 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://geysermc.org/wiki
|
||||
#
|
||||
# NOTICE: See https://geysermc.org/wiki/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
# Network settings for the Bedrock listener
|
||||
bedrock:
|
||||
# The IP address that Geyser will bind on to listen for incoming Bedrock connections.
|
||||
# Generally, you should only change this if you want to limit what IPs can connect to your server.
|
||||
address: 127.0.0.1
|
||||
|
||||
# The port that will Geyser will listen on for incoming Bedrock connections.
|
||||
# Since Minecraft: Bedrock Edition uses UDP, this port must allow UDP traffic.
|
||||
port: 19122
|
||||
|
||||
# Network settings for the Java server connection
|
||||
java:
|
||||
# The IP address of the Java Edition server.
|
||||
address: test.geysermc.org
|
||||
|
||||
# The port of the Java Edition server.
|
||||
port: 25564
|
||||
|
||||
# What type of authentication Bedrock players will be checked against when logging into the Java server.
|
||||
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
|
||||
auth-type: floodgate
|
||||
|
||||
# Whether to 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: true
|
||||
|
||||
# MOTD settings
|
||||
motd:
|
||||
# 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"
|
||||
primary-motd: Gayser
|
||||
secondary-motd: Another Gayser server.
|
||||
|
||||
# Whether Geyser should relay the MOTD from the Java server to Bedrock players.
|
||||
passthrough-motd: false
|
||||
|
||||
# Maximum amount of players that can connect.
|
||||
# This is only visual, and is only applied if passthrough-motd is disabled.
|
||||
max-players: 99
|
||||
|
||||
# Whether to relay the player count and max players from the Java server to Bedrock players.
|
||||
passthrough-player-counts: false
|
||||
|
||||
# How often to ping the Java server to refresh MOTD and player count, in seconds.
|
||||
ping-passthrough-interval: 2
|
||||
|
||||
# Gameplay options that affect Bedrock players
|
||||
gameplay:
|
||||
# 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: Gayser
|
||||
|
||||
# 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://geysermc.org/img/external/cooldown_indicator.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: actionbar
|
||||
|
||||
# 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
|
||||
|
||||
# Controls if coordinates are shown to players.
|
||||
show-coordinates: false
|
||||
|
||||
# Whether Bedrock players are blocked from performing their scaffolding-style bridging.
|
||||
disable-bedrock-scaffolding: 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.
|
||||
nether-roof-workaround: true
|
||||
|
||||
# Whether to show Bedrock Edition emotes to other Bedrock Edition players.
|
||||
show-emotes: 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.
|
||||
# This config option can be set to any Bedrock item identifier. If you want to set this to a custom item, make sure that you specify the item in the following format: "geyser_custom:<mapping-name>"
|
||||
unusable-space-block: minecraft:apple
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
enable-custom-content: 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: false
|
||||
|
||||
# Whether to automatically serve a resource pack that is required for some Geyser features to all connecting Bedrock players.
|
||||
# If enabled, force-resource-packs will be enabled.
|
||||
enable-integrated-pack: true
|
||||
|
||||
# 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: true
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
# If a player types in an unknown command, they will receive a message that states cheats are disabled.
|
||||
# Otherwise, commands work as expected.
|
||||
xbox-achievements-enabled: true
|
||||
|
||||
# The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
|
||||
# A value of 0 will disable all custom skulls.
|
||||
# Setting this to -1 will cause all custom skulls to be displayed regardless of distance or number.
|
||||
max-visible-custom-skulls: 111
|
||||
|
||||
# The radius in blocks around the player in which custom skulls are displayed.
|
||||
custom-skull-render-distance: 19
|
||||
|
||||
# The default locale if we don't have the one the client requested. If set to "system", the system's language will be used.
|
||||
default-locale: en_uk
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: false
|
||||
|
||||
# For online mode authentication type only.
|
||||
# Stores a list of Bedrock player usernames 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:
|
||||
- ThisExampleUsername
|
||||
- ThisOther
|
||||
|
||||
# For online mode authentication type only.
|
||||
# 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: 111
|
||||
|
||||
# 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
|
||||
|
||||
# Advanced configuration options. These usually do not need modifications.
|
||||
advanced:
|
||||
# Specify how many days player skin images will be cached to disk to save downloading them from the internet.
|
||||
# A value of 0 is disabled. (Default: 0)
|
||||
cache-images: 10
|
||||
|
||||
# Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
|
||||
# a lot of scoreboard packets per second, this 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: 10
|
||||
|
||||
# Whether Geyser should send team names in command suggestions.
|
||||
# Disable this if you have a lot of teams used that you don't need as suggestions.
|
||||
add-team-suggestions: true
|
||||
|
||||
# A list of remote resource pack urls to send to the Bedrock client for downloading.
|
||||
# The Bedrock client is very picky about how these are delivered - please see our wiki page for further info: https://geysermc.org/wiki/geyser/packs/
|
||||
resource-pack-urls: []
|
||||
|
||||
# Floodgate uses encryption to ensure use from authorized 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: keyyy.pem
|
||||
|
||||
# Advanced networking options for the Geyser to Java server connection
|
||||
java:
|
||||
# Whether to enable HAPROXY protocol when connecting to the Java server.
|
||||
# This is useful only when:
|
||||
# 1) Your Java server supports HAPROXY 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-haproxy-protocol: true
|
||||
|
||||
# Advanced networking options for Geyser's Bedrock listener
|
||||
bedrock:
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# A value of 0 will broadcast the port specified above.
|
||||
# DO NOT change this unless Geyser runs on a different port than the one that is used to connect.
|
||||
broadcast-port: 19133
|
||||
|
||||
# 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: 5
|
||||
|
||||
# Whether to expect HAPROXY protocol for connecting Bedrock clients.
|
||||
# This is useful only when you are running a UDP reverse proxy in front of your Geyser instance.
|
||||
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
|
||||
use-haproxy-protocol: true
|
||||
|
||||
# A list of allowed HAPROXY protocol speaking proxy IP addresses/subnets. Only effective when "use-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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
haproxy-protocol-whitelisted-ips:
|
||||
- 127.0.0.1
|
||||
- 172.18.0.0/13
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1399
|
||||
|
||||
# This option disables the auth step Geyser performs for connecting Bedrock players.
|
||||
# It can be used to allow connections from ProxyPass and WaterdogPE. In these cases, make sure that users
|
||||
# cannot directly connect to this Geyser instance. See https://www.spigotmc.org/wiki/firewall-guide/ for
|
||||
# assistance - and use UDP instead of TCP.
|
||||
# Disabling Bedrock authentication for other use-cases is NOT SUPPORTED, as it allows anyone to spoof usernames, and is therefore a security risk.
|
||||
# All Floodgate functionality (including skin uploading and account linking) will also not work when this option is disabled.
|
||||
validate-bedrock-login: true
|
||||
|
||||
# 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
|
||||
enable-metrics: false
|
||||
|
||||
# The bstats metrics uuid. Do not touch!
|
||||
metrics-uuid: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: true
|
||||
|
||||
# Do not change!
|
||||
config-version: 5
|
||||
@@ -0,0 +1,219 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://wiki.geysermc.org/
|
||||
#
|
||||
# NOTICE: See https://wiki.geysermc.org/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
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: 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. 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
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# DO NOT uncomment and change this unless Geyser runs on a different internal port than the one that is used to connect.
|
||||
# broadcast-port: 19132
|
||||
# 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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
#proxy-protocol-whitelisted-ips: [ "127.0.0.1", "172.18.0.0/16", "https://example.com/whitelist.txt" ]
|
||||
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: 25565
|
||||
# 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
|
||||
# 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: true
|
||||
# Relay the player count and max players from the remote server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
# 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 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: false
|
||||
|
||||
# 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 any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# 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.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# 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: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# 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
|
||||
@@ -0,0 +1,237 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://geysermc.org/wiki
|
||||
#
|
||||
# NOTICE: See https://geysermc.org/wiki/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
# Network settings for the Bedrock listener
|
||||
bedrock:
|
||||
# The IP address that Geyser will bind on to listen for incoming Bedrock connections.
|
||||
# Generally, you should only change this if you want to limit what IPs can connect to your server.
|
||||
address: 0.0.0.0
|
||||
|
||||
# The port that will Geyser will listen on for incoming Bedrock connections.
|
||||
# Since Minecraft: Bedrock Edition uses UDP, this port must allow UDP traffic.
|
||||
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.
|
||||
clone-remote-port: false
|
||||
|
||||
# Network settings for the Java server connection
|
||||
java:
|
||||
# What type of authentication Bedrock players will be checked against when logging into the Java server.
|
||||
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
|
||||
auth-type: online
|
||||
|
||||
# MOTD settings
|
||||
motd:
|
||||
# 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"
|
||||
primary-motd: Geyser
|
||||
secondary-motd: Another Geyser server.
|
||||
|
||||
# Whether Geyser should relay the MOTD from the Java server to Bedrock players.
|
||||
passthrough-motd: true
|
||||
|
||||
# Maximum amount of players that can connect.
|
||||
# This is only visual, and is only applied if passthrough-motd is disabled.
|
||||
max-players: 100
|
||||
|
||||
# Whether to relay the player count and max players from the Java server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
|
||||
# Whether to use server API methods to determine the Java server's MOTD and ping passthrough.
|
||||
# There is no need to disable this unless your MOTD or player count does not appear properly.
|
||||
integrated-ping-passthrough: true
|
||||
|
||||
# How often to ping the Java server to refresh MOTD and player count, in seconds.
|
||||
# Only relevant if integrated-ping-passthrough is disabled.
|
||||
ping-passthrough-interval: 3
|
||||
|
||||
# Gameplay options that affect Bedrock players
|
||||
gameplay:
|
||||
# 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
|
||||
|
||||
# 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://geysermc.org/img/external/cooldown_indicator.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
|
||||
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# 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.
|
||||
nether-roof-workaround: false
|
||||
|
||||
# Whether to show Bedrock Edition emotes to other Bedrock Edition players.
|
||||
show-emotes: 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.
|
||||
# This config option can be set to any Bedrock item identifier. If you want to set this to a custom item, make sure that you specify the item in the following format: "geyser_custom:<mapping-name>"
|
||||
unusable-space-block: minecraft:barrier
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
enable-custom-content: true
|
||||
|
||||
# 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
|
||||
|
||||
# Whether to automatically serve a resource pack that is required for some Geyser features to all connecting Bedrock players.
|
||||
# If enabled, force-resource-packs will be enabled.
|
||||
enable-integrated-pack: true
|
||||
|
||||
# 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
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
# If a player types in an unknown command, they will receive a message that states cheats are disabled.
|
||||
# Otherwise, commands work as expected.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
|
||||
# A value of 0 will disable all custom skulls.
|
||||
# Setting this to -1 will cause all custom skulls to be displayed regardless of distance or number.
|
||||
max-visible-custom-skulls: 0
|
||||
|
||||
# The radius in blocks around the player in which custom skulls are displayed.
|
||||
custom-skull-render-distance: 32
|
||||
|
||||
# The default locale if we don't have the one the client requested. If set to "system", the system's language will be used.
|
||||
default-locale: system
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: true
|
||||
|
||||
# For online mode authentication type only.
|
||||
# Stores a list of Bedrock player usernames 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
|
||||
|
||||
# For online mode authentication type only.
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# Advanced configuration options. These usually do not need modifications.
|
||||
advanced:
|
||||
# Specify how many days player skin images will be cached to disk to save downloading them from the internet.
|
||||
# A value of 0 is disabled. (Default: 0)
|
||||
cache-images: 0
|
||||
|
||||
# Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
|
||||
# a lot of scoreboard packets per second, this 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
|
||||
|
||||
# Whether Geyser should send team names in command suggestions.
|
||||
# Disable this if you have a lot of teams used that you don't need as suggestions.
|
||||
add-team-suggestions: true
|
||||
|
||||
# A list of remote resource pack urls to send to the Bedrock client for downloading.
|
||||
# The Bedrock client is very picky about how these are delivered - please see our wiki page for further info: https://geysermc.org/wiki/geyser/packs/
|
||||
resource-pack-urls: []
|
||||
|
||||
# Floodgate uses encryption to ensure use from authorized 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
|
||||
|
||||
# Advanced networking options for the Geyser to Java server connection
|
||||
java:
|
||||
# Whether to enable HAPROXY protocol when connecting to the Java server.
|
||||
# This is useful only when:
|
||||
# 1) Your Java server supports HAPROXY 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-haproxy-protocol: false
|
||||
|
||||
# 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, the remote address and port sections are ignored.
|
||||
# If disabled, expect performance decrease and latency increase.
|
||||
use-direct-connection: true
|
||||
|
||||
# Whether Geyser should attempt to disable packet compression (from the Java Server to Geyser) 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
|
||||
|
||||
# Advanced networking options for Geyser's Bedrock listener
|
||||
bedrock:
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# A value of 0 will broadcast the port specified above.
|
||||
# DO NOT change this unless Geyser runs on a different port than the one that is used to connect.
|
||||
broadcast-port: 0
|
||||
|
||||
# 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 expect HAPROXY protocol for connecting Bedrock clients.
|
||||
# This is useful only when you are running a UDP reverse proxy in front of your Geyser instance.
|
||||
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
|
||||
use-haproxy-protocol: false
|
||||
|
||||
# A list of allowed HAPROXY protocol speaking proxy IP addresses/subnets. Only effective when "use-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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
haproxy-protocol-whitelisted-ips: []
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1400
|
||||
|
||||
# This option disables the auth step Geyser performs for connecting Bedrock players.
|
||||
# It can be used to allow connections from ProxyPass and WaterdogPE. In these cases, make sure that users
|
||||
# cannot directly connect to this Geyser instance. See https://www.spigotmc.org/wiki/firewall-guide/ for
|
||||
# assistance - and use UDP instead of TCP.
|
||||
# Disabling Bedrock authentication for other use-cases is NOT SUPPORTED, as it allows anyone to spoof usernames, and is therefore a security risk.
|
||||
# All Floodgate functionality (including skin uploading and account linking) will also not work when this option is disabled.
|
||||
validate-bedrock-login: true
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: false
|
||||
|
||||
# Do not change!
|
||||
config-version: 5
|
||||
@@ -0,0 +1,236 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://geysermc.org/wiki
|
||||
#
|
||||
# NOTICE: See https://geysermc.org/wiki/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
# Network settings for the Bedrock listener
|
||||
bedrock:
|
||||
# The IP address that Geyser will bind on to listen for incoming Bedrock connections.
|
||||
# Generally, you should only change this if you want to limit what IPs can connect to your server.
|
||||
address: 0.0.0.0
|
||||
|
||||
# The port that will Geyser will listen on for incoming Bedrock connections.
|
||||
# Since Minecraft: Bedrock Edition uses UDP, this port must allow UDP traffic.
|
||||
port: 19132
|
||||
|
||||
# Network settings for the Java server connection
|
||||
java:
|
||||
# The IP address of the Java Edition server.
|
||||
address: 127.0.0.1
|
||||
|
||||
# The port of the Java Edition server.
|
||||
port: 25565
|
||||
|
||||
# What type of authentication Bedrock players will be checked against when logging into the Java server.
|
||||
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
|
||||
auth-type: online
|
||||
|
||||
# Whether to 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
|
||||
|
||||
# MOTD settings
|
||||
motd:
|
||||
# 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"
|
||||
primary-motd: Geyser
|
||||
secondary-motd: Another Geyser server.
|
||||
|
||||
# Whether Geyser should relay the MOTD from the Java server to Bedrock players.
|
||||
passthrough-motd: true
|
||||
|
||||
# Maximum amount of players that can connect.
|
||||
# This is only visual, and is only applied if passthrough-motd is disabled.
|
||||
max-players: 100
|
||||
|
||||
# Whether to relay the player count and max players from the Java server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
|
||||
# How often to ping the Java server to refresh MOTD and player count, in seconds.
|
||||
ping-passthrough-interval: 3
|
||||
|
||||
# Gameplay options that affect Bedrock players
|
||||
gameplay:
|
||||
# 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
|
||||
|
||||
# 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://geysermc.org/img/external/cooldown_indicator.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
|
||||
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# 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.
|
||||
nether-roof-workaround: false
|
||||
|
||||
# Whether to show Bedrock Edition emotes to other Bedrock Edition players.
|
||||
show-emotes: 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.
|
||||
# This config option can be set to any Bedrock item identifier. If you want to set this to a custom item, make sure that you specify the item in the following format: "geyser_custom:<mapping-name>"
|
||||
unusable-space-block: minecraft:barrier
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
enable-custom-content: true
|
||||
|
||||
# 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
|
||||
|
||||
# Whether to automatically serve a resource pack that is required for some Geyser features to all connecting Bedrock players.
|
||||
# If enabled, force-resource-packs will be enabled.
|
||||
enable-integrated-pack: true
|
||||
|
||||
# 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
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
# If a player types in an unknown command, they will receive a message that states cheats are disabled.
|
||||
# Otherwise, commands work as expected.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
|
||||
# A value of 0 will disable all custom skulls.
|
||||
# Setting this to -1 will cause all custom skulls to be displayed regardless of distance or number.
|
||||
max-visible-custom-skulls: 0
|
||||
|
||||
# The radius in blocks around the player in which custom skulls are displayed.
|
||||
custom-skull-render-distance: 32
|
||||
|
||||
# The default locale if we don't have the one the client requested. If set to "system", the system's language will be used.
|
||||
default-locale: system
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: true
|
||||
|
||||
# For online mode authentication type only.
|
||||
# Stores a list of Bedrock player usernames 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
|
||||
|
||||
# For online mode authentication type only.
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# Advanced configuration options. These usually do not need modifications.
|
||||
advanced:
|
||||
# Specify how many days player skin images will be cached to disk to save downloading them from the internet.
|
||||
# A value of 0 is disabled. (Default: 0)
|
||||
cache-images: 0
|
||||
|
||||
# Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
|
||||
# a lot of scoreboard packets per second, this 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
|
||||
|
||||
# Whether Geyser should send team names in command suggestions.
|
||||
# Disable this if you have a lot of teams used that you don't need as suggestions.
|
||||
add-team-suggestions: true
|
||||
|
||||
# A list of remote resource pack urls to send to the Bedrock client for downloading.
|
||||
# The Bedrock client is very picky about how these are delivered - please see our wiki page for further info: https://geysermc.org/wiki/geyser/packs/
|
||||
resource-pack-urls: []
|
||||
|
||||
# Floodgate uses encryption to ensure use from authorized 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
|
||||
|
||||
# Advanced networking options for the Geyser to Java server connection
|
||||
java:
|
||||
# Whether to enable HAPROXY protocol when connecting to the Java server.
|
||||
# This is useful only when:
|
||||
# 1) Your Java server supports HAPROXY 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-haproxy-protocol: false
|
||||
|
||||
# Advanced networking options for Geyser's Bedrock listener
|
||||
bedrock:
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# A value of 0 will broadcast the port specified above.
|
||||
# DO NOT change this unless Geyser runs on a different port than the one that is used to connect.
|
||||
broadcast-port: 0
|
||||
|
||||
# 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 expect HAPROXY protocol for connecting Bedrock clients.
|
||||
# This is useful only when you are running a UDP reverse proxy in front of your Geyser instance.
|
||||
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
|
||||
use-haproxy-protocol: false
|
||||
|
||||
# A list of allowed HAPROXY protocol speaking proxy IP addresses/subnets. Only effective when "use-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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
haproxy-protocol-whitelisted-ips: []
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1400
|
||||
|
||||
# This option disables the auth step Geyser performs for connecting Bedrock players.
|
||||
# It can be used to allow connections from ProxyPass and WaterdogPE. In these cases, make sure that users
|
||||
# cannot directly connect to this Geyser instance. See https://www.spigotmc.org/wiki/firewall-guide/ for
|
||||
# assistance - and use UDP instead of TCP.
|
||||
# Disabling Bedrock authentication for other use-cases is NOT SUPPORTED, as it allows anyone to spoof usernames, and is therefore a security risk.
|
||||
# All Floodgate functionality (including skin uploading and account linking) will also not work when this option is disabled.
|
||||
validate-bedrock-login: true
|
||||
|
||||
# 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
|
||||
enable-metrics: true
|
||||
|
||||
# The bstats metrics uuid. Do not touch!
|
||||
metrics-uuid: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: false
|
||||
|
||||
# Do not change!
|
||||
config-version: 5
|
||||
146
core/src/test/resources/configuration/chew/before.yml
Normal file
146
core/src/test/resources/configuration/chew/before.yml
Normal file
@@ -0,0 +1,146 @@
|
||||
# --------------------------------
|
||||
# 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. This is irrelevant if "passthrough-motd" is set to true
|
||||
motd1: "gsauta"
|
||||
motd2: "owo"
|
||||
# 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: "GSA"
|
||||
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: floodgate
|
||||
|
||||
# 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/MCPE username is the key for the Java server auth-info
|
||||
## this allows automatic configuration/login to the remote Java server
|
||||
## if you are brave/stupid enough to put your Mojang account info into
|
||||
## a config file
|
||||
#userAuths:
|
||||
# bluerkelp2: # MCPE/Xbox username
|
||||
# email: not_really_my_email_address_mr_minecrafter53267@gmail.com # Mojang account email address
|
||||
# password: "this isn't really my password"
|
||||
#
|
||||
# herpderp40300499303040503030300500293858393589:
|
||||
# email: herpderp@derpherp.com
|
||||
# password: dooooo
|
||||
|
||||
# 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
|
||||
|
||||
# Maximum amount of players that can connect
|
||||
max-players: 100
|
||||
|
||||
# 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: true
|
||||
|
||||
# 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 do not see a cooldown as they still use 1.8 combat
|
||||
show-cooldown: 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. While this feature does allow for a few
|
||||
# things such as block break animations to show up in creative mode and among others,
|
||||
# it is HIGHLY recommended you disable this on a production environment as it can eat
|
||||
# up a lot of RAM. However, 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
|
||||
|
||||
# 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 disconnect from the server if they don't
|
||||
# want to download the resource packs
|
||||
force-resource-packs: true
|
||||
|
||||
# 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: ff99f931-ff7f-4dfc-a027-4bd15edc5980
|
||||
|
||||
# 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
|
||||
|
||||
config-version: 4
|
||||
237
core/src/test/resources/configuration/chew/plugin.yml
Normal file
237
core/src/test/resources/configuration/chew/plugin.yml
Normal file
@@ -0,0 +1,237 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://geysermc.org/wiki
|
||||
#
|
||||
# NOTICE: See https://geysermc.org/wiki/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
# Network settings for the Bedrock listener
|
||||
bedrock:
|
||||
# The IP address that Geyser will bind on to listen for incoming Bedrock connections.
|
||||
# Generally, you should only change this if you want to limit what IPs can connect to your server.
|
||||
address: 0.0.0.0
|
||||
|
||||
# The port that will Geyser will listen on for incoming Bedrock connections.
|
||||
# Since Minecraft: Bedrock Edition uses UDP, this port must allow UDP traffic.
|
||||
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.
|
||||
clone-remote-port: false
|
||||
|
||||
# Network settings for the Java server connection
|
||||
java:
|
||||
# What type of authentication Bedrock players will be checked against when logging into the Java server.
|
||||
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
|
||||
auth-type: floodgate
|
||||
|
||||
# MOTD settings
|
||||
motd:
|
||||
# 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"
|
||||
primary-motd: gsauta
|
||||
secondary-motd: owo
|
||||
|
||||
# Whether Geyser should relay the MOTD from the Java server to Bedrock players.
|
||||
passthrough-motd: false
|
||||
|
||||
# Maximum amount of players that can connect.
|
||||
# This is only visual, and is only applied if passthrough-motd is disabled.
|
||||
max-players: 100
|
||||
|
||||
# Whether to relay the player count and max players from the Java server to Bedrock players.
|
||||
passthrough-player-counts: false
|
||||
|
||||
# Whether to use server API methods to determine the Java server's MOTD and ping passthrough.
|
||||
# There is no need to disable this unless your MOTD or player count does not appear properly.
|
||||
integrated-ping-passthrough: true
|
||||
|
||||
# How often to ping the Java server to refresh MOTD and player count, in seconds.
|
||||
# Only relevant if integrated-ping-passthrough is disabled.
|
||||
ping-passthrough-interval: 3
|
||||
|
||||
# Gameplay options that affect Bedrock players
|
||||
gameplay:
|
||||
# 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: GSA
|
||||
|
||||
# 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://geysermc.org/img/external/cooldown_indicator.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
|
||||
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# 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.
|
||||
nether-roof-workaround: false
|
||||
|
||||
# Whether to show Bedrock Edition emotes to other Bedrock Edition players.
|
||||
show-emotes: 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.
|
||||
# This config option can be set to any Bedrock item identifier. If you want to set this to a custom item, make sure that you specify the item in the following format: "geyser_custom:<mapping-name>"
|
||||
unusable-space-block: minecraft:barrier
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
enable-custom-content: true
|
||||
|
||||
# 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
|
||||
|
||||
# Whether to automatically serve a resource pack that is required for some Geyser features to all connecting Bedrock players.
|
||||
# If enabled, force-resource-packs will be enabled.
|
||||
enable-integrated-pack: true
|
||||
|
||||
# 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
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
# If a player types in an unknown command, they will receive a message that states cheats are disabled.
|
||||
# Otherwise, commands work as expected.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
|
||||
# A value of 0 will disable all custom skulls.
|
||||
# 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
|
||||
|
||||
# The default locale if we don't have the one the client requested. If set to "system", the system's language will be used.
|
||||
default-locale: system
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: true
|
||||
|
||||
# For online mode authentication type only.
|
||||
# Stores a list of Bedrock player usernames 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
|
||||
|
||||
# For online mode authentication type only.
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# Advanced configuration options. These usually do not need modifications.
|
||||
advanced:
|
||||
# Specify how many days player skin images will be cached to disk to save downloading them from the internet.
|
||||
# A value of 0 is disabled. (Default: 0)
|
||||
cache-images: 0
|
||||
|
||||
# Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
|
||||
# a lot of scoreboard packets per second, this 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
|
||||
|
||||
# Whether Geyser should send team names in command suggestions.
|
||||
# Disable this if you have a lot of teams used that you don't need as suggestions.
|
||||
add-team-suggestions: true
|
||||
|
||||
# A list of remote resource pack urls to send to the Bedrock client for downloading.
|
||||
# The Bedrock client is very picky about how these are delivered - please see our wiki page for further info: https://geysermc.org/wiki/geyser/packs/
|
||||
resource-pack-urls: []
|
||||
|
||||
# Floodgate uses encryption to ensure use from authorized 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
|
||||
|
||||
# Advanced networking options for the Geyser to Java server connection
|
||||
java:
|
||||
# Whether to enable HAPROXY protocol when connecting to the Java server.
|
||||
# This is useful only when:
|
||||
# 1) Your Java server supports HAPROXY 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-haproxy-protocol: false
|
||||
|
||||
# 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, the remote address and port sections are ignored.
|
||||
# If disabled, expect performance decrease and latency increase.
|
||||
use-direct-connection: true
|
||||
|
||||
# Whether Geyser should attempt to disable packet compression (from the Java Server to Geyser) 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
|
||||
|
||||
# Advanced networking options for Geyser's Bedrock listener
|
||||
bedrock:
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# A value of 0 will broadcast the port specified above.
|
||||
# DO NOT change this unless Geyser runs on a different port than the one that is used to connect.
|
||||
broadcast-port: 0
|
||||
|
||||
# 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 expect HAPROXY protocol for connecting Bedrock clients.
|
||||
# This is useful only when you are running a UDP reverse proxy in front of your Geyser instance.
|
||||
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
|
||||
use-haproxy-protocol: false
|
||||
|
||||
# A list of allowed HAPROXY protocol speaking proxy IP addresses/subnets. Only effective when "use-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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
haproxy-protocol-whitelisted-ips: []
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1400
|
||||
|
||||
# This option disables the auth step Geyser performs for connecting Bedrock players.
|
||||
# It can be used to allow connections from ProxyPass and WaterdogPE. In these cases, make sure that users
|
||||
# cannot directly connect to this Geyser instance. See https://www.spigotmc.org/wiki/firewall-guide/ for
|
||||
# assistance - and use UDP instead of TCP.
|
||||
# Disabling Bedrock authentication for other use-cases is NOT SUPPORTED, as it allows anyone to spoof usernames, and is therefore a security risk.
|
||||
# All Floodgate functionality (including skin uploading and account linking) will also not work when this option is disabled.
|
||||
validate-bedrock-login: true
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: false
|
||||
|
||||
# Do not change!
|
||||
config-version: 5
|
||||
236
core/src/test/resources/configuration/chew/remote.yml
Normal file
236
core/src/test/resources/configuration/chew/remote.yml
Normal file
@@ -0,0 +1,236 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://geysermc.org/wiki
|
||||
#
|
||||
# NOTICE: See https://geysermc.org/wiki/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
# Network settings for the Bedrock listener
|
||||
bedrock:
|
||||
# The IP address that Geyser will bind on to listen for incoming Bedrock connections.
|
||||
# Generally, you should only change this if you want to limit what IPs can connect to your server.
|
||||
address: 0.0.0.0
|
||||
|
||||
# The port that will Geyser will listen on for incoming Bedrock connections.
|
||||
# Since Minecraft: Bedrock Edition uses UDP, this port must allow UDP traffic.
|
||||
port: 19132
|
||||
|
||||
# Network settings for the Java server connection
|
||||
java:
|
||||
# The IP address of the Java Edition server.
|
||||
address: 127.0.0.1
|
||||
|
||||
# The port of the Java Edition server.
|
||||
port: 25565
|
||||
|
||||
# What type of authentication Bedrock players will be checked against when logging into the Java server.
|
||||
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
|
||||
auth-type: floodgate
|
||||
|
||||
# Whether to 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
|
||||
|
||||
# MOTD settings
|
||||
motd:
|
||||
# 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"
|
||||
primary-motd: gsauta
|
||||
secondary-motd: owo
|
||||
|
||||
# Whether Geyser should relay the MOTD from the Java server to Bedrock players.
|
||||
passthrough-motd: false
|
||||
|
||||
# Maximum amount of players that can connect.
|
||||
# This is only visual, and is only applied if passthrough-motd is disabled.
|
||||
max-players: 100
|
||||
|
||||
# Whether to relay the player count and max players from the Java server to Bedrock players.
|
||||
passthrough-player-counts: false
|
||||
|
||||
# How often to ping the Java server to refresh MOTD and player count, in seconds.
|
||||
ping-passthrough-interval: 3
|
||||
|
||||
# Gameplay options that affect Bedrock players
|
||||
gameplay:
|
||||
# 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: GSA
|
||||
|
||||
# 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://geysermc.org/img/external/cooldown_indicator.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
|
||||
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# 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.
|
||||
nether-roof-workaround: false
|
||||
|
||||
# Whether to show Bedrock Edition emotes to other Bedrock Edition players.
|
||||
show-emotes: 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.
|
||||
# This config option can be set to any Bedrock item identifier. If you want to set this to a custom item, make sure that you specify the item in the following format: "geyser_custom:<mapping-name>"
|
||||
unusable-space-block: minecraft:barrier
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
enable-custom-content: true
|
||||
|
||||
# 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
|
||||
|
||||
# Whether to automatically serve a resource pack that is required for some Geyser features to all connecting Bedrock players.
|
||||
# If enabled, force-resource-packs will be enabled.
|
||||
enable-integrated-pack: true
|
||||
|
||||
# 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
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
# If a player types in an unknown command, they will receive a message that states cheats are disabled.
|
||||
# Otherwise, commands work as expected.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
|
||||
# A value of 0 will disable all custom skulls.
|
||||
# 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
|
||||
|
||||
# The default locale if we don't have the one the client requested. If set to "system", the system's language will be used.
|
||||
default-locale: system
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: true
|
||||
|
||||
# For online mode authentication type only.
|
||||
# Stores a list of Bedrock player usernames 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
|
||||
|
||||
# For online mode authentication type only.
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# Advanced configuration options. These usually do not need modifications.
|
||||
advanced:
|
||||
# Specify how many days player skin images will be cached to disk to save downloading them from the internet.
|
||||
# A value of 0 is disabled. (Default: 0)
|
||||
cache-images: 0
|
||||
|
||||
# Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
|
||||
# a lot of scoreboard packets per second, this 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
|
||||
|
||||
# Whether Geyser should send team names in command suggestions.
|
||||
# Disable this if you have a lot of teams used that you don't need as suggestions.
|
||||
add-team-suggestions: true
|
||||
|
||||
# A list of remote resource pack urls to send to the Bedrock client for downloading.
|
||||
# The Bedrock client is very picky about how these are delivered - please see our wiki page for further info: https://geysermc.org/wiki/geyser/packs/
|
||||
resource-pack-urls: []
|
||||
|
||||
# Floodgate uses encryption to ensure use from authorized 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
|
||||
|
||||
# Advanced networking options for the Geyser to Java server connection
|
||||
java:
|
||||
# Whether to enable HAPROXY protocol when connecting to the Java server.
|
||||
# This is useful only when:
|
||||
# 1) Your Java server supports HAPROXY 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-haproxy-protocol: false
|
||||
|
||||
# Advanced networking options for Geyser's Bedrock listener
|
||||
bedrock:
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# A value of 0 will broadcast the port specified above.
|
||||
# DO NOT change this unless Geyser runs on a different port than the one that is used to connect.
|
||||
broadcast-port: 0
|
||||
|
||||
# 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 expect HAPROXY protocol for connecting Bedrock clients.
|
||||
# This is useful only when you are running a UDP reverse proxy in front of your Geyser instance.
|
||||
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
|
||||
use-haproxy-protocol: false
|
||||
|
||||
# A list of allowed HAPROXY protocol speaking proxy IP addresses/subnets. Only effective when "use-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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
haproxy-protocol-whitelisted-ips: []
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1400
|
||||
|
||||
# This option disables the auth step Geyser performs for connecting Bedrock players.
|
||||
# It can be used to allow connections from ProxyPass and WaterdogPE. In these cases, make sure that users
|
||||
# cannot directly connect to this Geyser instance. See https://www.spigotmc.org/wiki/firewall-guide/ for
|
||||
# assistance - and use UDP instead of TCP.
|
||||
# Disabling Bedrock authentication for other use-cases is NOT SUPPORTED, as it allows anyone to spoof usernames, and is therefore a security risk.
|
||||
# All Floodgate functionality (including skin uploading and account linking) will also not work when this option is disabled.
|
||||
validate-bedrock-login: true
|
||||
|
||||
# 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
|
||||
enable-metrics: true
|
||||
|
||||
# The bstats metrics uuid. Do not touch!
|
||||
metrics-uuid: ff99f931-ff7f-4dfc-a027-4bd15edc5980
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: false
|
||||
|
||||
# Do not change!
|
||||
config-version: 5
|
||||
219
core/src/test/resources/configuration/default/before.yml
Normal file
219
core/src/test/resources/configuration/default/before.yml
Normal file
@@ -0,0 +1,219 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://wiki.geysermc.org/
|
||||
#
|
||||
# NOTICE: See https://wiki.geysermc.org/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
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: 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. 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
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# DO NOT uncomment and change this unless Geyser runs on a different internal port than the one that is used to connect.
|
||||
# broadcast-port: 19132
|
||||
# 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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
#proxy-protocol-whitelisted-ips: [ "127.0.0.1", "172.18.0.0/16", "https://example.com/whitelist.txt" ]
|
||||
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: 25565
|
||||
# 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
|
||||
# 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: true
|
||||
# Relay the player count and max players from the remote server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
# 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 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 any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# 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.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# 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: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# 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
|
||||
237
core/src/test/resources/configuration/default/plugin.yml
Normal file
237
core/src/test/resources/configuration/default/plugin.yml
Normal file
@@ -0,0 +1,237 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://geysermc.org/wiki
|
||||
#
|
||||
# NOTICE: See https://geysermc.org/wiki/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
# Network settings for the Bedrock listener
|
||||
bedrock:
|
||||
# The IP address that Geyser will bind on to listen for incoming Bedrock connections.
|
||||
# Generally, you should only change this if you want to limit what IPs can connect to your server.
|
||||
address: 0.0.0.0
|
||||
|
||||
# The port that will Geyser will listen on for incoming Bedrock connections.
|
||||
# Since Minecraft: Bedrock Edition uses UDP, this port must allow UDP traffic.
|
||||
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.
|
||||
clone-remote-port: false
|
||||
|
||||
# Network settings for the Java server connection
|
||||
java:
|
||||
# What type of authentication Bedrock players will be checked against when logging into the Java server.
|
||||
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
|
||||
auth-type: online
|
||||
|
||||
# MOTD settings
|
||||
motd:
|
||||
# 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"
|
||||
primary-motd: Geyser
|
||||
secondary-motd: Another Geyser server.
|
||||
|
||||
# Whether Geyser should relay the MOTD from the Java server to Bedrock players.
|
||||
passthrough-motd: true
|
||||
|
||||
# Maximum amount of players that can connect.
|
||||
# This is only visual, and is only applied if passthrough-motd is disabled.
|
||||
max-players: 100
|
||||
|
||||
# Whether to relay the player count and max players from the Java server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
|
||||
# Whether to use server API methods to determine the Java server's MOTD and ping passthrough.
|
||||
# There is no need to disable this unless your MOTD or player count does not appear properly.
|
||||
integrated-ping-passthrough: true
|
||||
|
||||
# How often to ping the Java server to refresh MOTD and player count, in seconds.
|
||||
# Only relevant if integrated-ping-passthrough is disabled.
|
||||
ping-passthrough-interval: 3
|
||||
|
||||
# Gameplay options that affect Bedrock players
|
||||
gameplay:
|
||||
# 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
|
||||
|
||||
# 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://geysermc.org/img/external/cooldown_indicator.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
|
||||
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# 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.
|
||||
nether-roof-workaround: false
|
||||
|
||||
# Whether to show Bedrock Edition emotes to other Bedrock Edition players.
|
||||
show-emotes: 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.
|
||||
# This config option can be set to any Bedrock item identifier. If you want to set this to a custom item, make sure that you specify the item in the following format: "geyser_custom:<mapping-name>"
|
||||
unusable-space-block: minecraft:barrier
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
enable-custom-content: true
|
||||
|
||||
# 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
|
||||
|
||||
# Whether to automatically serve a resource pack that is required for some Geyser features to all connecting Bedrock players.
|
||||
# If enabled, force-resource-packs will be enabled.
|
||||
enable-integrated-pack: true
|
||||
|
||||
# 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
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
# If a player types in an unknown command, they will receive a message that states cheats are disabled.
|
||||
# Otherwise, commands work as expected.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
|
||||
# A value of 0 will disable all custom skulls.
|
||||
# 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
|
||||
|
||||
# The default locale if we don't have the one the client requested. If set to "system", the system's language will be used.
|
||||
default-locale: system
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: true
|
||||
|
||||
# For online mode authentication type only.
|
||||
# Stores a list of Bedrock player usernames 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
|
||||
|
||||
# For online mode authentication type only.
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# Advanced configuration options. These usually do not need modifications.
|
||||
advanced:
|
||||
# Specify how many days player skin images will be cached to disk to save downloading them from the internet.
|
||||
# A value of 0 is disabled. (Default: 0)
|
||||
cache-images: 0
|
||||
|
||||
# Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
|
||||
# a lot of scoreboard packets per second, this 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
|
||||
|
||||
# Whether Geyser should send team names in command suggestions.
|
||||
# Disable this if you have a lot of teams used that you don't need as suggestions.
|
||||
add-team-suggestions: true
|
||||
|
||||
# A list of remote resource pack urls to send to the Bedrock client for downloading.
|
||||
# The Bedrock client is very picky about how these are delivered - please see our wiki page for further info: https://geysermc.org/wiki/geyser/packs/
|
||||
resource-pack-urls: []
|
||||
|
||||
# Floodgate uses encryption to ensure use from authorized 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
|
||||
|
||||
# Advanced networking options for the Geyser to Java server connection
|
||||
java:
|
||||
# Whether to enable HAPROXY protocol when connecting to the Java server.
|
||||
# This is useful only when:
|
||||
# 1) Your Java server supports HAPROXY 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-haproxy-protocol: false
|
||||
|
||||
# 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, the remote address and port sections are ignored.
|
||||
# If disabled, expect performance decrease and latency increase.
|
||||
use-direct-connection: true
|
||||
|
||||
# Whether Geyser should attempt to disable packet compression (from the Java Server to Geyser) 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
|
||||
|
||||
# Advanced networking options for Geyser's Bedrock listener
|
||||
bedrock:
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# A value of 0 will broadcast the port specified above.
|
||||
# DO NOT change this unless Geyser runs on a different port than the one that is used to connect.
|
||||
broadcast-port: 0
|
||||
|
||||
# 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 expect HAPROXY protocol for connecting Bedrock clients.
|
||||
# This is useful only when you are running a UDP reverse proxy in front of your Geyser instance.
|
||||
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
|
||||
use-haproxy-protocol: false
|
||||
|
||||
# A list of allowed HAPROXY protocol speaking proxy IP addresses/subnets. Only effective when "use-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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
haproxy-protocol-whitelisted-ips: []
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1400
|
||||
|
||||
# This option disables the auth step Geyser performs for connecting Bedrock players.
|
||||
# It can be used to allow connections from ProxyPass and WaterdogPE. In these cases, make sure that users
|
||||
# cannot directly connect to this Geyser instance. See https://www.spigotmc.org/wiki/firewall-guide/ for
|
||||
# assistance - and use UDP instead of TCP.
|
||||
# Disabling Bedrock authentication for other use-cases is NOT SUPPORTED, as it allows anyone to spoof usernames, and is therefore a security risk.
|
||||
# All Floodgate functionality (including skin uploading and account linking) will also not work when this option is disabled.
|
||||
validate-bedrock-login: true
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: false
|
||||
|
||||
# Do not change!
|
||||
config-version: 5
|
||||
236
core/src/test/resources/configuration/default/remote.yml
Normal file
236
core/src/test/resources/configuration/default/remote.yml
Normal file
@@ -0,0 +1,236 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://geysermc.org/wiki
|
||||
#
|
||||
# NOTICE: See https://geysermc.org/wiki/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
# Network settings for the Bedrock listener
|
||||
bedrock:
|
||||
# The IP address that Geyser will bind on to listen for incoming Bedrock connections.
|
||||
# Generally, you should only change this if you want to limit what IPs can connect to your server.
|
||||
address: 0.0.0.0
|
||||
|
||||
# The port that will Geyser will listen on for incoming Bedrock connections.
|
||||
# Since Minecraft: Bedrock Edition uses UDP, this port must allow UDP traffic.
|
||||
port: 19132
|
||||
|
||||
# Network settings for the Java server connection
|
||||
java:
|
||||
# The IP address of the Java Edition server.
|
||||
address: 127.0.0.1
|
||||
|
||||
# The port of the Java Edition server.
|
||||
port: 25565
|
||||
|
||||
# What type of authentication Bedrock players will be checked against when logging into the Java server.
|
||||
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
|
||||
auth-type: online
|
||||
|
||||
# Whether to 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
|
||||
|
||||
# MOTD settings
|
||||
motd:
|
||||
# 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"
|
||||
primary-motd: Geyser
|
||||
secondary-motd: Another Geyser server.
|
||||
|
||||
# Whether Geyser should relay the MOTD from the Java server to Bedrock players.
|
||||
passthrough-motd: true
|
||||
|
||||
# Maximum amount of players that can connect.
|
||||
# This is only visual, and is only applied if passthrough-motd is disabled.
|
||||
max-players: 100
|
||||
|
||||
# Whether to relay the player count and max players from the Java server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
|
||||
# How often to ping the Java server to refresh MOTD and player count, in seconds.
|
||||
ping-passthrough-interval: 3
|
||||
|
||||
# Gameplay options that affect Bedrock players
|
||||
gameplay:
|
||||
# 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
|
||||
|
||||
# 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://geysermc.org/img/external/cooldown_indicator.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
|
||||
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# 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.
|
||||
nether-roof-workaround: false
|
||||
|
||||
# Whether to show Bedrock Edition emotes to other Bedrock Edition players.
|
||||
show-emotes: 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.
|
||||
# This config option can be set to any Bedrock item identifier. If you want to set this to a custom item, make sure that you specify the item in the following format: "geyser_custom:<mapping-name>"
|
||||
unusable-space-block: minecraft:barrier
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
enable-custom-content: true
|
||||
|
||||
# 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
|
||||
|
||||
# Whether to automatically serve a resource pack that is required for some Geyser features to all connecting Bedrock players.
|
||||
# If enabled, force-resource-packs will be enabled.
|
||||
enable-integrated-pack: true
|
||||
|
||||
# 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
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
# If a player types in an unknown command, they will receive a message that states cheats are disabled.
|
||||
# Otherwise, commands work as expected.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
|
||||
# A value of 0 will disable all custom skulls.
|
||||
# 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
|
||||
|
||||
# The default locale if we don't have the one the client requested. If set to "system", the system's language will be used.
|
||||
default-locale: system
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: true
|
||||
|
||||
# For online mode authentication type only.
|
||||
# Stores a list of Bedrock player usernames 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
|
||||
|
||||
# For online mode authentication type only.
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# Advanced configuration options. These usually do not need modifications.
|
||||
advanced:
|
||||
# Specify how many days player skin images will be cached to disk to save downloading them from the internet.
|
||||
# A value of 0 is disabled. (Default: 0)
|
||||
cache-images: 0
|
||||
|
||||
# Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
|
||||
# a lot of scoreboard packets per second, this 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
|
||||
|
||||
# Whether Geyser should send team names in command suggestions.
|
||||
# Disable this if you have a lot of teams used that you don't need as suggestions.
|
||||
add-team-suggestions: true
|
||||
|
||||
# A list of remote resource pack urls to send to the Bedrock client for downloading.
|
||||
# The Bedrock client is very picky about how these are delivered - please see our wiki page for further info: https://geysermc.org/wiki/geyser/packs/
|
||||
resource-pack-urls: []
|
||||
|
||||
# Floodgate uses encryption to ensure use from authorized 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
|
||||
|
||||
# Advanced networking options for the Geyser to Java server connection
|
||||
java:
|
||||
# Whether to enable HAPROXY protocol when connecting to the Java server.
|
||||
# This is useful only when:
|
||||
# 1) Your Java server supports HAPROXY 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-haproxy-protocol: false
|
||||
|
||||
# Advanced networking options for Geyser's Bedrock listener
|
||||
bedrock:
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# A value of 0 will broadcast the port specified above.
|
||||
# DO NOT change this unless Geyser runs on a different port than the one that is used to connect.
|
||||
broadcast-port: 0
|
||||
|
||||
# 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 expect HAPROXY protocol for connecting Bedrock clients.
|
||||
# This is useful only when you are running a UDP reverse proxy in front of your Geyser instance.
|
||||
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
|
||||
use-haproxy-protocol: false
|
||||
|
||||
# A list of allowed HAPROXY protocol speaking proxy IP addresses/subnets. Only effective when "use-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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
haproxy-protocol-whitelisted-ips: []
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1400
|
||||
|
||||
# This option disables the auth step Geyser performs for connecting Bedrock players.
|
||||
# It can be used to allow connections from ProxyPass and WaterdogPE. In these cases, make sure that users
|
||||
# cannot directly connect to this Geyser instance. See https://www.spigotmc.org/wiki/firewall-guide/ for
|
||||
# assistance - and use UDP instead of TCP.
|
||||
# Disabling Bedrock authentication for other use-cases is NOT SUPPORTED, as it allows anyone to spoof usernames, and is therefore a security risk.
|
||||
# All Floodgate functionality (including skin uploading and account linking) will also not work when this option is disabled.
|
||||
validate-bedrock-login: true
|
||||
|
||||
# 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
|
||||
enable-metrics: true
|
||||
|
||||
# The bstats metrics uuid. Do not touch!
|
||||
metrics-uuid: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: false
|
||||
|
||||
# Do not change!
|
||||
config-version: 5
|
||||
219
core/src/test/resources/configuration/invalid/invalid_enum.yml
Normal file
219
core/src/test/resources/configuration/invalid/invalid_enum.yml
Normal file
@@ -0,0 +1,219 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://wiki.geysermc.org/
|
||||
#
|
||||
# NOTICE: See https://wiki.geysermc.org/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
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: 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. 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
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# DO NOT uncomment and change this unless Geyser runs on a different internal port than the one that is used to connect.
|
||||
# broadcast-port: 19132
|
||||
# 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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
#proxy-protocol-whitelisted-ips: [ "127.0.0.1", "172.18.0.0/16", "https://example.com/whitelist.txt" ]
|
||||
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: 25565
|
||||
# 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
|
||||
# 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: true
|
||||
# Relay the player count and max players from the remote server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
# 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 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: invalidEnum
|
||||
|
||||
# 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 any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# 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.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# 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: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# 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
|
||||
219
core/src/test/resources/configuration/invalid/invalid_remote.yml
Normal file
219
core/src/test/resources/configuration/invalid/invalid_remote.yml
Normal file
@@ -0,0 +1,219 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://wiki.geysermc.org/
|
||||
#
|
||||
# NOTICE: See https://wiki.geysermc.org/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
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: 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. 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
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# DO NOT uncomment and change this unless Geyser runs on a different internal port than the one that is used to connect.
|
||||
# broadcast-port: 19132
|
||||
# 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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
#proxy-protocol-whitelisted-ips: [ "127.0.0.1", "172.18.0.0/16", "https://example.com/whitelist.txt" ]
|
||||
remote:auto
|
||||
# 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: 25565
|
||||
# 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
|
||||
# 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: true
|
||||
# Relay the player count and max players from the remote server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
# 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 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 any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# 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.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# 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: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# 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
|
||||
@@ -0,0 +1,219 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://wiki.geysermc.org/
|
||||
#
|
||||
# NOTICE: See https://wiki.geysermc.org/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
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: 0.0.0.0
|
||||
# The port that will listen for connections
|
||||
port: 99999
|
||||
# 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
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# DO NOT uncomment and change this unless Geyser runs on a different internal port than the one that is used to connect.
|
||||
# broadcast-port: 19132
|
||||
# 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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
#proxy-protocol-whitelisted-ips: [ "127.0.0.1", "172.18.0.0/16", "https://example.com/whitelist.txt" ]
|
||||
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: 25565
|
||||
# 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
|
||||
# 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: true
|
||||
# Relay the player count and max players from the remote server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
# 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 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 any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# 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.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# 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: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# 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
|
||||
219
core/src/test/resources/configuration/legacy/before.yml
Normal file
219
core/src/test/resources/configuration/legacy/before.yml
Normal file
@@ -0,0 +1,219 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://wiki.geysermc.org/
|
||||
#
|
||||
# NOTICE: See https://wiki.geysermc.org/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
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: 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. 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
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# DO NOT uncomment and change this unless Geyser runs on a different internal port than the one that is used to connect.
|
||||
# broadcast-port: 19132
|
||||
# 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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
#proxy-protocol-whitelisted-ips: [ "127.0.0.1", "172.18.0.0/16", "https://example.com/whitelist.txt" ]
|
||||
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: 25565
|
||||
# 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
|
||||
# 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: public-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: true
|
||||
# Relay the player count and max players from the remote server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
# 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 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: true
|
||||
|
||||
# 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 any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# 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.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# 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: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# 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: true
|
||||
|
||||
# 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
|
||||
237
core/src/test/resources/configuration/legacy/plugin.yml
Normal file
237
core/src/test/resources/configuration/legacy/plugin.yml
Normal file
@@ -0,0 +1,237 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://geysermc.org/wiki
|
||||
#
|
||||
# NOTICE: See https://geysermc.org/wiki/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
# Network settings for the Bedrock listener
|
||||
bedrock:
|
||||
# The IP address that Geyser will bind on to listen for incoming Bedrock connections.
|
||||
# Generally, you should only change this if you want to limit what IPs can connect to your server.
|
||||
address: 0.0.0.0
|
||||
|
||||
# The port that will Geyser will listen on for incoming Bedrock connections.
|
||||
# Since Minecraft: Bedrock Edition uses UDP, this port must allow UDP traffic.
|
||||
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.
|
||||
clone-remote-port: false
|
||||
|
||||
# Network settings for the Java server connection
|
||||
java:
|
||||
# What type of authentication Bedrock players will be checked against when logging into the Java server.
|
||||
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
|
||||
auth-type: online
|
||||
|
||||
# MOTD settings
|
||||
motd:
|
||||
# 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"
|
||||
primary-motd: Geyser
|
||||
secondary-motd: Another Geyser server.
|
||||
|
||||
# Whether Geyser should relay the MOTD from the Java server to Bedrock players.
|
||||
passthrough-motd: true
|
||||
|
||||
# Maximum amount of players that can connect.
|
||||
# This is only visual, and is only applied if passthrough-motd is disabled.
|
||||
max-players: 100
|
||||
|
||||
# Whether to relay the player count and max players from the Java server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
|
||||
# Whether to use server API methods to determine the Java server's MOTD and ping passthrough.
|
||||
# There is no need to disable this unless your MOTD or player count does not appear properly.
|
||||
integrated-ping-passthrough: true
|
||||
|
||||
# How often to ping the Java server to refresh MOTD and player count, in seconds.
|
||||
# Only relevant if integrated-ping-passthrough is disabled.
|
||||
ping-passthrough-interval: 3
|
||||
|
||||
# Gameplay options that affect Bedrock players
|
||||
gameplay:
|
||||
# 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
|
||||
|
||||
# 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://geysermc.org/img/external/cooldown_indicator.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
|
||||
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# 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.
|
||||
nether-roof-workaround: false
|
||||
|
||||
# Whether to show Bedrock Edition emotes to other Bedrock Edition players.
|
||||
show-emotes: 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.
|
||||
# This config option can be set to any Bedrock item identifier. If you want to set this to a custom item, make sure that you specify the item in the following format: "geyser_custom:<mapping-name>"
|
||||
unusable-space-block: minecraft:barrier
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
enable-custom-content: true
|
||||
|
||||
# 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
|
||||
|
||||
# Whether to automatically serve a resource pack that is required for some Geyser features to all connecting Bedrock players.
|
||||
# If enabled, force-resource-packs will be enabled.
|
||||
enable-integrated-pack: true
|
||||
|
||||
# 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
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
# If a player types in an unknown command, they will receive a message that states cheats are disabled.
|
||||
# Otherwise, commands work as expected.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
|
||||
# A value of 0 will disable all custom skulls.
|
||||
# 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
|
||||
|
||||
# The default locale if we don't have the one the client requested. If set to "system", the system's language will be used.
|
||||
default-locale: system
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: true
|
||||
|
||||
# For online mode authentication type only.
|
||||
# Stores a list of Bedrock player usernames 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
|
||||
|
||||
# For online mode authentication type only.
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# Advanced configuration options. These usually do not need modifications.
|
||||
advanced:
|
||||
# Specify how many days player skin images will be cached to disk to save downloading them from the internet.
|
||||
# A value of 0 is disabled. (Default: 0)
|
||||
cache-images: 0
|
||||
|
||||
# Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
|
||||
# a lot of scoreboard packets per second, this 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
|
||||
|
||||
# Whether Geyser should send team names in command suggestions.
|
||||
# Disable this if you have a lot of teams used that you don't need as suggestions.
|
||||
add-team-suggestions: true
|
||||
|
||||
# A list of remote resource pack urls to send to the Bedrock client for downloading.
|
||||
# The Bedrock client is very picky about how these are delivered - please see our wiki page for further info: https://geysermc.org/wiki/geyser/packs/
|
||||
resource-pack-urls: []
|
||||
|
||||
# Floodgate uses encryption to ensure use from authorized 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
|
||||
|
||||
# Advanced networking options for the Geyser to Java server connection
|
||||
java:
|
||||
# Whether to enable HAPROXY protocol when connecting to the Java server.
|
||||
# This is useful only when:
|
||||
# 1) Your Java server supports HAPROXY 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-haproxy-protocol: false
|
||||
|
||||
# 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, the remote address and port sections are ignored.
|
||||
# If disabled, expect performance decrease and latency increase.
|
||||
use-direct-connection: true
|
||||
|
||||
# Whether Geyser should attempt to disable packet compression (from the Java Server to Geyser) 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
|
||||
|
||||
# Advanced networking options for Geyser's Bedrock listener
|
||||
bedrock:
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# A value of 0 will broadcast the port specified above.
|
||||
# DO NOT change this unless Geyser runs on a different port than the one that is used to connect.
|
||||
broadcast-port: 0
|
||||
|
||||
# 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 expect HAPROXY protocol for connecting Bedrock clients.
|
||||
# This is useful only when you are running a UDP reverse proxy in front of your Geyser instance.
|
||||
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
|
||||
use-haproxy-protocol: false
|
||||
|
||||
# A list of allowed HAPROXY protocol speaking proxy IP addresses/subnets. Only effective when "use-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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
haproxy-protocol-whitelisted-ips: []
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1400
|
||||
|
||||
# This option disables the auth step Geyser performs for connecting Bedrock players.
|
||||
# It can be used to allow connections from ProxyPass and WaterdogPE. In these cases, make sure that users
|
||||
# cannot directly connect to this Geyser instance. See https://www.spigotmc.org/wiki/firewall-guide/ for
|
||||
# assistance - and use UDP instead of TCP.
|
||||
# Disabling Bedrock authentication for other use-cases is NOT SUPPORTED, as it allows anyone to spoof usernames, and is therefore a security risk.
|
||||
# All Floodgate functionality (including skin uploading and account linking) will also not work when this option is disabled.
|
||||
validate-bedrock-login: true
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: false
|
||||
|
||||
# Do not change!
|
||||
config-version: 5
|
||||
236
core/src/test/resources/configuration/legacy/remote.yml
Normal file
236
core/src/test/resources/configuration/legacy/remote.yml
Normal file
@@ -0,0 +1,236 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://geysermc.org/wiki
|
||||
#
|
||||
# NOTICE: See https://geysermc.org/wiki/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
# Network settings for the Bedrock listener
|
||||
bedrock:
|
||||
# The IP address that Geyser will bind on to listen for incoming Bedrock connections.
|
||||
# Generally, you should only change this if you want to limit what IPs can connect to your server.
|
||||
address: 0.0.0.0
|
||||
|
||||
# The port that will Geyser will listen on for incoming Bedrock connections.
|
||||
# Since Minecraft: Bedrock Edition uses UDP, this port must allow UDP traffic.
|
||||
port: 19132
|
||||
|
||||
# Network settings for the Java server connection
|
||||
java:
|
||||
# The IP address of the Java Edition server.
|
||||
address: 127.0.0.1
|
||||
|
||||
# The port of the Java Edition server.
|
||||
port: 25565
|
||||
|
||||
# What type of authentication Bedrock players will be checked against when logging into the Java server.
|
||||
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
|
||||
auth-type: online
|
||||
|
||||
# Whether to 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
|
||||
|
||||
# MOTD settings
|
||||
motd:
|
||||
# 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"
|
||||
primary-motd: Geyser
|
||||
secondary-motd: Another Geyser server.
|
||||
|
||||
# Whether Geyser should relay the MOTD from the Java server to Bedrock players.
|
||||
passthrough-motd: true
|
||||
|
||||
# Maximum amount of players that can connect.
|
||||
# This is only visual, and is only applied if passthrough-motd is disabled.
|
||||
max-players: 100
|
||||
|
||||
# Whether to relay the player count and max players from the Java server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
|
||||
# How often to ping the Java server to refresh MOTD and player count, in seconds.
|
||||
ping-passthrough-interval: 3
|
||||
|
||||
# Gameplay options that affect Bedrock players
|
||||
gameplay:
|
||||
# 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
|
||||
|
||||
# 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://geysermc.org/img/external/cooldown_indicator.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
|
||||
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# 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.
|
||||
nether-roof-workaround: false
|
||||
|
||||
# Whether to show Bedrock Edition emotes to other Bedrock Edition players.
|
||||
show-emotes: 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.
|
||||
# This config option can be set to any Bedrock item identifier. If you want to set this to a custom item, make sure that you specify the item in the following format: "geyser_custom:<mapping-name>"
|
||||
unusable-space-block: minecraft:barrier
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
enable-custom-content: true
|
||||
|
||||
# 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
|
||||
|
||||
# Whether to automatically serve a resource pack that is required for some Geyser features to all connecting Bedrock players.
|
||||
# If enabled, force-resource-packs will be enabled.
|
||||
enable-integrated-pack: true
|
||||
|
||||
# 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
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
# If a player types in an unknown command, they will receive a message that states cheats are disabled.
|
||||
# Otherwise, commands work as expected.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
|
||||
# A value of 0 will disable all custom skulls.
|
||||
# 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
|
||||
|
||||
# The default locale if we don't have the one the client requested. If set to "system", the system's language will be used.
|
||||
default-locale: system
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: true
|
||||
|
||||
# For online mode authentication type only.
|
||||
# Stores a list of Bedrock player usernames 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
|
||||
|
||||
# For online mode authentication type only.
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# Advanced configuration options. These usually do not need modifications.
|
||||
advanced:
|
||||
# Specify how many days player skin images will be cached to disk to save downloading them from the internet.
|
||||
# A value of 0 is disabled. (Default: 0)
|
||||
cache-images: 0
|
||||
|
||||
# Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
|
||||
# a lot of scoreboard packets per second, this 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
|
||||
|
||||
# Whether Geyser should send team names in command suggestions.
|
||||
# Disable this if you have a lot of teams used that you don't need as suggestions.
|
||||
add-team-suggestions: true
|
||||
|
||||
# A list of remote resource pack urls to send to the Bedrock client for downloading.
|
||||
# The Bedrock client is very picky about how these are delivered - please see our wiki page for further info: https://geysermc.org/wiki/geyser/packs/
|
||||
resource-pack-urls: []
|
||||
|
||||
# Floodgate uses encryption to ensure use from authorized 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
|
||||
|
||||
# Advanced networking options for the Geyser to Java server connection
|
||||
java:
|
||||
# Whether to enable HAPROXY protocol when connecting to the Java server.
|
||||
# This is useful only when:
|
||||
# 1) Your Java server supports HAPROXY 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-haproxy-protocol: false
|
||||
|
||||
# Advanced networking options for Geyser's Bedrock listener
|
||||
bedrock:
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# A value of 0 will broadcast the port specified above.
|
||||
# DO NOT change this unless Geyser runs on a different port than the one that is used to connect.
|
||||
broadcast-port: 0
|
||||
|
||||
# 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 expect HAPROXY protocol for connecting Bedrock clients.
|
||||
# This is useful only when you are running a UDP reverse proxy in front of your Geyser instance.
|
||||
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
|
||||
use-haproxy-protocol: false
|
||||
|
||||
# A list of allowed HAPROXY protocol speaking proxy IP addresses/subnets. Only effective when "use-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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
haproxy-protocol-whitelisted-ips: []
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1400
|
||||
|
||||
# This option disables the auth step Geyser performs for connecting Bedrock players.
|
||||
# It can be used to allow connections from ProxyPass and WaterdogPE. In these cases, make sure that users
|
||||
# cannot directly connect to this Geyser instance. See https://www.spigotmc.org/wiki/firewall-guide/ for
|
||||
# assistance - and use UDP instead of TCP.
|
||||
# Disabling Bedrock authentication for other use-cases is NOT SUPPORTED, as it allows anyone to spoof usernames, and is therefore a security risk.
|
||||
# All Floodgate functionality (including skin uploading and account linking) will also not work when this option is disabled.
|
||||
validate-bedrock-login: true
|
||||
|
||||
# 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
|
||||
enable-metrics: true
|
||||
|
||||
# The bstats metrics uuid. Do not touch!
|
||||
metrics-uuid: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: false
|
||||
|
||||
# Do not change!
|
||||
config-version: 5
|
||||
@@ -0,0 +1,219 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://wiki.geysermc.org/
|
||||
#
|
||||
# NOTICE: See https://wiki.geysermc.org/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
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: 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. 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
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# DO NOT uncomment and change this unless Geyser runs on a different internal port than the one that is used to connect.
|
||||
# broadcast-port: 19132
|
||||
# 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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
#proxy-protocol-whitelisted-ips: [ "127.0.0.1", "172.18.0.0/16", "https://example.com/whitelist.txt" ]
|
||||
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: 25565
|
||||
# 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
|
||||
# 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: true
|
||||
# Relay the player count and max players from the remote server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
# 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 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: "no-emotes"
|
||||
|
||||
# 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: false
|
||||
|
||||
# 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 any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# 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.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# 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: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# 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
|
||||
@@ -0,0 +1,237 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://geysermc.org/wiki
|
||||
#
|
||||
# NOTICE: See https://geysermc.org/wiki/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
# Network settings for the Bedrock listener
|
||||
bedrock:
|
||||
# The IP address that Geyser will bind on to listen for incoming Bedrock connections.
|
||||
# Generally, you should only change this if you want to limit what IPs can connect to your server.
|
||||
address: 0.0.0.0
|
||||
|
||||
# The port that will Geyser will listen on for incoming Bedrock connections.
|
||||
# Since Minecraft: Bedrock Edition uses UDP, this port must allow UDP traffic.
|
||||
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.
|
||||
clone-remote-port: false
|
||||
|
||||
# Network settings for the Java server connection
|
||||
java:
|
||||
# What type of authentication Bedrock players will be checked against when logging into the Java server.
|
||||
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
|
||||
auth-type: online
|
||||
|
||||
# MOTD settings
|
||||
motd:
|
||||
# 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"
|
||||
primary-motd: Geyser
|
||||
secondary-motd: Another Geyser server.
|
||||
|
||||
# Whether Geyser should relay the MOTD from the Java server to Bedrock players.
|
||||
passthrough-motd: true
|
||||
|
||||
# Maximum amount of players that can connect.
|
||||
# This is only visual, and is only applied if passthrough-motd is disabled.
|
||||
max-players: 100
|
||||
|
||||
# Whether to relay the player count and max players from the Java server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
|
||||
# Whether to use server API methods to determine the Java server's MOTD and ping passthrough.
|
||||
# There is no need to disable this unless your MOTD or player count does not appear properly.
|
||||
integrated-ping-passthrough: true
|
||||
|
||||
# How often to ping the Java server to refresh MOTD and player count, in seconds.
|
||||
# Only relevant if integrated-ping-passthrough is disabled.
|
||||
ping-passthrough-interval: 3
|
||||
|
||||
# Gameplay options that affect Bedrock players
|
||||
gameplay:
|
||||
# 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
|
||||
|
||||
# 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://geysermc.org/img/external/cooldown_indicator.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
|
||||
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# 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.
|
||||
nether-roof-workaround: false
|
||||
|
||||
# Whether to show Bedrock Edition emotes to other Bedrock Edition players.
|
||||
show-emotes: false
|
||||
|
||||
# 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.
|
||||
# This config option can be set to any Bedrock item identifier. If you want to set this to a custom item, make sure that you specify the item in the following format: "geyser_custom:<mapping-name>"
|
||||
unusable-space-block: minecraft:barrier
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
enable-custom-content: true
|
||||
|
||||
# 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
|
||||
|
||||
# Whether to automatically serve a resource pack that is required for some Geyser features to all connecting Bedrock players.
|
||||
# If enabled, force-resource-packs will be enabled.
|
||||
enable-integrated-pack: true
|
||||
|
||||
# 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
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
# If a player types in an unknown command, they will receive a message that states cheats are disabled.
|
||||
# Otherwise, commands work as expected.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
|
||||
# A value of 0 will disable all custom skulls.
|
||||
# Setting this to -1 will cause all custom skulls to be displayed regardless of distance or number.
|
||||
max-visible-custom-skulls: 0
|
||||
|
||||
# The radius in blocks around the player in which custom skulls are displayed.
|
||||
custom-skull-render-distance: 32
|
||||
|
||||
# The default locale if we don't have the one the client requested. If set to "system", the system's language will be used.
|
||||
default-locale: system
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: true
|
||||
|
||||
# For online mode authentication type only.
|
||||
# Stores a list of Bedrock player usernames 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
|
||||
|
||||
# For online mode authentication type only.
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# Advanced configuration options. These usually do not need modifications.
|
||||
advanced:
|
||||
# Specify how many days player skin images will be cached to disk to save downloading them from the internet.
|
||||
# A value of 0 is disabled. (Default: 0)
|
||||
cache-images: 0
|
||||
|
||||
# Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
|
||||
# a lot of scoreboard packets per second, this 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
|
||||
|
||||
# Whether Geyser should send team names in command suggestions.
|
||||
# Disable this if you have a lot of teams used that you don't need as suggestions.
|
||||
add-team-suggestions: true
|
||||
|
||||
# A list of remote resource pack urls to send to the Bedrock client for downloading.
|
||||
# The Bedrock client is very picky about how these are delivered - please see our wiki page for further info: https://geysermc.org/wiki/geyser/packs/
|
||||
resource-pack-urls: []
|
||||
|
||||
# Floodgate uses encryption to ensure use from authorized 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
|
||||
|
||||
# Advanced networking options for the Geyser to Java server connection
|
||||
java:
|
||||
# Whether to enable HAPROXY protocol when connecting to the Java server.
|
||||
# This is useful only when:
|
||||
# 1) Your Java server supports HAPROXY 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-haproxy-protocol: false
|
||||
|
||||
# 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, the remote address and port sections are ignored.
|
||||
# If disabled, expect performance decrease and latency increase.
|
||||
use-direct-connection: true
|
||||
|
||||
# Whether Geyser should attempt to disable packet compression (from the Java Server to Geyser) 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
|
||||
|
||||
# Advanced networking options for Geyser's Bedrock listener
|
||||
bedrock:
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# A value of 0 will broadcast the port specified above.
|
||||
# DO NOT change this unless Geyser runs on a different port than the one that is used to connect.
|
||||
broadcast-port: 0
|
||||
|
||||
# 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 expect HAPROXY protocol for connecting Bedrock clients.
|
||||
# This is useful only when you are running a UDP reverse proxy in front of your Geyser instance.
|
||||
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
|
||||
use-haproxy-protocol: false
|
||||
|
||||
# A list of allowed HAPROXY protocol speaking proxy IP addresses/subnets. Only effective when "use-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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
haproxy-protocol-whitelisted-ips: []
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1400
|
||||
|
||||
# This option disables the auth step Geyser performs for connecting Bedrock players.
|
||||
# It can be used to allow connections from ProxyPass and WaterdogPE. In these cases, make sure that users
|
||||
# cannot directly connect to this Geyser instance. See https://www.spigotmc.org/wiki/firewall-guide/ for
|
||||
# assistance - and use UDP instead of TCP.
|
||||
# Disabling Bedrock authentication for other use-cases is NOT SUPPORTED, as it allows anyone to spoof usernames, and is therefore a security risk.
|
||||
# All Floodgate functionality (including skin uploading and account linking) will also not work when this option is disabled.
|
||||
validate-bedrock-login: true
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: false
|
||||
|
||||
# Do not change!
|
||||
config-version: 5
|
||||
@@ -0,0 +1,236 @@
|
||||
# --------------------------------
|
||||
# Geyser Configuration File
|
||||
#
|
||||
# A bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition.
|
||||
#
|
||||
# GitHub: https://github.com/GeyserMC/Geyser
|
||||
# Discord: https://discord.gg/geysermc
|
||||
# Wiki: https://geysermc.org/wiki
|
||||
#
|
||||
# NOTICE: See https://geysermc.org/wiki/geyser/setup/ for the setup guide. Many video tutorials are outdated.
|
||||
# In most cases, especially with server hosting providers, further hosting-specific configuration is required.
|
||||
# --------------------------------
|
||||
|
||||
# Network settings for the Bedrock listener
|
||||
bedrock:
|
||||
# The IP address that Geyser will bind on to listen for incoming Bedrock connections.
|
||||
# Generally, you should only change this if you want to limit what IPs can connect to your server.
|
||||
address: 0.0.0.0
|
||||
|
||||
# The port that will Geyser will listen on for incoming Bedrock connections.
|
||||
# Since Minecraft: Bedrock Edition uses UDP, this port must allow UDP traffic.
|
||||
port: 19132
|
||||
|
||||
# Network settings for the Java server connection
|
||||
java:
|
||||
# The IP address of the Java Edition server.
|
||||
address: 127.0.0.1
|
||||
|
||||
# The port of the Java Edition server.
|
||||
port: 25565
|
||||
|
||||
# What type of authentication Bedrock players will be checked against when logging into the Java server.
|
||||
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
|
||||
auth-type: online
|
||||
|
||||
# Whether to 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
|
||||
|
||||
# MOTD settings
|
||||
motd:
|
||||
# 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"
|
||||
primary-motd: Geyser
|
||||
secondary-motd: Another Geyser server.
|
||||
|
||||
# Whether Geyser should relay the MOTD from the Java server to Bedrock players.
|
||||
passthrough-motd: true
|
||||
|
||||
# Maximum amount of players that can connect.
|
||||
# This is only visual, and is only applied if passthrough-motd is disabled.
|
||||
max-players: 100
|
||||
|
||||
# Whether to relay the player count and max players from the Java server to Bedrock players.
|
||||
passthrough-player-counts: true
|
||||
|
||||
# How often to ping the Java server to refresh MOTD and player count, in seconds.
|
||||
ping-passthrough-interval: 3
|
||||
|
||||
# Gameplay options that affect Bedrock players
|
||||
gameplay:
|
||||
# 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
|
||||
|
||||
# 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://geysermc.org/img/external/cooldown_indicator.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
|
||||
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# 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.
|
||||
nether-roof-workaround: false
|
||||
|
||||
# Whether to show Bedrock Edition emotes to other Bedrock Edition players.
|
||||
show-emotes: false
|
||||
|
||||
# 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.
|
||||
# This config option can be set to any Bedrock item identifier. If you want to set this to a custom item, make sure that you specify the item in the following format: "geyser_custom:<mapping-name>"
|
||||
unusable-space-block: minecraft:barrier
|
||||
|
||||
# Whether to add any items and blocks 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.
|
||||
# Geyser's block, item, and skull mappings systems will also be disabled.
|
||||
# This option requires a restart of Geyser in order to change its setting.
|
||||
enable-custom-content: true
|
||||
|
||||
# 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
|
||||
|
||||
# Whether to automatically serve a resource pack that is required for some Geyser features to all connecting Bedrock players.
|
||||
# If enabled, force-resource-packs will be enabled.
|
||||
enable-integrated-pack: true
|
||||
|
||||
# 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
|
||||
|
||||
# Allows Xbox achievements to be unlocked.
|
||||
# If a player types in an unknown command, they will receive a message that states cheats are disabled.
|
||||
# Otherwise, commands work as expected.
|
||||
xbox-achievements-enabled: false
|
||||
|
||||
# The maximum number of custom skulls to be displayed per player. Increasing this may decrease performance on weaker devices.
|
||||
# A value of 0 will disable all custom skulls.
|
||||
# Setting this to -1 will cause all custom skulls to be displayed regardless of distance or number.
|
||||
max-visible-custom-skulls: 0
|
||||
|
||||
# The radius in blocks around the player in which custom skulls are displayed.
|
||||
custom-skull-render-distance: 32
|
||||
|
||||
# The default locale if we don't have the one the client requested. If set to "system", the system's language will be used.
|
||||
default-locale: system
|
||||
|
||||
# Whether player IP addresses will be logged by the server.
|
||||
log-player-ip-addresses: true
|
||||
|
||||
# For online mode authentication type only.
|
||||
# Stores a list of Bedrock player usernames 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
|
||||
|
||||
# For online mode authentication type only.
|
||||
# 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
|
||||
|
||||
# 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
|
||||
|
||||
# Advanced configuration options. These usually do not need modifications.
|
||||
advanced:
|
||||
# Specify how many days player skin images will be cached to disk to save downloading them from the internet.
|
||||
# A value of 0 is disabled. (Default: 0)
|
||||
cache-images: 0
|
||||
|
||||
# Geyser updates the Scoreboard after every Scoreboard packet, but when Geyser tries to handle
|
||||
# a lot of scoreboard packets per second, this 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
|
||||
|
||||
# Whether Geyser should send team names in command suggestions.
|
||||
# Disable this if you have a lot of teams used that you don't need as suggestions.
|
||||
add-team-suggestions: true
|
||||
|
||||
# A list of remote resource pack urls to send to the Bedrock client for downloading.
|
||||
# The Bedrock client is very picky about how these are delivered - please see our wiki page for further info: https://geysermc.org/wiki/geyser/packs/
|
||||
resource-pack-urls: []
|
||||
|
||||
# Floodgate uses encryption to ensure use from authorized 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
|
||||
|
||||
# Advanced networking options for the Geyser to Java server connection
|
||||
java:
|
||||
# Whether to enable HAPROXY protocol when connecting to the Java server.
|
||||
# This is useful only when:
|
||||
# 1) Your Java server supports HAPROXY 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-haproxy-protocol: false
|
||||
|
||||
# Advanced networking options for Geyser's Bedrock listener
|
||||
bedrock:
|
||||
# The port to broadcast to Bedrock clients with the MOTD that they should use to connect to the server.
|
||||
# A value of 0 will broadcast the port specified above.
|
||||
# DO NOT change this unless Geyser runs on a different port than the one that is used to connect.
|
||||
broadcast-port: 0
|
||||
|
||||
# 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 expect HAPROXY protocol for connecting Bedrock clients.
|
||||
# This is useful only when you are running a UDP reverse proxy in front of your Geyser instance.
|
||||
# IF YOU DON'T KNOW WHAT THIS IS, DON'T TOUCH IT!
|
||||
use-haproxy-protocol: false
|
||||
|
||||
# A list of allowed HAPROXY protocol speaking proxy IP addresses/subnets. Only effective when "use-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.
|
||||
# IP addresses, subnets, and links to plain text files are supported.
|
||||
haproxy-protocol-whitelisted-ips: []
|
||||
|
||||
# The internet supports a maximum MTU of 1492 but could cause issues with packet fragmentation.
|
||||
# 1400 is the default.
|
||||
mtu: 1400
|
||||
|
||||
# This option disables the auth step Geyser performs for connecting Bedrock players.
|
||||
# It can be used to allow connections from ProxyPass and WaterdogPE. In these cases, make sure that users
|
||||
# cannot directly connect to this Geyser instance. See https://www.spigotmc.org/wiki/firewall-guide/ for
|
||||
# assistance - and use UDP instead of TCP.
|
||||
# Disabling Bedrock authentication for other use-cases is NOT SUPPORTED, as it allows anyone to spoof usernames, and is therefore a security risk.
|
||||
# All Floodgate functionality (including skin uploading and account linking) will also not work when this option is disabled.
|
||||
validate-bedrock-login: true
|
||||
|
||||
# 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
|
||||
enable-metrics: true
|
||||
|
||||
# The bstats metrics uuid. Do not touch!
|
||||
metrics-uuid: 00000000-0000-0000-0000-000000000000
|
||||
|
||||
# If debug messages should be sent through console
|
||||
debug-mode: false
|
||||
|
||||
# Do not change!
|
||||
config-version: 5
|
||||
Reference in New Issue
Block a user