Hey all, we’re no longer maintaing the legacy chat system so unfortunately cannot get to fixing this bug. Please consider migrating to the new TextChatService, and if that is not currently feasible for you, I’d recommend the workarounds other developers have graciously shared here.
Would it be possible to add some disclaimer to the .Chatted documentation to redirect developers to the TextChatService API? It would probably be infuriating for inexperienced or uninformed developers to use .Chatted without knowing of a better alternative and suddenly have to deal with this issue