Allow Trusted Developers to Modify Core UI Elements

Feature Requests Studio Features
1

I understand this is likely an unrealistic request, but I wanted to put the idea forward to see if it could be entertained.

Allowing developers to create custom system menus could improve immersion, visual consistency, and usability across experiences. Many Roblox games already rely on custom settings menus to support nonstandard controls/mechanics. If developers were able to design a menu that integrates Roblox’s core menu settings, those custom options could live in a single interface instead of being split between Roblox’s menu and a separate in game UI.

This could reduce player confusion, streamline controls, and free up keybinds that are currently reserved for opening custom menus.

There are obvious reasons for why Roblox enforces standardized core UI. Not every developer wants to create a full settings menu, and there are concerns about abuse (such as experiences making it difficult for players to leave or access important system features). Because of this, as mentioned earlier, any implementation would need safeguards such as:

  • Required, non removable core actions (Leave, Report, etc.)
  • A verified or opt-in system for developers
  • Automatic fallback to the default Roblox menu if requirements are not met

While this idea would be very difficult to go about, it could enable more cohesive and player friendly experiences for games with many customized mechanics or stylized interfaces.

4 Likes
2

The problem here is what qualifies as a trusted developer? Who would decide that, would Roblox themselves manually choose creators? If you’re making this in the hopes that you can use it what about you do you think would make you qualify for that?

Would you gain access to this for just having a big game? Would quality matter? Can you get it for being notable on the forum? What about creating a resource on the level of moon animator which is essentially a must-have for studio animators?

Just to clarify, I hope this does get implemented, but even if it does, a holy ton of people will call it unfair. And they really wouldn’t be wrong either. There are other topics also talking about what you have requested (@AlexanderLindholt, @Visuile) but I doubt it’ll happen anytime soon.

I’d consider someone like @Reditect trusted, almost every developer that has used the forum twice in their life knows who he is, but would Roblox staff even know who he is?

Here are some other topics that may interest you:

https://devforum.roblox.com/t/remove-the-default-top-bar-%E2%80%94-start-powering-creativity/3819072?u=timefrenzied

(No clue why he edited the content out, but you can still view the discussion surrounding it.)

I personally believe that PC players should be able to hide the menu for themselves entirely (with an option in settings to revert it for unfortunate cases like a broken ESC button) since it’s completely irrelevant.

7 Likes
3

What I don’t get is why there even is a restriction for editing CoreGuis in the first place. For some specific ones, restricting access makes sense, in example, the main menu to experiences that allows players to leave the game, or reset their character; however, for other CoreGuis that only rely on public APIs, why restrict them?

For us developers that, let’s say would like to change about the way the PlayerList CoreGui works, there is nothing stopping us from doing so, except unnecessary bridges that have to be crossed:

  1. The developer would have to completely grab the visual elements from CoreGui during an experience play test.
  2. Reverse-engineering the elements to mimic Roblox’s system would be required.
  3. Continuous improvement measures would have to be taken to manually keep the system in sync with updates made from Roblox’s end.

Most CoreGuis are also open-sourced, so in reality, there is little to no reason at all to barrier developers off from changing around how most CoreGuis function.

4

It would unfortunately most likely just have to be some sort of opt-in feature because while this feature would be incredibly useful, putting player settings in the hands of developers is just too dangerous of a permission on Roblox. (Code in game could start changing a players settings without their input.)

Maybe they could isolate settings for games that use a custom menu ui? (Which, honestly would make a lot of sense thinking about it, players would probably want to save specific settings for certain games and have them persist)

Another thing, looking through the menu there are a lot of settings that could become redundant
If you were to make a custom camera system or movement system, the Camera Mode and Movement Mode settings become useless and just clutter the menu.

2 Likes
5

Alternatively, instead of allowing developers to directly modify the Core UI, they could just expose an API that lets us attach custom StyleSheets to the CoreGUI. It would be the safest option that also keeps in line with their wishes to make sure every feature is accessible to all developers without any form of “trust” system (they’ve mentioned before in response to someone asking at RDC if shader support might ever be available to “trusted developers” that they don’t like the idea of gatekeeping features like that)

