Yep. I also just tried it as well with the same result
2 Likes
I have tried that in my video
Perhaps this issue is specific to certain users (which is odd if it was the case)
Nvm only work on studio, somehow peoples managed to bypass
1 Like
Studio has no filter at all. You would have to test it on a live game
so i count this as a found bypass then
from doing my research its a glitch that only works if you set your roblox language to Vietnamese it will allow you to use a symbol and paste the verify badge
1 Like
No, this is tagged in a real game.
1 Like
Not always though. It seems to be the only reason why this report was made.
I know. I even said this myself.
1 Like
It isn’t really a bug though. Users are allowed to chat with unicode character
Not really, the character is tagged at the first place for preventing usurpation of verified identitys.
1 Like
You don’t understand the report, some peoples at the time found a way to bypass the tag which can cause some usurpation
I was just about to report this until i noticed this post
It’s actually a method used from this post
It’s just a character that’s normally censored but exploiters can go through the filtering
It’s this icon: “”
Even tho you see the “:” difference. It easily tricked people into getting scammed
Also “appearantly” you just change your language to remove the tags in certain cases
1 Like
Malicious users are abusing a vulnerability to impersonate others with a fake verified badge, due to it not getting filtered by the chat:
I’ve tested in a random game to see if other players could really see it in chat:
Edit: This seems to also work with the Robux and Premium unicodes.
Reproduction steps are in private content for staff
Expected behavior
The verified badge unicode should always get filtered in chat.
A private message is associated with this bug report
5 Likes
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.
1 Like
for work u must put experience language to VIETNAMESE
2 Likes
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
1 Like
Or just make it so their message doesn’t show…
1 Like
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.
2 Likes