LemonCaramel

Confirmed in 24w37a

This issue has been fully fixed in 24w36a with the teleport refactoring. Players no longer send incorrect xRot values to the server, no longer spam packets, and no longer show impossible rotation behavior when the chat screen is open.

Ban reason is converted to JSON component format when sent to the player.

The converted ban reason always has the following format. (64 number of characters)

{"translate":"multiplayer.disconnect.banned.reason","with":[""]}

To trigger the error, it needs to exceed 32767 characters(32768+), so 32704 characters or more is correct.

I was very disappointed with Mojang's response, and I think they treated Koreans poorly.
They didn't even explain why they won’t fix this issue.
And among many languages, only Korean has changed to be difficult to read.
I know, this is Unifont's fault. but Mojang choose Unifont among the other fonts. Isn't it?
Mojang is no longer an indie game company. Before making these font changes, the local community has to confirm that there are no problem, and if there are, Mojang should resolve it.
It doesn't seem to be right to pass over responsibility on customer to solve Unifont issue.
This is never a minor issue and should be fixed before 1.20 release. Please reconsider this issue, Mojang.

First, I was making a recoil(gun, helicopter and etc...) system. _{(using Relative Teleport)}
However, this bug prevents me from performing the intended action.

-------

As you can see in the video, the player can take actions that are impossible.

-------

From the viewpoint of the third-party server operator(or Developer)

• Sends xRot(Pitch) values to the server that the player cannot have.

• Clients spam packets to the server to correct invalid pitch values.

From the viewpoint of the player

• The game player can see the impossible action.

• and more?.. (i don't know)

From the viewpoint of the content creator

• When using the relative teleport, the player can see unintended actions.

There are too many omitted expressions because I am not good at English. I'm sorry.

yes The video I uploaded is Vanilla Client.

• ^{Sends xRot values that the player cannot have to the server}

• ^{client can make impossible moves.}

^{There is no problem with 1.19.2 or less. (It's calibrated by the client)}

I forgot to reply. It was resolved after switching to Fabulous, so you can close the issue.

Can confirm in 22w11a

You may not have known. singleplayer uses a way of open and join in multiplayer server.

singleplayer = open multiplayer server and join(If you check the Minecraft log, you can understand this method.)

In other words, the singleplayer server crashes enough.

I don't live in an English-speaking country. I hope you can understand what I'm saying.