Replace word 'Player' with 'Account' in messages.

Technically speaking, one player can own both the Java and the Bedrock
account with the same name, so it's more appropriate to say account
instead of player.
This commit is contained in:
Smart123s
2021-06-20 17:44:46 +02:00
parent 33261b9ea6
commit 2ffe7e0daf
2 changed files with 5 additions and 4 deletions

View File

@ -69,17 +69,18 @@ public class FloodgateHook<P extends C, C, S extends LoginSource> {
"Could not check wether Floodgate Player {}'s name conflicts a premium Java player's name.",
username);
try {
source.kick("Could not check if your name conflicts an existing Java Premium Player's name");
source.kick("Could not check if your name conflicts an existing premium Java account's name.\n"
+ "This is usually a serverside error.");
} catch (Exception e1) {
core.getPlugin().getLog().error("Could not kick Player {}", username);
}
}
if (premiumUUID.isPresent()) {
core.getPlugin().getLog().info("Bedrock Player {}'s name conflicts an existing Java Premium Player's name",
core.getPlugin().getLog().info("Bedrock Player {}'s name conflicts an existing premium Java account's name",
username);
try {
source.kick("Your name conflicts an existing Java Premium Player's name");
source.kick("Your name conflicts an existing premium Java account's name");
} catch (Exception e) {
core.getPlugin().getLog().error("Could not kick Player {}", username);
}

View File

@ -94,7 +94,7 @@ public abstract class FloodgateManagement<P extends C, C, L extends LoginSession
premiumUUID = core.getResolver().findProfile(username);
} catch (IOException | RateLimitException e) {
core.getPlugin().getLog().error(
"Could not check wether Floodgate Player {}'s name conflits a premium Java player's name.",
"Could not check wether Floodgate Player {}'s name conflits a premium Java account's name.",
username);
return;
}