MiniDay/Velocity
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Align default prevent proxy connection settings with the default config file

Browse Source 
This option generally creates a bunch of oddities in many setups, defaulting to false
as per the default toml config, is probably the better option here
This commit is contained in:
Shane Freeder
2024-04-20 13:57:31 +01:00
parent 9e42049a67
commit 3b6419997c
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
proxy/src/main/java/com/velocitypowered/proxy/config/VelocityConfiguration.java
View File

@@ -503,7 +503,7 @@ public class VelocityConfiguration implements ProxyConfig {
final boolean forceKeyAuthentication = config.getOrElse("force-key-authentication", true); final boolean forceKeyAuthentication = config.getOrElse("force-key-authentication", true);
final boolean announceForge = config.getOrElse("announce-forge", true); final boolean announceForge = config.getOrElse("announce-forge", true);
final boolean preventClientProxyConnections = config.getOrElse( final boolean preventClientProxyConnections = config.getOrElse(
"prevent-client-proxy-connections", true); "prevent-client-proxy-connections", false);
final boolean kickExisting = config.getOrElse("kick-existing-players", false); final boolean kickExisting = config.getOrElse("kick-existing-players", false);
final boolean enablePlayerAddressLogging = config.getOrElse( final boolean enablePlayerAddressLogging = config.getOrElse(
"enable-player-address-logging", true); "enable-player-address-logging", true);