PaperMC
Warterfall can't get kick message from subserver.
Waterfall version: #445 Paper version: 1.16.5 #762
Issue: When a player is refused by the subserver for some reason
( for example, refused by Authme, for using an illegal username),
The subserver's console can display the right message.
but waterfall can't get the right reason for "lost connection". It just displays "could not connect to a default or fallback server".
This caused my players to be unable to know the specific reason why they were disconnected. Everyone thought that the server had not been started yet. I have developed a plug-in to verify some user information, and use the disallow method ( I have also tried player.kick method) to deny players who do not meet the requirements to enter. Waterfall also cannot obtain this information. Only the console of the subserver can correctly output the reason for the disconnection.
The reason for this is that on join bungeecord tries to connects you to the priority list servers from top to bottom. When it recieves a kick, it tries the next server is that list, if there is none, you get this message.
I see potential for this issue to get fixed in BungeeCord as well if you create an issue there.
The reason for this is that on join bungeecord tries to connects you to the priority list servers from top to bottom. When it recieves a kick, it tries the next server is that list, ifthere is none, you get this message.
but bungeecord should and used to show why player is kicked, why the recent version's can't。