No inappropriate text will be created from numbers, so I do not believe it needs to be filtered.
However, I understand your concerns. I’m sure we will get a response from DevRel eventually.
GUIDs shouldn’t be inappropriate as the GenerateGUID function is used by Roblox. If an inappropriate ID comes from it— that’s on them.
Yes, but I’m slicing off most of the GUID so that I have anywhere between two to six characters that are on the very start of the GUID; would that then make it modified and as a result become my responsibility to filter?
I don’t see how that would be any different than using the full GUID as it would still show the same word(s).
I guess the main problem here is like the word “Assessment” for example, if you take the first 3 characters of that word you get something mildly questionable for some people. It all just depends how its generated and the context you take out of the generated string which (since its random) can yield potential TOS breaking results.
I made a license plate script a couple years ago, ill look at it to see if it abides by the rules and if it does ill yoink it into your DMs so you can look at it.
I mean I’d only be chopping off numbers, not any letters or words. The letters and words I can automatically generate myself and then put those through Roblox’s filter as it actually has a high chance of not being inappropriate, and I can just discard the inappropriate ones. It’s the numbers that cause every randomly generated license plate to be rejected/filtered out.
See my earlier reply. A random generation system by Roblox is held to the same standard as a developer’s. If an inappropriate phrase is generated, you are held accountable for it because it’s in your game and you will get moderated for it. It’s filed as an avoidable offense (e.g. using filtering before displaying).
1 Like
or simply, if you get a filtered license plate, you just regenerate it, simple.
This is bad advice and doesn’t resolve the root issue. Please don’t suggest things like this.
Regenerating license plates doesn’t address the problem which is that a majority of randomly generated license plates can and will get filtered when it comes to broadcast-based filtering, as it needs to be inclusive of all age groups (broadcast is the most restrictive filtering option).
It’s also worth mentioning that the chat filter is internally a web call, meaning that filtering takes a certain amount of time. Regenerating license plates until a non-filtered option appears will increase the time it takes to get a valid plate and that’s bad for UX when users are expecting near-instantaneous results.
2 Likes
If nothing else works, you could manually generate a large number of possible number plates, review then manually and chuck out any with bad words, and use the remaining ones as a “pool” of number plates to be randomly chosen from (i.e in a huge array stored somewhere)
Obviously, this would take time and limit the number of random number plates you can realistically include, so it’s a bit of a sucky solution
This is how I already was doing it, but every single attempt was filtered because of the numbers in it. That leads us to the dilemma I’m at now.