Could not pass event AsyncPlayerChatEvent to ChatEx v2.5.2

Question

Could not pass event AsyncPlayerChatEvent to ChatEx v2.5.2

lerokko opened this issue 5 years ago · 6 comments

lerokko commented 5 years ago

Sorry if this is not an issue with your plugin.
Today a player joined and sometimes when he send messages they where malformed. The current format is "[N] playername: message" without the <> from vanilla. For some reason some of his messages (2 to be exact both of them only saying ":p") appeared with the two brackets.

I'm running paperspigot build 332 with luckperms, vault, vault chat formatter.

[Tue, 2. Jun 2020 18:41:29 CEST INFO] [N] redacted3: bye cruel world
[Tue, 2. Jun 2020 18:41:23 CEST ERROR] Could not pass event AsyncPlayerChatEvent to ChatEx v2.5.2
[Tue, 2. Jun 2020 18:41:23 CEST INFO] <[N] redacted3> :p

TheJeterLP · Answer 1 · 2020-06-02T19:10:47.000Z

Do you have any more error information? Or was there no error code? lerokko <[email protected]> schrieb am Di., 2. Juni 2020, 19:43:

…

Sorry if this is not an issue with your plugin. Today a player joined and sometimes when he send messages they where malformed. The current format is "[N] playername: message" without the <> from vanilla. For some reason some of his messages (2 to be exact both of them only saying ":p") appeared with the two brackets. I'm running paperspigot build 332 with luckperms, vault, vault chat formatter. [Tue, 2. Jun 2020 18:41:29 CEST INFO] [N] redacted3: bye cruel world [Tue, 2. Jun 2020 18:41:23 CEST ERROR] Could not pass event AsyncPlayerChatEvent to ChatEx v2.5.2 [Tue, 2. Jun 2020 18:41:23 CEST INFO] <[N] redacted3> :p — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#19>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA45KKNVWZBV3XYV7ROZMCDRUU245ANCNFSM4NQ556MQ> .

lerokko · Answer 2 · 2020-06-03T15:19:02.000Z

This is how it appeared in the console. I included the first line to show you how it usually appears. 2nd line is the Error message which I assume causes the malformed message (line 3).

If there are any other logs I could provide, please let me know. Right know this is sadly all I got.
On top of that I was not able to reproduce it.

TheJeterLP · Answer 3 · 2020-06-03T19:13:17.000Z

Weird, I will check it later lerokko <[email protected]> schrieb am Mi., 3. Juni 2020, 17:19:

…

This is how it appeared in the console. I included the first line to show you how it usually appears. 2nd line is the Error message which I assume causes the malformed message (line 3). If there are any other logs I could provide, please let me know. Right know this is sadly all I got. On top of that I was not able to reproduce it. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA45KKNPDZ3P4RMI5XRXCMDRUZSXPANCNFSM4NQ556MQ> .

TheJeterLP · Answer 4 · 2020-06-04T16:33:30.000Z

Should be fixed with the new 2.5.3 version, thanks!

lerokko · Answer 5 · 2020-06-05T10:33:26.000Z

Thank you for the swift fix! I just updated to 2.5.5. (I hope my reply does not reopen this, I don't know how github works, if so sorry)

TheJeterLP · Answer 6 · 2020-06-05T10:43:56.000Z

No it shouldn't reopen, no problem :) lerokko <[email protected]> schrieb am Fr., 5. Juni 2020, 12:33:

…

*Thank you for the swift fix!* I just updated to 2.5.5. (I hope my reply does not reopen this, I don't know how github works, if so sorry) — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA45KKMNSICGH4ZRGZVGCZTRVDCYHANCNFSM4NQ556MQ> .

Share to