Format disapears when players type too fast

Question

Format disapears when players type too fast

Closed this issue 2 years ago · 4 comments

when submitting a message too fast (preview can't keep up) the message will appear without any format and any username.
As if it had been a /tellraw command.

Here are some images to better explain :

When the preview has time to update :

When the preview doesn't have time to load :

On the console :

Here's a list of all the mods i use :

https://yellow-maighdiln-25.tiiny.site

And here's a log from launch :

https://mclo.gs/pAg6eaI

Answer 1 · 2023-01-14T08:39:43.000Z

I fear that's a limitation of Minecraft's chat signing feature. You have to give the message time to be signed before sending it, otherwise the signature doesn't correspond to the message and the server/other players cannot verify it.

Answer 2 · 2023-02-05T17:14:13.000Z

Is there a way to make the player wait for the signing to happen before beeing able to send the message ?
Now that my server is open, it's very frustrating not knowing who's talking...

Answer 3 · 2023-02-12T14:55:46.000Z

There's a setting on the client regarding when messages get signed. You can set that to sign when sending it to the server after which the server will decorate it, send it back to the client and the client can then confirm it. Rather annoying if you ask me, but this entire chat signing stuff is anyway.

Answer 4 · 2023-02-13T18:40:34.000Z

I believe this should be fixed in the next update. I am currently porting the mod to 1.19.3 and Mojang removed chat previews. This means that the client does not have to wait to receive the decorated version from the server anymore before sending the message which should fix this issue. I have tried this on my own local test server and it appeared to be fine, but I obviously cannot say with certainty that this issue is now resolved.

There is virtually nothing I can do to fix this in the current version because this is a limitation of Minecraft's chat signing system (which thus seems fixed in 1.19.3), so if you really need a version for 1.19.2, there is sadly nothing I can do for you.

I will hereby close this issue, if you still encounter this in the next version which I will release hopefully somewhere in the coming days/weeks, please open a new one.