You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the /me styling for messages defined on lines 2906-2908, it ignores the chosen recipient field when determining display. It properly maintains chosen view permissions, on who actually sees it, which is most important; but could lead to confusion when it does not also carry the msgsendmod or similar message permission variable before it in the view frame. With PMs the handling would be more complicated, since it normally displays the recipient name after the sender name. But for [M] [S] or [A] messages, there would be no problem with displaying those variables before the /me message. It seems like it could be done by adapting the code from lines 2867-2882.
I do not run a copy of your chat to test this change on at this time, but hope my description was clear enough to understand the issue I mention and see a way to fix it.
thank you
The text was updated successfully, but these errors were encountered:
When using the /me styling for messages defined on lines 2906-2908, it ignores the chosen recipient field when determining display. It properly maintains chosen view permissions, on who actually sees it, which is most important; but could lead to confusion when it does not also carry the msgsendmod or similar message permission variable before it in the view frame. With PMs the handling would be more complicated, since it normally displays the recipient name after the sender name. But for [M] [S] or [A] messages, there would be no problem with displaying those variables before the /me message. It seems like it could be done by adapting the code from lines 2867-2882.
I do not run a copy of your chat to test this change on at this time, but hope my description was clear enough to understand the issue I mention and see a way to fix it.
thank you
The text was updated successfully, but these errors were encountered: