This is pretty much a bump from this older report my friend made (they didnt age check, hence why I report this bug for them).
After having applied some changes to their resource, such as removing HTTP requests, they finally managed to get the model on the toolbox.
However, the issue returned yesterday (July 10th ~4 PM GMT+0), after updating the free model. The model has been hidden from search, and only copies and obfuscated versions of their resource are now shown.
As mentioned on their topic, the name of the resource is Fork3X.
We have tried multiple things to restore the model, including:
Reuploading the previously approved, version. This was fruitless.
Using version history to restore the previous version. This worked, and so according to my friend, this shows that the issue comes from a change to the moderation
Removing most new things. This was fruitless again.
Content that may be against the creator store guidelines isnt included in the free model, and shared otherwhere. The source code can also be found here (the addons folder is empty when publishing the free model).
It would really be nice to have an answer asap. My friend’s resource has a small success, and many people rely on it. The longer this stays unsolved, the more people might insert fake and malicious versions of this resource.
Expected behavior
Free models that formerly were rightfully approved should still be able to get updates, without getting incorrectly hidden (and without any way to appeal this). At the very best, older versions should still be approved.
Hello! It does seem you can search the specific resource now: https://create.roblox.com/store/models?keyword=Fork3X+Building+Tools+[F3X+MOD]. We have been dealing with a separate issue from our flaggin system that likely had that asset not show up in search which should be resolved now. In terms of the expected behaviour, there is a concern that an updated asset can go from following our policies to becoming violative which is why we cannot simply allow all future versions to be approved. We are working on upcoming improvements that should help address issues with genuine assets. Until then, though we know it is frustrating, we recommend appealing future versions that are flagged to quickly resolve issues.
My friend indeed noticed that the problem has been resolved, and theyre really glad to know that the visibility issue wont hamper their resource anymore.
They however had one question concerning the appealing part. They dont really know how to appeal visibility actions concerning free models. Do they have to appeal by selecting “Appeal a Decision”, then “I was moderated for content or assets I created” in the Support window?
On the configuration page they should see an alert banner above the Distribution toggle with a link to the appeal page that should have a generated violation with the title “Your model broke the rules” that they can appeal through or just go straight to the appeal page here: Appeals Page. In this instance though it was a regression in our system which should be fixed now. Always happy to reply and help
