David

I am the only one too my knowledge that posted about this

they should make it so that you are able to decide wether or not you want to be able to control your camera with your attack and place button. Because some people use their index finger to press the attack and place blocks buttons, and their thumb to move the camera, and if your camera also moves when you tap on your attack button, it can make it impossible to aim properly

Perdi meu mundo

Not everyone gets kicked when this happens, some do, but even if you don't get kicked your chat is still broken and the only way to fix it is by logging out and back in.

This is still a bug in the latest version and it has been a bug for a very long time. When the server thinks that a player is flying, the following is logged to the console:

[Disconnect] User PLAYER has disconnected, reason: Flying is not enabled on this server
[Server] INFO [Player] PLAYER left the game
[Server] WARN PLAYER was kicked for floating too long!

The bug is that the "was kicked for floating too long" message is logged hundreds of times all at once in response to a single kick event (it was logged 382 times in response to a single kick event on my server today), which floods the console with the same message over using up lots of disk space over time and is also very annoying. This may also cause a lag spike on the server, as others have reported.

Same happened to me, when I was kicked out of my friend's world and after returning to menu GUI scale was smaller and in the setting maximum size I could choose was "0".

My phone: Google Pixel 7. Android 13.

Can confirm that this is still a bug in 1.19.3. Avoma is exactly right, this is inconsistent with other statistics such as smelting.

Is there any chance this will be fixed? I understand the algorithms were changed but this is a big deal for servers. Old worlds are unable to use eyes of ender. Are we just supposed to reset the entire world every time there is a new Minecraft update?

Can confirm 1.19.3

Thank you for the response. I was able to properly test this on vanilla Minecraft, Spigot, and Paper. Both vanilla Minecraft and Spigot have a similar issue with these same areas, but they are rendered much faster (usually taking less than one second). But for Paper it takes multiple seconds to render the same thing, so I think I've made some progress figuring this out. Sorry for creating another invalid ticket here. Thanks for the help.

I created a Jira issue earlier today with a similar description, but please notice that the issue described here is clearly an issue with the Minecraft client and not related to any server software I am using. Thank you so much for your help resolving this very important issue.

I have attached the player's log, they were using the optifine client (which i seriously doubt has any effect)
The server is a realm, so it literally couldn't be more vanilla

I also do not have the player blocked in the 'p' menu

I find it incredibly weird that this issue is occurring before 1.19.1 has even been released

When I went to record this morning the bug was not happening in either singleplayer or multiplayer. I was able to reproduce it when I created this ticket, and when I posted the first comment on this ticket, but as of today it looks like this issue is no longer happening. I'm assuming this was fixed elsewhere, either intentionally or unintentionally.

In any case this ticket can be closed. Thank you to everyone who spent time on this. The whole community is very appreciative of all the bug fixes! Keep up the great work 🙂 

Fixed.... I had to go into advanced settings set Steam VR  for open xr....            now it opens just crashes about 40 seconds into the game... its awesome for that forty seconds though.

Are you able to provide a seed for which this happens?