I am not completely sure if the ability to adjust client FFlags is going to be completely removed or if Roblox will just set some FFlags that can be adjusted while preventing the adjustment of others because two engineers @Bitdancer and @Dogekidd2012 are saying two different things.
Here DogeKidd2012 said that it’s simply not sustainable for them and would require that they play a cat and mouse game to only set specific FFlags that can be adjustable and preventing the adjustment of others and would require them to constantly make sure that specific FFlags can’t be abused.
But it seems to me that Roblox is just planning to disable the ability for people to change their client FFlags and not whitelist and blacklist specific FFlags that can or cannot be adjusted. While the former is definitely better and easier for Roblox and for developers, it would be very bad for people who adjust their FFlags for good intentions for example to improve performance like me.
So I would really like for them to add alternative ways to adjust these features like adding advanced graphics quality controls instead of having to use “DFIntDebugFRMQualityLevelOverride” and also add better screenshoting features so we wouldn’t have the need to use FFlags to take screenshots without Roblox CoreGUI, player names and developer UI.
I would be happy if they do that and wouldn’t complain at all if they disable the ability for people to adjust client FFlags but offer alternative ways to adjust useful and good faith FFlags.
i hope a “Feature Flags” menu will be available that allows you change more settings directly within the Universal App’s Settings page.
Most web browsers already have this, so it would be beneficial to us (users) & hopefully be available on mobile like Safari on iOS or Chrome on Android.
it would house whitelisted flags, and i prefer @Bitdancer’s approach in this thread
I’m using FastFlags to correct a Roblox bug. Because of some Roblox bug I can’t set own graphics settings and it’s stuck on automatic which sucks, so I use an FFlag to force Roblox to use level 21 at all times.
(a favor to keep these mentioned flags, please don’t make me go mad because of one certain thing)
I’ve seen it way too much…
Well might be correct to keep some fast flags, but here’s what i use:
My presets (These 2 flags makes the character move weird, and i like it perfectly and it’s very funny too):
“DFIntReplicatorAnimationTrackLimitPerAnimator”
“DFIntMaxActiveAnimationTracks”
Bloxstrap Presets (can be seen by clicking show preset flags):
“FLogNetwork”
“DFIntTaskSchedulerTargetFps”
“FFlagEnableInGameMenuChromeABTest3”
“FFlagEnableV3MenuABTest3”
“FFlagEnableMenuControlsABTest”
“FFlagEnableInGameMenuModernization”
“FFlagEnableInGameMenuControls”
“DFIntCanHideGuiGroupId”
“FFlagFixGraphicsQuality”
“FFlagHandleAltEnterFullscreenManually”
“DFFlagTextureQualityOverrideEnabled”
“DFIntTextureQualityOverride”
“FFlagEnableInGameMenuChrome”
“FIntFullscreenTitleBarTriggerDelayMillis”
“FFlagDisableNewIGMinDUA”
“FFlagDebugGraphicsPreferD3D11FL10”
“FIntDebugForceMSAASamples”
“FFlagDisablePostFx”
“FIntTerrainArraySliceSize”
“FIntRenderShadowIntensity”
So these are my favorite fast flags that could be kept on forever (because i won’t handle it on 1 frame per second)
We’re saying the same thing in different ways. The plan is an allowlist, ideally with flags we can expose as actual settings in the future, which doesn’t require the cat and mouse game. What people were suggesting is denylisting abusive flags, which isn’t sustainable.
I’m trying to say that it’s best to share this with one of the admins to try and get it fixed instead of posting it here where people who like to abuse fflags can see it.
Hey this is unrelated but, would every single fast flag that exists be restricted from use in the official client? Or would it be that only certain fast flags are restricted?
I have plenty reason why I think not everything should be restricted.
Graphics API changes
Test out some experimental features in production
Force Lighting technology (although this is just preference, it’s a neat thing to have.)
Wouldn’t it be better if only networking/physics related flags would be restricted?
I mainly use "FFlagEnableInGameMenuChrome": "True" because all of my friends except me have this available without the flag change and I prefer this version of the menu due to the voice chat bubble not being on screen all the time and the large popout for it taking too much space for smaller windows. I hope this becomes defaulted on (at least for me alongside my friends) soon.
Then I’m trying to say that it’s issue on Roblox’s end that they cannot prevent it, their anti cheat can be easily avoided. Those flags were already shared to public anyway.
sorry if this is not the correct comment to reply to, but are fflags like FFlagDebugDisableTelemetry[…] going to be allowed or not? or stuff like FFlagAdServiceEnabled too?
Roblox has quite a few bizarre settings enabled by default that make games unplayable that were intentionally made like that. For example, Roblox has a texture downscale system designed to make like the iPad 4 not crash when it was still supported. That system, for unknown reasons, got enabled on computer and now theres a 50/50 when you join a game on some systems without setting fastflags all textures get downscaled to 16x16
No need for it due to the built-in fps unlocker, which still sucks because it’s capped to 240 and bottomed at 60 instead of 30, you also can’t change the cap yourself so the fps fflag is for if you need those specific values
