Great question - I spend a lot of time on genres as everyone here knows. Regarding making genres more community-driven, we’re evaluating crowdsourcing feedback from verified players to help classify experiences beyond genres.
But to provide more context on what we’re doing for genres, we’re taking a two-pronged approach. First, we’re making a taxonomy that makes sense for Roblox and honors the genres that are popular and unique to our platform. You can expect similar high-level genres as we have today, but we’ll have more nuanced subgenres — and we’ll share more information on the full list with you on the DevForum soon. So for example, we’ll have an Action top-level genre, and we may have a ‘Battlegrounds/Fighting’ subgenre since that is a very Roblox phenomenon. Second, we’ll be revising this constantly as new genres emerge. Themes, gameplay mechanics and aesthetics often transcend genres, and we will want to call attention to what’s trending on Roblox in new and interesting ways.
We’re excited about revamping the Asset Manager so everyone can work more efficiently with their assets.
Our plan is that Toolbox will be focused on the Creator Store, while Asset Manager will be a separate view that replaces the Inventory tab now in Toolbox. Asset Manager will have more features than the Inventory tab now supports – for instance, better handling of large asset libraries, better search capabilities, and bulk editing support. Please share your feedback once it goes live!
Great question. When a creator curates an avatar on Marketplace, the original creators of the items will get the same 30% revenue split that currently exists. The curator of the avatar is not considered the affiliate. So, if a creator curates an avatar with all items they themselves published, they would get 30% of the sales of that entire avatar.
We support a wide range of creators, many of whom face challenges with session locking, retries, and managing player data. Creators shouldn’t need to be distributed storage experts to build great experiences.
Some creators need high-level solutions, while others prefer low-level primitives for greater customization.
For high-level solutions, we’re focusing on player profile storage and improving integration with Roblox systems like economy. For low-level, we’ll continue enhancing data store primitives, including exploring atomic transactions for trading systems.
We’d like to hear more about your batch write use cases!
Thanks for the question! We know there are still issues with 2D clothing and modesty layers. While we removed the requirement for modesty layers for certain avatars like inanimate objects and animals, we’re still working on an overall long-term plan for 2D clothing and modesty layers, particularly for its impact on bundles. We can’t share an exact timeline at the moment, but we are actively engaged in ensuring the safety of our avatars across the platform and addressing this creator need.
Thanks for this important question. We view anti-cheat through two lenses: what can we provide automatically to all experiences, and what tools can we give you to make your own anti-cheat decisions.
Over the past year, we’ve continued to improve our Windows anti-tamper system, Hyperion, which helps prevent many cheating exploits from running automatically. While we can’t disclose specifics, we are developing multiple mechanisms on Android and other platforms to prevent, detect, and respond to exploiters, which will also work automatically.
In the long term, our goal is to provide an anti-cheat toolbox for developers that you can customize according to the level of protection needed for your experiences. We want competitive experiences to have all the necessary tools to ensure a safe, fun, and fair gaming environment.
Delivering this goal started with the Ban API, which automatically works with alt-detection, and we are working on systems to provide you with additional tools to detect and take action around cheating. One important part of this is something we mentioned at RDC: better support for server authority. This is in active development, and it will help mitigate things such as physics exploits.
We don’t currently have any plans to release an offline version of Studio. We have listened when folks have told us about their problems working with patchy connections, and we will continue to make Studio more robust and performant in those scenarios, but to run Studio for extended periods you will need to be connected to the internet.
Thanks for your feedback. The team that owns Talent Hub has been hard at work on top creator pain points like collaborator permissions, group revenue sharing and experience ownership transfer. We don’t have any major Talent Hub updates planned for this year, but stay tuned in 2025 for improvements that will make it easier to find new collaborators.
Once it’s enabled, it will work in Studio both while editing and play testing, automatically. We’ll announce it on the DevForum when we fully roll it out and hope you like it!
Yes! While we’re still in the early stages of working on the 3D Foundational Model, our first steps will be to generate individual 3D assets from scratch, and in the longer term, we plan to work on helping create full scenes.
Our goal is to build great support in Roblox Studio, out of the box, for working on your code as files. This means letting you use your favorite IDE, and its plugins to edit the code in any Roblox project.
Before the end of the year we plan to share the first preview of our new approach, as an opt-in Studio feature. As this is a very early preview this won’t support all of your workflows, but we want to make sure we are developing this transparently and sharing our progress as we go to continuously get feedback. This build will include basic support for right-clicking on a script, and syncing it bidirectionally with a file on your disk when you save.
Like you said - we’re late on this. The real reason for this is - we weren’t happy with our first attempt and went back to the drawing board.
For those of you who are interested in why - I’ve included some more info in the drop down below.
What was wrong with the first version of File Sync 1
File watching is hard, bidirectional sync with file watching is even harder when you factor in Team Create. We tried to skip this by making the file sync manual (i.e., click import / export). This led to a pretty janky workflow with a high risk of data loss.
We tried to provide one tool to sync scripts in the whole DataModel to files. The challenge is that the DataModel is not a file system. Tools like Rojo have invested a lot of time building practices / conventions for this. Our attempt to do this in a way that would work on any Roblox project was not convincing.
File sync was some widget with controls you needed to operate, rather than being something that fit into your workflow more naturally
For those of you who don’t need the details - the short of it was, the feature didn’t feel right. Those in the community that volunteered to test it told us the same.
As we gather feedback from this first preview, and build out our full roadmap, we’ll release our progress regularly.
Thank you for sharing your experience with us. We take the privacy of our users very seriously and are evaluating changes to our verified badge feature based on what we’ve been hearing from the community. We will share more in the future, but would love to hear your thoughts around what functionality you’d be looking for here.
We are not currently looking into this, but thank you for the feedback. We’ll add this to our feature request list, and we note all the interest during this AMA!
We want to improve our material system over time, which may involve shaders or other approaches (e.g., parametric materials), and we want to ensure that our solutions work performantly across all platforms. While we do not have anything related to shader support in active development, we may potentially revisit this in the future. Thank you for the feedback.
In Q4, we’ll pilot our Shopify commerce integration with a small number of creators and brands. Early next year, we’ll expand to enable any eligible creator to sell physical merchandise directly from within their experiences to users in the US ages 13+.
Creators will be able to attach a digital benefit like an avatar or in-experience item from Creator Hub when you set up your commerce products. You’ll also have access to in-experience APIs and webhooks to help you manage merchandising, checkout and order confirmation.
Hey, thanks for the suggestion! This is not currently on the roadmap, but we will certainly look into something like this if we end up doing more mega posts like the RDC wrap-up in the future.
Thank you for this question! We are piloting an avatar creator feedback group now and hope to roll out a broader channel in the near future. More generally, we’ve been trying to spend more time with UGC creators at events, such as at Gamescom LATAM and RDC, and I’ve definitely been learning a lot about the challenges facing the community.
We are not currently working on dynamic clouds, but could you let us know if you have specific feature requests? We’ll make sure they’re on our radar for consideration and future roadmaps.