Just like the title says allow the devloper to switch between coregui versions: legacy and new just like with TextChatService.ChatVersion legacychatservice and textchatservice
Why? Most of the buttons like SelfView are impossible to disable with SetCore and new coregui is very intrusive and annoying for developers
reference to: https://devforum.roblox.com/t/new-coregui-is-getting-out-of-hand/2851171
Preferably: Allow us to disable it for PC users or hide it until the mouse enters the topbar proximity.
Honestly, roblox should just stop remaking the gui every week. Rather, make one design and stick to it. I, personally, have many designs in mind but no one would probably acknowledge them so… no thanks.
This could lead to inconsistences, as users might not be able to find out where the CoreGUI is on a per-game basis. One of the main reasons there’s a consistent CoreGUI is to act as a landmark; users may be confused when some games have different menus which can make the interface harder to navigate.
Also, if the old CoreGUI is maintained, this version of the camera/vc controls would have to be kept (which would probably receive not very good reception of the community).
If Roblox provides this option, creators would probably expect Roblox to maintain constant and reliable support for both of the CoreGUI versions, which would require more resources, especially to make the menu work with new features they might release in the future.
If you provide more use cases/problems, that would probably help in discussion with staff about another way to approach this problem!
As much as I also do not like the intrusiveness of the new UI, there is no substantial case here about why Roblox should continue to support older versions of the CoreGui in the future for developers to change to nor how this would benefit your development or player experience. You’d have a better shot at asking for an option to disable the self view (either set by the client or the developer) than to ask for Roblox to continue supporting older content.
I don’t expect Roblox to continue supporting the Legacy Chat System option long term; support for the code has already been dropped and now they only go as far as to inject the code into your experience, meaning you’re responsible for any maintenance you want done on it. In the future they may remove injection of the old scripts into experience and retitle the option to “Scriptable” for developers who want to or already do use their own chat systems.