Yeah, I tested this yesterday on a plane script. I put a bogus ID into the sound field and the plane just errored and didn’t work. This is easily fixable but how many old games are ‘devless’ and wont’ be fixed. Not good.
oh lordy this is going to break too many games
way too many…
its almost like they didnt contact a lot of the staff team while making this update,
This is the kind of music they’re gonna label as “horror music” and expect front page games to use and player’s to enjoy
This update is honestly so terrible, my game had to be privatised because of it since there is over 300 assets that need replacing…
found this gem somewhere and i think it pretty much proves a point that the audio uploaded by roblox themselves will actually be annoying to sift through
I’m sorry but idk why I found this funny LMAO
Oh boy, if Roblox is gonna force us to use these they should at bare minimum put SFX or SONG in the title to clarify what it is for us.
This really needs to be stopped.
I see the vector despicable me gif in google oof
im not sure about this but i am sure that its gonna cause a lot of pain for devs with a flood of library-collected audio stuff (I guess)
Not a bad update, but how will this affect the hundreds of thousands of games that either utilize or sell access to radios where the client can play an audio on the server? It seems like the privatization of audios will prevent the game from pulling that audio to play on the server, destroying the attraction of those features and diminishing the value of that game pass to anyone who already owns them. Is this just sort of a “tough luck” situation?
We’ll just have to wait and see for the future of radios for now. Once March 22, they said changing audios to public will be halted for a bit untill they find a better solution, so perhaps they may come back.
How are we 2 days in with almost 3300 posts in without a proper response? This is absolutely embarrassing for the team at roblox to keep ignoring feedback from the majority of the community and ghost us.
I get roblox doesn’t commonly reply to backlash, but this is the thread with the most posts in the announcements category. You’d think at that point it’d stick out like a sore thumb and roblox would be scrambling to create a professional response.
But no, here we are, left in the dark.
I know that they will be set to private automatically, but if I change them back to public because I am the creator of the group as well as the audios on the group.
im betting you my life savings they aint gonna respond even after 10k responses
You can’t set them back to public though. That’s the problem. They are temporarily removing the ability to put things back to public until they quote “find a solution.”
Fun fact, the post has 3471 posts, by looking in the url
Which means mods are deleting criticism less gooo
Pretty sure it was just rule-breaking replies. If they were actually deleting criticism, 3/4ths of the replies would vanish
You’d know if slowmode wasn’t here, there would’ve been like double the amount of responses already, and we still will get not even a single nudge.
its almost like they KNEW this update is bad and they would get backlash
Please Roblox, we’re begging you, please cancel the forced audio privatization immediately.
90 percent of experiences on Roblox will either be silent or non-functional if this happens. Players and developers are already losing money because the developers have had to make their boombox gamepasses off-sale, and searching for sound effects and game related music rather than bland music will be much more difficult. The audio marketplace will be nothing but Roblox owned audio and UGC audio less than six seconds. Does that sound like a good idea at all? Why not let audio uploaders choose whether they’d like to lock their audio instead of doing it for them even if they encouraged people to take them?
Trust me, that means they wont do anything. We’ve seen this with forum removal where they said they were going to make a new forum but never did. So you’re never going to be able to make audios public after this update