Imma be honest, if it was supposed to always do this, it did not work the entire time. It only disallowed me from uploading new assets such as audio or images, but it did not directly stop me from continuing developing on my projects.
The moderation check simply pings for account status and shows the new UI. It runs at start up (so we can tell you why you canât login) and then we also check during the autosave tick while youâre in the Editor. Before this, things would just kind of silently fail depending on what youâre doing.
But we arenât doing anything new with actual moderation here. Thatâs all driven by the backend.
I was referring to the server kick in that reply.
Yeah you probably could keep working in a non-TC session but autosave or any other number of server/endpoints were likely silently erroring out. If you are working in a local file, you could maybe have gotten a little farther but in the current Studio architecture we donât have a clean way of isolating backend calls. The Next Gen stuff puts us in a better spot to do this in the future.
I am aware, and thatâs is what I am replying about; I have continued work on my projects in a TC environment along with other developers while I was banned with no issues apart from the uploading. All of the scripts have saved and there were no silent errors, and I have not once been directly kicked from the TC servers.
What tab is that showing up in? Are you doing anything wacky with flags or mods?
Hmmm maybe it depends on the class of ban/warn. Our team didnât change anything with the backend or moderation system. All of my own testing was an immediate server kick to a blank Start Page and cryptic error messages on launch.
Is there plans to improve AI moderation? My asset called EasyDataStores keeps getting taken down because of the word datastores and I can appeal it once but using the same appeal message or wording it diffrently causes it the AI to not approve the appeal and itâs really annoying
With respect, the safety team does not use these processes themselves to the extent that we do. Perhaps they will read this back.
I have heard multiple anecdotes from notable developers getting caught up with appeals that do not pass in the recent past. This is for both cases that are simple harmless honest mistakes wherein the punishment is disproportionate for the harm it causes, and cases where there was a bad moderation decision but the appeal was stubbornly retained. UGC creators I know of seem especially subject to this frustration often. If I am hearing these anecdotes in my small closed circle of power users, I expect them to be happening one hundredfold for developers without support circles.
The bottom line is that the standard for moderation is to deal out wildly disruptive consequences, and to a regular developer who is just trying to work, are often just for innocuous things, or accidents. These things donât warrant losing an entire workday+ waiting on someone with little sympathy to argue with you about your fate. The foundation of how moderation effects are applied is simply wrong.
Wait, how did you get that popup as a test popup?
Is this going to apply to the Roblox app as well? Because if someone gets banned, they currently see a message that reads something like âUnable to connect to the serverâ which usually coincides with an internet connection problem. Happened to me several times, and I had thought I was having issues with the Internet.
Also, if someone gets banned while in Studio Team Create, a good improvement would be to display in the output that an account received moderation action, so others know not to add them again. If someoneâs account gets moderated for things like inappropriate behavior, then they clearly canât be trusted to be in the Team Create session in the first place.
I wanna give credit were credit is due by saying this is a nice feature.
last time I got moderated the only thing suspicious was that my avatar didnt load and ârejected requestâ errors popped up, I thought roblox was just down until I went to the website to see a nonsensical 1 day ban. so at least now with this update I can know immediately what is actually going on.
but I think the real core of the problem is how moderation is even conducted.
to quote the statement above: âif your account recieved a moderation warning or ban. our intent is to offer a faster way to appeal incorrect moderations so you can quickly return to creation and development work.â
there are a few problems with this, first and formost this feels like treating the problem not curing it, granted its better than nothing.
secondly appealing moderation is a mixed bag, support will either unban or keep you banned and never give any specific details on why you were banned and what you can do specifically to fix the problem. for example if something is wrong with your audio why not tell developers exactly what is wrong with the audio and how you can fix it rather than telling developers to buckle up and take the ban.
Yeah and Iâm mostly just the Studio guy but we are working with our safety team on this and Iâm sharing the comments/notes.
Yes to this please. A button to close Studio near the log out button would be nice, as Iâd rather not be logged out (logging in again becomes annoying for various reasons).
this is roblox job , it is really needed to check if the asset is moderated or not before uploading it