I think a better solution is to instead impose this extra filter on the TextChatService CoreGui and / or provide a function to implement it easily into custom GUI equivalents as well. Developers are probably going to be forced to use TextChatService for all conversational messages in the near future (around April), and there may be other, non game-chat related, reasons for wanting to use characters like the verified badge in messages.
for work u must put experience language to VIETNAMESE
The filtering should also be done server-side, since everyone knows no server-side protection means exploiters will always find a way around it.
im thinking adding a server side way to anyone putting the verification icon gets kicked so they stop trying
Or just make it so their message doesnāt showā¦
If you find yourself adversely affected by this issue, Iāve released a faithful recreation of TextChatService that addresses this issue. OpenTextChatService - Open-Source Implementation of TextChatService. While it is pretty simple to implement your own custom character filtering (and you certainly donāt need a custom text chat implementation to do so), Iāve included it as a built in feature for convenience. This is on top of a bunch of other bugs and performance issues that Iāve addressed. If that isnāt your jam, something as simple as this will do the trick though.
local function filterSpecialCharacters(text)
local new = text
for i,v in {utf8.char(0xE000), utf8.char(0xE001), utf8.char(0xE002)} do new = string.gsub(new, v, "#") end
return new
end
game:GetService("TextChatService").OnIncomingMessage = function(message)
message.Text = if message.TextSource ~= nil then filterSpecialCharacters(message.Text) else message.Text
end
That being said, I do hope this bug is addressed formally since this isnāt something developers should have to worry about.