One of our group members is unable to set their display name as “Nazli” because it’s being flagged as inappropriate by the filter. We believe this is a mistake.
“Nazlı” is a common and meaningful Turkish name. It can be translated roughly as “graceful,” “delicate,” or “coy” — it’s a positive and respectful word, not offensive in any way. Since Roblox doesn’t support the Turkish character “ı” (dotless i), the name is written as “Nazli” instead, which is a natural adaptation for platforms using standard Latin characters…
We kindly ask that you take another look at this. It’s frustrating for our friend to be excluded from participating in our roleplay group just because the name they chose — which is a culturally meaningful and appropriate name — is being misinterpreted by the system. Everyone should be able to choose names that reflect their identity or cultural background. It’s a small but meaningful part of feeling welcome, included, and represented. We hope the filtering system can be adjusted to better recognize names from different languages so that players aren’t unfairly blocked from expressing themselves.
Additionally, this name has clearly been accepted on the platform in the past — for example, the following user has had the username “Nazli” for over a decade and a half, and they still actively exist on the platform today:
Expected behavior
We expect the display name “Nazli” to be allowed, as it is a culturally appropriate and non-offensive name. We hope the filter can be updated so names like this are not mistakenly blocked in the future, allowing all users to express themselves freely and participate fully in the community.
This name should not be allowed as the inappropriate term is a lot more popular and would be used as a bypass. While “Nazli” may be a culturally meaningful name, the substring it contains too closely resembles a highly sensitive and offensive term in English. Because of this, the filter is functioning as intended - proactively blocking names that could be used to bypass moderation, especially on a platform used by a younger audience.
This is not a bug, as the filter is deliberately blocking terms based on similarity to restricted content. The appropriate category for this type of issue would be Platform Feedback - Website Features, since it relates to how the display name filtering system functions, not a technical malfunction.
If the user would like to see this filter behaviour reconsidered in future updates, they’re encouraged to submit feedback in the correct category where the appropriate teams are more likely to review feature-level suggestions or improvements to the filtering logic.
Exactly what I was going to say.
The majority of Roblox’s user base is English-speaking — not Turkish or any other language where this name is culturally appropriate. Roblox will not adjust its global filter to accommodate a tiny fraction of users if doing so would enable a much larger percentage to abuse the system for bypasses or inappropriate content.
The filter is working as intended here — this is not a bug but an intentional safeguard, especially on a platform with such a young audience.
The most recent reply explained this perfectly: if you wish to suggest adjustments to the filter logic for cultural names, the correct avenue is a feature request — not a bug report.
Also worth noting: the style and tone of this bug report (especially the emoji use) unfortunately hints more at trying to bypass moderation than a good-faith request. The thread should be closed as this is not a valid bug.
That’s your opinion, but they’ve been allowing that username for over 15 years (just look at the Roblox user profile I linked above), so why shouldn’t it be allowed as a display name too?
I already explained above why it’s appropriate, and I even gave a real-world example to back it up—if the name were actually inappropriate, it would have been removed a long time ago. The word itself isn’t inappropriate, and the moderators clearly acknowledge that.
But honestly, this isn’t even just about whether it’s allowed or not. The real issue here is a filter adjustment problem, which is exactly what this report is addressing.
As for the rest of your reply—telling me to just “submit feedback”—that’s nonsense. This is actually a bug in the filter system, and it’s something we can and should report from here.
There are already multiple bug reports about cases where words that should be allowed are being blocked. In case you’re new to the DevForum, here are a few relevant links:
