btw @kiizde for my bedrock server I fixed by hooking the StartGamePacket and setting the Pitch/Yaw values to 0 if NaN. This avoids the game crashing with a memory leak.
This should be doable in client side. Its more easy to simulate using MCPE-Linux (I know that's not official, but its easier to simulate there), but it does happen ocasionally at Minecraft for Windows 10 as well.
The thing is that in local game and bedrock server, you can fix it by editing the NBT and setting the NaNs to zero in player profile, but when playing in a realm, you're stuck.
Since the cause of NaN's are unknown, I would add to bedrock codebase a fix on StartGamePacket to ensure no NaN values go to client. This way, if the crash happens, you just need to log in the server again.
Lucas Teske
btw @kiizde for my bedrock server I fixed by hooking the StartGamePacket and setting the Pitch/Yaw values to 0 if NaN. This avoids the game crashing with a memory leak.
https://github.com/racerxdl/bedhock/blob/main/src/hooks/fixes.cpp#L23-L29
This should be doable in client side. Its more easy to simulate using MCPE-Linux (I know that's not official, but its easier to simulate there), but it does happen ocasionally at Minecraft for Windows 10 as well.
The thing is that in local game and bedrock server, you can fix it by editing the NBT and setting the NaNs to zero in player profile, but when playing in a realm, you're stuck.
Since the cause of NaN's are unknown, I would add to bedrock codebase a fix on StartGamePacket to ensure no NaN values go to client. This way, if the crash happens, you just need to log in the server again.