Remove bungeecord messaging hook
It was the cause of many issues, as temp replacement server owners can use AuthMeBridge.
This commit is contained in:
@@ -49,9 +49,6 @@ public class AsyncChangePassword implements AsynchronousProcess {
|
||||
playerCache.updatePlayer(auth);
|
||||
processService.send(player, MessageKey.PASSWORD_CHANGED_SUCCESS);
|
||||
ConsoleLogger.info(player.getName() + " changed his password");
|
||||
|
||||
// Send a Bungee message for the password change
|
||||
bungeeService.sendPasswordChanged(player, hashedPassword);
|
||||
} else {
|
||||
processService.send(player, MessageKey.WRONG_PASSWORD);
|
||||
}
|
||||
|
||||
@@ -119,7 +119,6 @@ public class ProcessSyncPlayerLogin implements SynchronousProcess {
|
||||
// The Login event now fires (as intended) after everything is processed
|
||||
bukkitService.callEvent(new LoginEvent(player));
|
||||
player.saveData();
|
||||
bungeeService.sendBungeeMessage(player, "login");
|
||||
|
||||
// Login is done, display welcome message
|
||||
if (service.getProperty(RegistrationSettings.USE_WELCOME_MESSAGE)) {
|
||||
|
||||
@@ -64,8 +64,6 @@ public class ProcessSynchronousPlayerLogout implements SynchronousProcess {
|
||||
|
||||
// Player is now logout... Time to fire event !
|
||||
bukkitService.callEvent(new LogoutEvent(player));
|
||||
// Send Bungee stuff. The service will check if it is enabled or not.
|
||||
bungeeService.sendBungeeMessage(player, "logout");
|
||||
|
||||
service.send(player, MessageKey.LOGOUT_SUCCESS);
|
||||
ConsoleLogger.info(player.getName() + " logged out");
|
||||
|
||||
@@ -92,7 +92,6 @@ public class ProcessSyncPasswordRegister implements SynchronousProcess {
|
||||
}
|
||||
|
||||
// Send Bungee stuff. The service will check if it is enabled or not.
|
||||
bungeeService.sendBungeeMessage(player, "register");
|
||||
bungeeService.connectPlayer(player);
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user