-
-
Notifications
You must be signed in to change notification settings - Fork 497
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
Implement degraded client notice & legacifying of messages for LunarClient #1294
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed still broken on LunarClient 1.17.1-63e9251. Tested that channel register, plugin message and client brand will trigger the notice.
Will check again, soon |
…sages completely. Related to #1294
Confirmed that LunarClient fixed it, took them long enough. Next version has the notice & click/hover component removal taken out |
the message has not been removed. or at least, i'm still getting notifications in the log that people have been shown the warning. |
The latest release still has it, it will be gone in the next version |
For users stumbling upon this PR,
Due to LunarClient hiding messages containing click to copy functionality (this also happens for vanilla commands, eg. the
/seed
command) and not showing any intention to fix this even after being notified of the issue (multiple times over 5+ months), we have decided to add a notification for users using LunarClient letting them know that some commands may not work as expected, as this functionality should work as it does on the vanilla client instead of completely hiding the message.Image of their support manually closing a ticket without comment regarding this issue. The ticket was closed before the last message. The last message was sent in hopes of response to no avail.