It is not ok to shadow ban an experience silently.
At the time the description was submitted, the system should reject the update, if it is going to cause the game to be banned. Instead, the sus description was accepted by the Experience settings form, without notifying the Dev that they had included something that could cause their experience to silently have all the traffic drained, without knowing why, what triggered it, when, or how to fix it.
This creates an environment of distrust where I have to constantly check whether my game has been silently banned by Roblox, after a legitimate update to my description.
Roblox needs to do more to inform a Dev when their experience has problems, especially to the point where it is de-listed from Discovery. Majority of Devs, including myself, want to play fair and have an experience description that is informative and relevant, and updated frequently. My game has been affected by this issue, but it does not have “spammy keywords” in the description, but I do feel my stress levels rise, when I have to update my game’s description, because in the past that triggered a lot of struggle to recover from the damage done to being totally un-discoverable.
Can we please look at the form where updates to the Experience Description are submitted, and cause a validation error to occur if it is possible the text would trigger a shadow ban?
Can we please send a notice to the Dev when their Experience is de-listed, so that they can have a trigger to take action, without feeling the need to constantly monitor whether they have been banned? It would be helpful to have additional information in that notice about WHY the ban occurred, so the Dev is empowered to fix their experience in a timely manner.
This may not be considered a bug, but the current process is not acceptable either. Thus, I think this still should be looked at by a Roblox engineer because it represents a broken interaction between the Dev and Roblox with ample room for improvement.
