There’s a very obvious reason why adservice flag had to be blacklisted. 2020 menu also caused an advantage in multiple games (ex. Jailbreak, it was game breaking and allowed you to completely avoid arrest)
It had to be a whitelist and it had to be small. So many flags caused an advantage in games with literally no way to fight against it.
The humble %localappdata%/roblox/GlobalBasicSettings_13.xml in question:
3 Likes
I never said it wasn’t fair, just that it’s bad. I’m hoping AGH catches the at requests anyways.
pls crack open the zip system
Thank you for this. I’ve had numerous reports of people using Fast Flags as cheats in my game, and it is very nice to know that exploitable flags will no longer be additional headache for me as a developer.
Would it still be possible to just have flags that would toggle the new LightingQuality and Style settings instead of the old deprecated things like technology?
I was thinking of making a feature request but I’ll just ask here since others are doing that too
FFlagAddUILessMode is a necessary FFlag that should be kept, in my opinion.
The ability to get rid of the Chrome UI is a plus in my book.
Additionally, although I don’t think you will consider this, will there be any changes/updates to the FFlagEnableV3Menu or FFlagEnableMenuModernizationABTest flags? I want to keep the new and better escape menu, rather than the old and boring one. It still works and supports most of the features that Roblox has added.
6 Likes
The old APIs still have the same behavior you could just use them to get the list.
someone has to resoond to this if you agree
https://clientsettingscdn.roblox.com/v1/settings/application?applicationName=PCDesktopClient
https://clientsettingscdn.roblox.com/v2/settings/application/PCDesktopClient
https://clientsettingscdn.roblox.com/v2/settings/secured-settings/PCDesktopClient
The allowlist is set per channel. Having said that, we aim to keep the allowlist the same across all public channels.
2 Likes
Correct me if I’m wrong but i don’t think secured-settings is or can be used to get the settings for a client application.
This didn’t even work before the whitelist. Although, if it did, yeah it should really be kept.
Many of us are unable to make feature requests, so a majority of users simply cant request feature flags they make heavy use of to be kept.
These two flags are used to mitigate a bug that causes textures to only be loaded at a compressed resolution, even on devices that could probably run a good portion of Roblox’s infrastructure.
I also agree, furthermore I thik the fastflag whitelist should instead be a blacklist for known bad flags. It is the job of your developers to ensure that fastflags that could be abused are either not pushed to global release or simply have bounds so that abnormal vlaues cannot be exploited.
It is way too much work for us as users to convince you and for your developers to implement every workaround for every fastflag we would benefit from being able to use. It would be so much easier for everyone if instead it was a blacklist approach.
Please also permit the FFlagDebugGraphicsDisableDirect3D11 flag, as it allows us to force the engine to use other renderers as it is not very stable at sticking to our preferred renderer otherwise.
Please also permit FFlagRenderVulkanFixMinimizeWindow as I believe this fixes a bug with Vulkan where the client’s rendering just breaks when unfocussed for a long period of time or when focus is switched frequently.
2 Likes
Actually, they started accepting people into feature requests recently, so a lot of people have access to it now.
1 Like
can you allow
these fflags
FFlagAddUILessMode
FFlagEnableInGameMenuChromeABTest4
FFlagEnableInGameMenuSongbirdABTest
FFlagEnableInGameMenuChrome
i cant send them to engine features because it says i dont have permission to do it
2 Likes
Honestly don’t have too much of an issue with this. Seems like a good solution to abuse and I personally don’t think this is too bad.
1 Like
and just how would I request access?
You should be able to request access to it here
Flags that have Debug or Test in the name are very unlikely to make it into the allowlist. The ones that are already there will go away as soon as we have an alternative.