The Weekly Recap has once again risen from the grave… and we hope you’re hungry for news!
Beware - we keep information at a high level within these recaps. For more information or to leave feedback, please comment on their official announcements linked below.
We’re excited to announce that Scalable Lightweight Interactive Models (SLIM) is now available in Studio Beta!
For experiences with instance streaming enabled, SLIM smartly composites and creates LoDs for streamed-out models in your experience, allowing you complete freedom to create more detailed and expansive worlds.
We’re expanding In-Experience Creation (IEC) to allow users to create, purchase, and save custom Accessories and Layered Clothing directly to their inventory from within your experience.
You can now allow your users to create, pay for, and save custom layered clothing and rigid accessories to their inventory using the same technical foundation: the EditableMesh and EditableImage APIs.
We’re launching the beta of Party Simulator, a plugin that lets you build, test, and debug party-based logic in Server and Clients playtests.
With the Party Simulator, you can validate any logic that depends on Player.PartyId, GetPartyAsync, or GetPlayersByPartyId without publishing or coordinating multiple devices and accounts.
With PlayerFeedback API, you can now collect feedback from your players in your experiences.
You can show a player the feedback dialog in your experience simply by calling PromptFeedbackSubmissionAsync API, and the player can enter feedback about your experience.
We’ve added a new optional parameter to the PlayerRemoving event called exitReason, which tells you why a player left your experience.
This gives you more visibility into why a session ended, such as whether a player left voluntarily, was kicked by the experience, or was removed by the platform.
We’re introducing two new API calls (GetUpcomingExperienceEventsAsync and GetExperienceEventAsync) that make it easy for you to automatically get event details, without having to hardcode event IDs.
Based on community input, we’ve decided to pause the planned changes to memory tracking at this time. Stay tuned for future announcements for improvements.
This month’s spotlight focuses on the creator of 99 nights in the Forest. How did the idea come to be? What are the developers most proud of? And why 99 nights?
This week started as the best week in Roblox history and then ended in a horrible car accident where flames spread as far as the eye can see.
——
My rating: 76/90
0 out of 10 for the age to chat announcement
Most of the announcements were fantastic like Emisives, SLIM, and multi line command bar.
However, the announcement “PlayerFeedback API: Prompt player Feedback In Experiences” seems to not work which makes it look rushed out the door. And the announcement “Encouraging users to complete an age check to chat” is a horrible idea.
——
When are we going to start seeing beta features implemented into production? It’s been over a month and the UI Stroke improvements for example still aren’t pushed, even though it’s a relatively simple beta feature.
Even if the fixes are relatively minor and things look ready in Studio the timeline gets drawn out a bit needing to wait on mobile app updates to actually push the button on full release since we don’t want to force people to do mobile updates every single week.
Almost all betas take at least a couple months to complete even if they’re on the simpler side.
I demand a recount. This week started as a usual W Roblox week, but it did not end in a car accident; it ended in a nuclear missile to everything Roblox stands for. So here’s my rating:
My rating: 27/90
Most of the announcements WERE fantastic, but they mean nothing since Roblox players will be unable to chat with each other.
Roblox decided randomly to destroy the core idea of their platform, making any updates they had before the age check to chat irrelevant in my opinion.
Please do not go through with this it is a horrible idea. Not only does AI age estimation NEVER work properly, but there’s going to be so many people who don’t want to upload a picture of themselves which will completely ruin chat based games.
This will cause people to be even more worried about data breaches and it’s just creepy when a game asks for a picture of you, especially when we’re talking about children.
There are much better ways to improve safety, this is not it.
This week looked really solid, all except for this little stinker right here. There are so many better, more effective, less invasive methods of making the platform safer than forcing people to reveal their identity online. Does anyone else remember when “never share personal information” was the golden rule of the internet?
Just for this one, I’m gonna have to give this week a 0/10.
Oh and I dont know if it’s mentioned but the Source Sans Pro font is now almost entirely absent from font selectors. You have to force the Enum or have an existing asset with it already applied. Even Source Sans 3 is gone.
EDIT: Apparently just rebooting the application returned it. I have no idea why. Studio works in mysterious ways.
Thanks, god bless, but I think even if you did, it wouldn’t matter because of the sheer amount of weekly updates we have to do with other apps, making me not care about them that much anymore.
Can I ask what a good range between forcing mobile updates is? A month?
Maybe different app stores get them at different times, or there is that effort to push for mobile-wide. There’s the universal app and whatnot, likely still differences that are non-store related, and a bunch of other points. Overall just interested in that.
Yes, it’s safe to assume we don’t let people get more than a month out of date.
Beyond that there’s a ton of factors that go into things, there’s no hard fixed rules on when the various mobile updates happen like there are for desktop.
- we keep information at a high level within these recaps. For more information or to leave feedback, please comment on their official announcements linked below.
My rating: 76/90