Our vision is that everyone should be able to create on Roblox, no matter the device they’re on.
Later this year, we plan on releasing a new starter experience that focuses on creation and works well on mobile devices. It’ll be a simpler way to create instead of using the full power of Studio. Our plan for that experience is to make it collaborative, sharable and able to persist creations.
Also, we’re moving more UI components to Lua, which will simplify future integration of Studio tools and features into the starter experience.
This is an excellent question. We are re-evaluating our permissions models and how they interact with content in an experience (including a player’s avatar), but we don’t have a concrete answer to share right now. As we build out our permission system, we want to unlock additional capabilities while keeping creators in control of their IP. We also want to ensure the system can support the use cases at scale. Thank you for sharing what you’d like to do – we’ll add this to our list of use cases!
We understand catalog asset bugs are a concern for the community: we appreciate these reports. There’s always room to improve and do a better job communicating here, and we do intend to act on these.
There are different opinions about catalog asset bugs: some of you want us to leave these items as they are, while others want things updated. So we need to develop a system to determine which ones we ought to fix versus leave as part of our DevForum bugs effort.
That said, with limited resources, we can’t always fix everything we’d like to in a timely way, so we appreciate any patience you can offer. We’ll prioritize fixing the most important assets first and know that we’re otherwise working on the most impactful issues.
Good question. While we do not have this on our roadmap, we are revisiting this area as we look at enabling more types of content on the platform and as we see creators do impressive things with our UI framework to build 2D content. While we cannot commit to anything right now, please share any further thoughts on what you would like to see!
Since the RDC announcement, this feature is already live (in closed beta) across a small number of experiences. We’ve partnered with two commerce partners (including Shopify) to enable these creators to sell physical merchandise within experiences, and some of these purchases are being bundled with virtual items.
We’re planning to roll this capability out with Shopify more broadly in the coming months, and are finalizing the eligibility criteria to enable the bundling of virtual items on purchase. We’re still working on the eligibility criteria, and it might include the things you’d expect like ID verification and average earnings/DAUs as we scale the feature.
We’re prioritizing OpenCloud API additions by community demand, and group membership management is our most recent launch. DevProduct management and timestamps for InventoryItem are in the works. Please share feature requests for new and existing APIs so we can enable you to automate more.
While cleaner API definitions are great, we recognize there is established de-facto use of ‘legacy’ APIs, and automating with cookies is a significant pain point. We are prioritizing better docs and the elimination of cookies over an overhaul of all functionality to OpenCloud v2 resources. For example, we added API key support for many ‘legacy’ endpoints recently and will be expanding on these.
We are reworking the Cloud Reference documentation to be task oriented - e.g. if you want to automate tasks around group management, you’ll be able to see all of Roblox’s groups-related APIs with auth scopes, stability guarantees and so on within a single page.
In addition, we’ll be building on the work we started to enable OpenCloud use in-experience, allowing more APIs to be used. We are proceeding carefully here to ensure authorization is intuitive, but also fully controllable and auditable by the owner.
Stay tuned for roadmap updates as we make progress on shipping these improvements.
We’re considering this and know that there are some constraints for us to work through.
We also are looking into offering lower price options for paid access experiences along with other enhancements such as free trial mode. In addition, creators will continue to have the option to publish experiences that are paid in Robux only.
We’re still beta testing the new Next Gen Studio UI and are a few months away from a full launch! We’re aiming to launch stylesheets and our revamped asset manager around that time too. We’re excited to get these into your hands and will let you know as soon as they’re launched!
We care about this area a lot. Our current focus is speeding up our action time once we detect an exploiter.
In parallel, we’re working on improving alternate account detection, which we’ll integrate with exploit detection/action. We’ll keep the community updated when we have a date to share!
We released Announcements last year to support rich, long-form content that is shared from a connected Guilded community. The feature supports hero images, up to 1,000 characters, line-breaks, emojis, reactions from your community, and the option to notify community members that have opted in to receive notifications.
For creators who enable this feature, Announcements will replace Shouts on the Community page. For more details on how to set up Announcements for your Community, see here.
Brazil is an important region for us. It’s a larger market, including for active Roblox devs — it’s a growing, vibrant community. It’s a priority for us and we will plan to share more when we have.
Block-based coding systems that enable you to “click together” functionality are a really cool way for non coders to start building experiences. We don’t currently have anything on the roadmap, but we’re starting to look at how systems like this or Node Graphs might be useful for areas like audio or animation programming where they fit really nicely, even for experienced developers.
While we aren’t currently prioritizing building an official ‘visual coding’ system at Roblox, we are looking at how we can make Luau easier to write with tools like Assistant.
Over the past few years we have seen the community explore this problem space through plugins. One example is EventBlocks. We’d love to see more work like this and are very open to feedback about how we could better support these tools.
Our design team is currently looking at updating the layout and spacing based on community feedback. This is currently available in beta as Next Gen Studio Preview - go try it out! Among other customizations, we’re looking into the possibility of different density options.
This is one of our goals with server authority, as part of a broad effort for more security against cheating and exploits. You can check out this post for more info, and we’re hoping to share more on this in the summer. This is in addition to the work that we currently do to improve our prevention of cheats and exploits across Roblox.
We’ll do this differently, as this post was in reference to our upcoming asset privacy beta launch, which is coming in the next few months.
The launch for decals, images and meshes will not be rolled out automatically for previously uploaded assets, as we did for audio. When a creator opts into the beta, they’ll have the option of enabling privacy for newly uploaded decals, images, and meshes - they’ll be in control.
There’s also a bunch of improvements to reduce friction and improve collaboration workflows using “restricted” (private) assets, including audio. That includes “restricted” assets that are used in Models, Packages or Mesh Parts. Restricted asset capabilities and controls will be consistent across Audio and other assets.