warn on player quit

[newbie029]

sometime player is disconnecting.. then when they try to join again... the server said that the player name is currently playing on the game... need to wait 10-30 seconds to rejoin the server.. here the console log
Paperspigot 1.12.2 Build 1360

[17:14:03 INFO]: Disconnecting com.mojang.authlib.GameProfile@3896f0f7[id=561fe784-64ae-3e42-b6c1-aafc84780d04,name=Crystalize,properties={},legacy=false] (/114.124.201.127:60827): Nama pengguna yang sama sedang bermain di dalam server!
[17:14:03 INFO]: com.mojang.authlib.GameProfile@3896f0f7[id=561fe784-64ae-3e42-b6c1-aafc84780d04,name=Crystalize,properties={},legacy=false] (/114.124.201.127:60827) lost connection: Nama pengguna yang sama sedang bermain di dalam server!
[17:14:13 WARN]: Couldn't look up profile properties for com.mojang.authlib.GameProfile@57dbf051[id=561fe784-64ae-3e42-b6c1-aafc84780d04,name=Crystalize,properties={},legacy=false]
com.mojang.authlib.exceptions.AuthenticationException: The client has sent too many requests within a certain amount of time
at com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService.makeRequest(YggdrasilAuthenticationService.java:79) ~[patched_1.12.2.jar:git-Paper-1360]
at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillGameProfile(YggdrasilMinecraftSessionService.java:180) [patched_1.12.2.jar:git-Paper-1360]
at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillProfileProperties(YggdrasilMinecraftSessionService.java:173) [patched_1.12.2.jar:git-Paper-1360]
at com.destroystokyo.paper.profile.WrappedMinecraftSessionService.fillProfileProperties(WrappedMinecraftSessionService.java:67) [patched_1.12.2.jar:git-Paper-1360]
at com.destroystokyo.paper.profile.CraftPlayerProfile.complete(CraftPlayerProfile.java:112) [patched_1.12.2.jar:git-Paper-1360]
at net.minecraft.server.v1_12_R1.LoginListener$LoginHandler.fireEvents(LoginListener.java:301) [patched_1.12.2.jar:git-Paper-1360]
at net.minecraft.server.v1_12_R1.LoginListener$2.run(LoginListener.java:206) [patched_1.12.2.jar:git-Paper-1360]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_161]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_161]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_161]
[17:14:13 INFO]: Disconnecting com.mojang.authlib.GameProfile@695716c1[id=561fe784-64ae-3e42-b6c1-aafc84780d04,name=Crystalize,properties={},legacy=false] (/114.124.201.127:60828): Nama pengguna yang sama sedang bermain di dalam server!
[17:14:13 INFO]: com.mojang.authlib.GameProfile@695716c1[id=561fe784-64ae-3e42-b6c1-aafc84780d04,name=Crystalize,properties={},legacy=false] (/114.124.201.127:60828) lost connection: Nama pengguna yang sama sedang bermain di dalam server!
[17:14:20 INFO]: Yuramy lost connection: Timed out
[17:14:20 INFO]: [-] 『Developer』Yuramy left the game.
[17:14:20 INFO]: Crystalize lost connection: Timed out
[17:14:20 INFO]: [-] 『Member』Crystalize left the game.
[17:14:21 WARN]: Couldn't look up profile properties for com.mojang.authlib.GameProfile@3be011d4[id=561fe784-64ae-3e42-b6c1-aafc84780d04,name=Crystalize,properties={},legacy=false]
com.mojang.authlib.exceptions.AuthenticationException: The client has sent too many requests within a certain amount of time
at com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService.makeRequest(YggdrasilAuthenticationService.java:79) ~[patched_1.12.2.jar:git-Paper-1360]
at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillGameProfile(YggdrasilMinecraftSessionService.java:180) [patched_1.12.2.jar:git-Paper-1360]
at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillProfileProperties(YggdrasilMinecraftSessionService.java:173) [patched_1.12.2.jar:git-Paper-1360]
at com.destroystokyo.paper.profile.WrappedMinecraftSessionService.fillProfileProperties(WrappedMinecraftSessionService.java:67) [patched_1.12.2.jar:git-Paper-1360]
at com.destroystokyo.paper.profile.CraftPlayerProfile.complete(CraftPlayerProfile.java:112) [patched_1.12.2.jar:git-Paper-1360]
at net.minecraft.server.v1_12_R1.LoginListener$LoginHandler.fireEvents(LoginListener.java:301) [patched_1.12.2.jar:git-Paper-1360]
at net.minecraft.server.v1_12_R1.LoginListener$2.run(LoginListener.java:206) [patched_1.12.2.jar:git-Paper-1360]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_161]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_161]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_161]
[17:14:21 INFO]: UUID of player Crystalize is 561fe784-64ae-3e42-b6c1-aafc84780d04
[17:14:21 INFO]: Crystalize[/114.124.201.127:60833] logged in with entity id 318491 at ([pvpon]-321.0177302374274, 4.0, -1128.574460210938)
[17:14:21 INFO]: [+] 『Member』Crystalize joined the game.
[17:14:37 INFO]: [AuthMe] The user Crystalize has 2 accounts:
[17:14:37 INFO]: [AuthMe] yuramy, Crystalize.
[17:14:37 INFO]: [AuthMe] Crystalize logged in!
[17:15:06 INFO]: UUID of player Yuramy is 4cd58cb0-72e2-38f9-a20b-7a4f22448995
[17:15:09 INFO]: Yuramy[/114.124.201.127:60842] logged in with entity id 322353 at ([pvpon]-317.1067297379713, 4.0, -1129.1416266272029)

[Black-Hole]

For offline mode server it's normal behaviour that new connections won't kick existing connections with the same user name.

But your problem is caused by this: "com.mojang.authlib.exceptions.AuthenticationException: The client has sent too many requests within a certain amount of time"

Please ask the AuthMe author for help configuring the plugin to avoid this.

[sgdc3]

For offline mode server it's normal behaviour that new connections won't kick existing connections with the same user name.

False, this is done by AuthMe

But your problem is caused by this: "com.mojang.authlib.exceptions.AuthenticationException: The client has sent too many requests within a certain amount of time"
Please ask the AuthMe author for help configuring the plugin to avoid this.

What's the connection between the authsession rate limit and AuthMe? Sorry but i don't get your point, could you explain this please? ;)
@Black-Hole

[electronicboy]

This issue is entirely out of our realms, your issue is also on player login. Rate limits are a Mojang thing and have nothing to do with us, nor is there anything we can do about that.