Continued Asked & Answered
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
S:
Here’s a non-built-in custom solution for something similar:
Fallen Character/Parts Recall Height [v1]
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Q:
A:
Thank you for your question. We constantly review floor prices to support a healthy and growing marketplace economy. We recently made an update to price floors for avatar bodies and heads and are seeing positive results. We plan to do more of these in support of the ecosystem.
Q:
For Audio APIs, will there be an option for voice chat without the proximity effect?
Pertaining to UGC, for Improved Avatar Face and Body Tooling and Bodies and Animated Faces, will imported armatures and bones ever have support for bone drivers and bone constraints? And for Powerful search and browse capabilities, will that also apply to the UGC Marketplace and include features such as boolean search operators?
A:
Yes, with the Audio API, there will be options that provide more control over voice, allowing you to implement changes like fine-tuning distance attenuation, building features like walkie-talkies, and enabling non-spatialized voice.
For avatar tooling, we do not currently have plans to support bone drivers and constraints on imported armatures. If you can expand on your feature request though, we’re happy to consider it!
Lastly– for the powerful search and browse capabilities we outlined in the Creator Roadmap– those are in reference to the homepage and experience discovery. Not all of them are applicable to Marketplace, but we do plan to improve the discovery and usability of avatar items. This includes algorithm, UX, and interface improvements to help with discovery and navigation.
Q:
Are there any plans to add screen space reflections?
A:
Thank you for the question. This is not currently on our roadmap.
Q:
Can we please get closure on the car company dilemma currently on the platform? We have had 0 closure by you guys on the moves going forward in terms of vehicle models. There’s many games in development, or are already out, that do not know what to do: custom models or stay with the debranded vehicles? Of course, going custom is always the safest option. Are games allowed to use debranded vehicles as long as it is debranded, not a gamepass/robux locked, and a different name? Or should we stay completely custom? I understand this might not be your area to answer, but an answer is better than no answer.
A:
Thanks for your question. Roblox respects intellectual property rights and operates a robust notice and takedown system that allows rights holders to report content when they believe it violates their IP. Before you upload any content to Roblox, you should make sure that you have permission to use any 3rd party content that is included in your creation. If you have specific questions about what is or is not IP infringing you may want to speak to an attorney.
Q:
Are there any plans to bring emission maps to Roblox in 2024?
A:
Emission maps are on our longer-term roadmaps, but we are not actively working on them now. Our primary focus with lighting is on bringing Future is Bright to Android and releasing our new GPU Lightgrid system, which brings high-fidelity lighting to a wide range of devices at high performance.
Q:
Unknown question from @colbert2677. Only found question appears unrelated.
Question was related to “genre sorting” but was removed by the poster as a similar question had already been asked.
A:
Thank you for the thoughtful feedback. We acknowledge that you are not getting the response you would like on your earlier feature requests. We are committed to better communicating discovery products related changes via blog posts, AMAs, and other formats, starting this quarter. We will also share our active work through the creator roadmap (Roblox Creator Roadmap ).
To clarify, our recommendations look at a number of signals to match users with experiences they will love. This includes long term engagement, retention, relevance, and monetization, among other signals. We have also made improvements to accelerate the discovery of new experiences that are showing staying power. Several new experiences have achieved success thanks to these improvements.
We mentioned earlier that discovery by genre is something we’re rethinking. Genres are very fluid on Roblox as we see creators evolve their experiences, and users on Roblox look for experiences by other attributes (like themes). There are also diverse opinions on how genres should be defined, and we also find that genres can be easily abused without the right safeguards. We are now thinking about how to build trusted sources of genre information: from creators, users and other expert sources, and how to do that at scale and in a way that can’t be abused.
Please continue giving us feedback.
Q:
With regards to Studio Luau File Sync Beta, there have been rumors circulating amongst developers and staff that Roblox is working on a Protocol Buffer (“protobuf”) based file format for places and models.
The purpose of protobuf is to enable multiple community tools to easily process these files without having to maintain multiple ser/des implementations, as is the case with the current binary (RBXL/RBXM) and XML (RBXLX/RBXMX) formats in tools like rbx-dom, rbxmk, Lync, and others.
The Question: If we are to see this new file format incorporated into Roblox, will it be added alongside the Studio Luau File Sync Beta, and if not; where on the roadmap can we expect it to be added?
Thanks for the AMA!
A:
We realize the limitations of our current serialization formats and are actively thinking about what is needed to enable a rich ecosystem open to third-party tools. While we cannot commit to an exact serialization format at this time, our vision is that creation on the platform is open.
When we release the Studio Luau File Sync Beta, it will include a preview of a new format to help test our assumptions about what the ecosystem needs. It’ll take time to refine this as we evolve both solutions while maintaining backward compatibility. Our long-term plan is for the finalized format to be released alongside the full release of Studio File Sync.
Stay tuned for more information here, we are very excited to learn from each other as we build out both products!