5 Likes
6

The suggestion to allow trusted developers to modify Roblox’s core UI elements touches on one of the most important aspects of platform design: balancing developer flexibility with user safety and consistency. Roblox’s current approach is to maintain strict control over core UI components such as the system menu, settings, and reporting tools. This ensures that every player, regardless of the experience they join, has access to familiar, reliable, and non‑removable functions like “Leave,” “Report,” and “Settings.” These elements are critical for trust, safety, and accessibility.

At the same time, developers have long expressed interest in greater control over the player interface. Many experiences already implement custom menus, settings panels, and stylized UI systems to enhance immersion. The challenge is that these custom systems exist alongside the default Roblox menu, which can create redundancy, confusion, or stylistic inconsistency. Allowing developers to integrate or modify core UI elements could streamline the player experience, reduce friction, and enable more cohesive design.

Key points to consider:

  • Immersion and consistency: Customizing core UI elements would allow developers to create experiences where the interface matches the game’s style. This reduces visual dissonance and enhances immersion.
  • Usability improvements: Integrating custom settings with Roblox’s core menu could simplify controls, reduce duplication, and make it easier for players to find what they need.
  • Safeguards against misuse: Any system that allows modification of core UI must enforce strict protections. Non‑removable actions such as “Leave” and “Report” must remain accessible at all times.
  • Verification and trust: Limiting this capability to verified or trusted developers would reduce the risk of abuse. An opt‑in system could ensure that only developers who meet certain standards are granted access.
  • Fallback mechanisms: Automatic fallback to the default Roblox menu if requirements are not met would guarantee that players always have access to essential functions.
  • Industry comparisons: Other platforms often allow developers to customize UI within strict boundaries. For example, console games can implement custom menus but must preserve system‑level actions like quitting or reporting. Roblox could adopt a similar model.
  • Implementation feasibility: Technically, Roblox could expose a controlled API for modifying certain aspects of the core UI. Developers could adjust styling, integrate custom panels, or extend functionality, while Roblox retains control over mandatory actions.

The benefits of implementing such a system are clear:

  • Enhanced player experience: Games would feel more polished and cohesive, with interfaces tailored to their mechanics and aesthetics.
  • Reduced confusion: Players would no longer need to navigate both a custom menu and the default Roblox menu, streamlining usability.
  • Developer empowerment: Trusted developers would gain new tools to differentiate their experiences and deliver higher‑quality content.
  • Community trust: By enforcing safeguards, Roblox could balance developer freedom with player safety, ensuring that essential functions remain intact.

It is important to acknowledge the complexity of this proposal. Allowing modification of core UI elements introduces risks, particularly if safeguards are not properly enforced. However, by limiting access to trusted developers, requiring opt‑in verification, and maintaining non‑removable core actions, Roblox could mitigate these risks while delivering meaningful improvements to the player experience.

In summary, enabling trusted developers to modify core UI elements would enhance immersion, streamline usability, and empower creators, provided that strict safeguards are in place. This adjustment would align Roblox with industry practices, demonstrate responsiveness to developer feedback, and reinforce the platform’s commitment to balancing creativity with safety. While challenging to implement, the potential benefits make it a valuable consideration for future development.

1 Like
7

You should really write your own posts instead of using a painfully obvious AI to pump out posts.

7 Likes
8

i hate when people do this
admins should ban him and then blow up their house

1 Like
9

yknow if we wanted an answer from ai we would’ve asked it ourselves
no one asked you

6 Likes
10

No feudalism please.
Just add option to disable (or fully remove) most of coregui all together
Im tired of having react slop consuming more fps than my entire game!

1 Like
11

Absolutely based of them.
No bias, no feudalism or “elites” developers should have the same possibilities.
Core UI changes could be made with some publish time checks validating if crucial buttons are obscured, and if so, then defaulting to regular UI.

I just hope it fully removes the old core GUI from memory so I can make my ultra optimized UI 3000.

1 Like