As far as I'm aware this is due to Mojang rate-limiting a critical API of theirs recently, I'm not 100% sure why...
How very strange, well caught!
Yeah, just drop those 200 users. They're people who refunded their Minecraft purchase or were removed for other reasons.
It looks like this issue can currently arise from legacy account holders/demo account holders buying accounts and this not being properly handled by the system, but obviously we don't have any idea about the internal workings, so we can only conjecture.
As far as server owners are concerned, yes, it is possible to get a wrong uuid for a user, and in fact is quite likely if you happen to get one of the users affected by this bug since it seems the incorrect uuid is the ony first in the list, which will result in (when it gets fixed) the correct uuid being the second one, which means that any server that tried to convert them beforehand will have the wrong uuid saved!
Looks like the vanilla minecraft server assigns the wrong UUID to this user.
I just ran a test startup of an online mode vanilla server and it exceptioned out (but still converted) Nico.dat to 3bfb7c8d-02a2-4ece-8b56-c7e22a553be3.dat
Bug still present in vanilla server, please mark as unresolved.
Is that an authoritative statement, or a suggestion?
Oh ok, so false alarm?
I'm unclear if this is still an issue or not.
If the intended behaviour is for the username -> uuid lookup to return a single uuid, so as far as it looks, even if it's for the demo account reasons, it's still an issue.
Just to be clear, I'm talking about the "Server sent invalid player data." message here.
/tp commandercarrot ~1000 ~ ~ followed by /tp commandercarrot ~-1000 ~ ~
That doesn't fix expiring skins for new joins after 24h
Whoever formatted this for me, you're a saint, thankyou.
Don't panic. This code doesn't "break" inventory event cancelling.
It does however cause derpiness client side.
This isn't a technical issue, this is a bug with the rate-limiting of the API by Mojang.
While it might be technically a DOS, it's a very low threshold they've set. This bug report serves to prove that they are harming vanilla gameplay with their rate-limiting.