They should just remove showing the macOS version and done. Easy problem solved.
Still an issue.
@Mustermaster1402
You can still request username history if you know his uuid.
And since the swap from names to uuids was 10 years ago there shouldn't be any database or other userdata storage which is solely based on names in 2022.
And you apparantly cannot read. In WEB-13 is was said that the parameter was removed INTENTIONALLY. You won't get it back.
Edit: Also projects exist to use namemc as api like https://github.com/jaqobb/namemc-api so I really don't see the problem here.
I would consider "looking bad" as bug and not as feature request
Unfortunaly there is no 100%- complementary API for this available as others have alreay noted. The priority of this issue is wrong!
As the original issue got reopened, this can be closed.
Deprecation before removal would've been a good option here.
I just thought of adding a TinyEntityMove packet, which moves the entity inside 1/32 of a block with a precision of 1/32. This packet could be sent by the server if the entity is not moving much or not at all to get a higher precision. Or you could add a boolean to the existing packet for this.
Is there going to be any backport for this fix?
I updated the description, removed mentines of optifine (as its clearly irrelevant). Also I put maybe irrelevant things I used as I got this error into an extra part and made things clearer. (I'm not a native english speaker)
not fixed yet, but i can't edit it 😞
this bug is not fixed in the newest snapshot
I can only confirm this. I currently test my first bukkit plugin on my local server and when i stop the server, and join any other server (can be the same) , the chat is not cleared and even the history (arrow up while typing) is still there.
But the chat will be cleared if you are kicked and then go to singleplayer.
Even with the default texture pack and the newest snapshot I can't see the experience bar. PLEASE REOPEN AND FIX THIS.
(I can see the hearts and my food level, so I'm not in creative mode. this happens in survival and adventure mode.
I really like this exploding and I hope this won't be changed.
I testet a bit and i can say, that it is a problem with especially this seed. Without a seed or with an other seed with the same settings it works. Also, changing game mode to survival or turning cheats off couldn't resolve the issue. Also turning cheats off and changing game mode to survival made nothing. It is a problem with the seed.
Maybe the full error message could help...
Its sad to see that cutting costs stands far above user experience here.