I know this is a very frequently asked question so I’ll post it here and ask on the behalf of many, so it can be answered officially:
Will there be any plans on increasing DevEx rates? The economy is changing both in ROBLOX and the world itself, however DevEx rates don’t reflect the changes. I won’t go too much in detail, but the post below gives great reasons:
https://devforum.roblox.com/t/roblox-needs-to-increase-devex-rates-and-why/1533966/
Privacy is of utmost importance. When a government-issued ID is scanned for verification, an anonymized value is generated, which allows Roblox to verify ID without risking exposure of the user’s real identity. If you’re 13+, ID verification is sufficient to access all features and capabilities for creators on Roblox, excluding 17+ content and experience development.
It’s important to note that age verification is entirely optional. Creators can continue to enjoy Roblox without going through this process, and if they’d like to gain access to features that may be limited/restricted by age, they can consider ID verification.
Hi, thanks for replying!
It’s optional for now, but as Roblox rolls out more and more important features locked behind this wall, won’t a time come when the non-verified development experience is so kneecapped and so limited that developers are borderline forced into verifying?
Are there any plans to increase server memory? It’s no secret that games in ROBLOX are getting much more realistic functionality wise and visually, and I feel like we should be equipped with more memory to maintain these higher realistic projects. I understand a lot of it is on the developer to optimize and use resources sparingly, but eventually some developers will hit the ceiling of the current 6.25 GB limit of server memory (before the server crashes when it hits the limit).
Here’s a post with better reasoning and in-depth detail, along with many people wanting this:
With future changes to voxel lighting, is the implementation of a more visible representation of PBR normal map effects planned? Currently, that’s the main thing (other than translucency) holding back my projects that use Voxel lighting from a much higher standard of quality.
Roblox Connect will launch with one to one functionality, with API’s available to developers. After launch we’ll be working to expand the capabilities to include group communication.
Will we ever be able to register be able to register and deregister controls in the help tab of the Roblox menu?
We are working to make highlights available on all devices. There are no plans to increase the number of highlights supported at the moment but we know this is a common request and are looking into how to best expand in the future.
I believe you’ve misinterpreted the question. Currently, creators who accidentally set their age to be <13 are LOCKED into that age group, and cannot fix the age, even if they have an ID proving they are above 13 (hence “verifying with ID”)
Our major focuses right now are bringing Future is Bright (FIB) to Android by end of year and rolling out a new GPU-based lighting system that looks much closer to FIB than the current shadow map system, enabling better scalability. We’re also doing a lot behind the scenes to significantly improve terrain performance, as well as other improvements to physics and environment like grass length and wind.
Thank you for sharing the specific aspects for improvement, we’re always trying to work on smaller improvements in parallel with our larger features.
Roblox needs to listen to the community more about discovery. What is Roblox doing about that? I’d like some form of discussion with those who work on discovery and the entire community.
Here’s something for reference: Discovery does not respect the community, and desperately needs to change - #2 by Reditect
We are looking at ways to grant creators more control over memory usage and other aspects of the experience runtime. This means better tools to understand current consumption to assist optimization efforts as well.
Will there be any form of decrease in Roblox’s Fee and/or Tax percentage?
At the current moment on our platform, we make a lot of purchases even if it’s not development-wise.
I made a pretty clear board summarizing the entire list of whatever I could find that has a fee or tax.
I apologize in case this question is insulting in some sort of manner.
actually the tax for UGC items is 70%, meaning we (UGC creators) only make 5 cents for each dollar spent
Why can’t we as creators view the sales of our assets in the creator dashboard or the API?
thanks for the question. it’s a big change, and we’re being extremely thoughtful about changing the requirements. we are still finalizing the requirements for avatar items for opening up creation to everyone. the economy team plans to share a detailed post with final requirements in the coming weeks.
Are there any plans in future to allow for developers to let our users select a Lighting technology of their choice? Currently, the main game I work on uses voxel lighting due to wanting to remain accessible to as many users as possible, but we’d love to be able to use future lighting for users who are willing to accept the higher computational cost. To my knowledge, this couldn’t be changed without rejoining a game as the lighting technology gets initialized during client loading, but would still allow for much higher visual fidelity without a reduction in player counts due to players perceiving lag.
At RDC 2022, the common sentiment amongst the Studio team that I talked to was the desire for developers to use Roblox Studio and no 3rd party tools (VSCode etc.). With “Fitting Your Workflows” it seems that Roblox’s thoughts on 3rd party tools may have changed.
Is the goal to enable developers to use 3rd party tools? I’m namely interested in VSCode as Rojo has been the only option for 3rd-party coding for years now.
My question is very deep-rooted, as of recently we have seen Roblox pushing a lot of harsh updates that impact our workflow deeply, think Experiences using Marketplace Items - Policy update, the polar-opposing opinions (both positive and negative) of the new CoreGUI “upgrade” (discussed here) and the previous audio-privacy update.
These “updates” are major changes made to developers’ workflows, sometimes with little to no notice and seemingly no developer consultation before release. Is there anything being done to reduce the amount of these harsh updates and / or ensure that no developer is unfairly impacted by a decision made that clearly did not respect the creative vision of their experience?
