This is essentially MC-52974, except it does not happen every time.
The bug
If the host of a LAN world has not opened another world before opening a world to LAN, any player that joins that LAN world won't see the host's skin and receive the following error message:
Couldn't look up profile properties for com.mojang.authlib.GameProfile@36e09f7b[id=80635c78-1b0d-4d33-9e84-efa687448d77,name=violine1101,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)
at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillGameProfile(YggdrasilMinecraftSessionService.java:180)
at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillProfileProperties(YggdrasilMinecraftSessionService.java:173)
at dea.a(SourceFile:114)
at dea$$Lambda$1140/12275979.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Steps to reproduce
Host starts the game
Host joins a world
Host opens the world to LAN
Player joins the LAN world
Player doesn't see host's skin
Linked issues
is duplicated by 4
relates to 2
Comments 5
I ran into this problem today running 1.13.2. Steve was the skin of the player hosting the game, but from his machine he was properly skinned. I had the client disconnect and reconnect and his model was Steve for a brief moment before it updated to the correct skin. Is it possible that latency or lag is the culprit?
I doubt it. I tested this with two clients on my computer, so latency/lag should have been nearly non-existant.
But, I'm not exactly sure as to when exactly this issue occurs, so further testing is always appreciated.
I've had this issue in 1.14.3, and the skins 'reset' when the server is restarted and opened again, even on computers that have opened it previously
Confirmed for 1.13.1-pre1