RIP the grass length/speed ones if they don’t make the cut, terrain grass is really laggy and developers shouldn’t be able to force it on us.
Thank you guys for listening to the community for feedback!
Is there an estimated timeline yet for this removal and allowlist? If not, I completely understand.
Sorry, we can’t share release dates before official announcements are made.
No worries, thanks for the fast reply!
I hope these fastflags are included in the list
“FFlagEnableInGameMenuChromeABTest2”: “False”,
“FFlagEnableReportAbuseMenuRoactABTest2”: “False”
Both flags are in the allow list.
Keep in mind, the allow list will be dynamically adjusted, some flags might be added in the future while other flags will be taken out.
Can i ask if this FFlag is included in the list:
"DFIntCanHideGuiGroupId": "1"
It is commonly used to hide the UI to make videos etc
Please look into these if you haven’t already:
FIntFRMMaxGrassDistance
FIntFRMMinGrassDistance
FIntGrassMovementReducedMotionFactor
FIntRenderGrassDetailStrands
Whatever will I do without DFStringHttpCurlProxyHostAndPort
(absolutely makes sense if this one ISN’T in the allow list though)
maybe removing ability for FFlags isn’t a good idea, instead block the usage of “cheats” and let all other fastflags work. i have some friends which can’t afford a good computer, they used fast flags to improve the peformance as much as possible (graphics level 1 doesn’t always give the best peformance)
Hey, is this flag "FFlagHandleAltEnterFullscreenManually"
in the allow list?
I hope we will get list of allowed FFlags in Documentation - Roblox Creator Hub after FFlags update or at least "FStringDebugShowFlagState"
will be whitelisted.
Also would be great if those FFlags will be in whitelist. I’m using it as shortcut to the specific settings page instead of doing more clicks to specific settings page or alt tab:
"FStringPlatformEventUrl"
"FFlagPlatformEventEnabled2"
Will the FFlag "FFlagMovePrerender"
be whitelisted? When it’s set to true it causes all sorts of problems with Robot 64 and most likely a few other games. Since it’s set to default on mobile clients players using Sober on Linux will experience all of those problems unless they are able to set it to false.
Maybe theres a bit of confusing, but i haven’t seen any info of FFlags being “removed” but rather being in a allowlist. They will keep FFlags and remove the abusive ones. My guess is that certain news accounts and creators accidentally send misinformation or the info has changed
Check this post:
Sorry for the ping
I believe it is because Bloxy News reported it and they reported it from Matt, the head developer of Bloxstrap.
For reference:-
Currently, there are 32 allowed flags, including FFlagMovePrerender
. We are still working on refining this list and will make it public once FFlag allow lists are tested on public test channels.
Having said that, our aim is to reduce the number of allowed FFlags and replace those most in demand with officially supported, more easily accessible features.
Hopefully we will get advanced graphics quality controls
All of this could have been avoided if people had actually read the thread they were pointing to. We attempted to encourage folks to at least read what Roblox staff had to say on that topic, but alas, it was already too late.
To clear up some of the unfortunate wording in the attached images:
- So far, there has been no official announcement.
- This thread has been around for quite some time to test the waters, so nothing should come as a surprise.
- FFlags are not going to be removed; the current plan is to restrict which FFlags can be locally overridden. The list of allowed FFlags can and will dynamically change to adapt to the needs of the community.
- Anything discussed in this thread is subject to change or even cancellation until there is an official announcement.
Yes, instead of remove fflags, the current plan is to restrict which fflags can be locally overriden. that, why there no official announcement, for that is there any suggestion or anything