Fixed 'allowFloodgateNameConflict' for 'false' value.

This commit is contained in:
Smart123s
2021-03-22 19:57:13 +01:00
parent 5d94e610ff
commit f9992f1447
2 changed files with 5 additions and 3 deletions

View File

@ -39,7 +39,9 @@ public class FloodgateAuthTask implements Runnable {
player.kickPlayer("This name is allready in use by a Premium Java Player");
}
if (!allowNameConflict.equalsIgnoreCase("true") && !allowNameConflict.equalsIgnoreCase("linked")) {
if (!allowNameConflict.equalsIgnoreCase("true")
&& !allowNameConflict.equalsIgnoreCase("linked")
&& !allowNameConflict.equalsIgnoreCase("false")) {
plugin.getLog().error(
"Invalid value detected for 'allowFloodgateNameConflict' in FasttLogin/config.yml. Aborting login of Player {}",
player.getName());

View File

@ -197,8 +197,8 @@ autoLogin: true
# !!! DO NOT REMOVE THE APOSTROPHE !!!
autoLoginFloodgate: 'false'
# This enables Floodgate players to join the server, even if autoRegister is true and there's an existing Java Premium
# account with the same name
# This enables Floodgate players to join the server, even if autoRegister is true and there's an existing
# Java **PREMIUM** account with the same name
# Possible values:
# false: Check for Premium Java name conflicts as described in 'autoRegister'
# 'autoRegister' must be 'true' for this to work