-
-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chat error message #3438
Comments
I guess this implies there is a mismatch between what the server thinks ChatVisibility is and what the client has it set to? There is now a Client Information packet sent from the client for config phase, but maybe this is not being interpreted correctly. I don't see anything weird on the client side that would force this to hidden during the config phase. |
I can also confirm this issue, I don't have installed ChatVisibility, but it to happen for the first few messages for me on every single backend server that installed ViaVersion + ViaBackwards. |
I am also experiencing this issue. I am using the following: Client: Minecraft 1.20.2 The issue only happens on my 1.19.4 server and not my 1.17.1 servers. It also only affects messages sent using PlayerJoinEvent (I have join/leave messages disabled, but those are probably affected too). |
Does this still happen with 4.9.x? |
Yes, it is still happening on the latest version. |
I can reproduce this with the latest ViaVersion on a 1.19.4 server and a 1.20.2 client. LAN. |
Still an issue on 4.9.2 |
Yup, still seems to be present on viaversion 4.9.2 with viabackwards 4.9.1 |
Same issue here even with latest dev build |
Can reproduce this with any client version higher than 1.19.4 while server being on 1.19.4, doesn't happen with versions lower than 1.19.4. |
This comment has been minimized.
This comment has been minimized.
That issue still exists on latest versions |
Can't reproduce with latest ViaVersion, if the issue still exists, create a new issue. |
Still can reproduce this on Paper 1.19.4 and ViaVersion 4.9.3. |
Same here, but with server being 1.20.1 ( |
Looks like the issue only appears when running a cracked server (or a bungee/velocity sub server) |
Not in my case, I'm using
|
Please try the latest build(s) from https://ci.viaversion.com/. In case the issue still persists send the new dump |
It's still happening in 1.19.4 |
This is still happening on the latest 4.10.3 snapshot. https://dump.viaversion.com/b786287a2dae23f77a51c18e7f0d7344527e375416cb5a9302a98cec8feb8ea6 |
BUMP |
/viaversion dump
Outputhttps://dump.viaversion.com/82846e490167681afdf28b316987f4cc04779bc39c3a1e35c3782dd315d8e5a0
Console Error
It's only in the client-side logs
[14:50:03] [Render thread/INFO]: [System] [CHAT] BicigliKepu joined the game
[14:50:03] [Render thread/INFO]: [System] [CHAT] Can't deliver chat message, check server logs: BicigliKepu joined the game
Bug Description
Using ViaVersion on a 1.20.1 server and connecting to it with 1.20.2 will result in a chat error message on join like this:
![image](https://private-user-images.githubusercontent.com/145910739/270165215-a61e7fb8-8a5a-4a79-a60f-0d0a2924d86e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjI4NDA2NDYsIm5iZiI6MTcyMjg0MDM0NiwicGF0aCI6Ii8xNDU5MTA3MzkvMjcwMTY1MjE1LWE2MWU3ZmI4LThhNWEtNGE3OS1hNjBmLTBkMGEyOTI0ZDg2ZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODA1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgwNVQwNjQ1NDZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00N2I2YTlhNzk0OGM1YzM3MTg2M2IwMzM3MmQzZjE0OWVmMzM5NjdkNDUyYWE3NTBlYzczOWMyODYzMWUwZjEzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.AujaRq38LnM0sa9vIqcD6yImUxznYjReNKZIciV8pOc)
I tried with Paper and Spigot, on Spigot it's the same message on 1st join but after that it doesn't happen (?), meanwhile on Paper it happens on every join
Steps to Reproduce
Expected Behavior
No error message on chat
Additional Server Info
No response
Checklist
The text was updated successfully, but these errors were encountered: