Fast flags are being used as cheats

[crepper1323_new (CREPPER1323)]

Fast flags are being used as cheats

To confirm: Rōblox will decide which flags users will be able to modify in the future. However, there are dynamic flags – which Rōblox can change in the middle of a play session. I can imagine a similar system where the ability to change individual FFlags can be toggled by Rōblox intermittently. Is this something that you anticipate?

i think we will have fast flag editor in roblox without abusive fast flags

[pyxfluff (Pyx)]

@sicknoobie

. It’s a necessary step to make the platform better overall.

This is obviously not true and is the same type of logic people used for the audio update and the Youtube dislike update. Both (or all three possibly) are horrible changes which benefit nobody because of a minority misusing the system instead of developing proper solutions.

Blocking a useful debugging tool most people use with good intent because of the 1% is nothing short of lazy on Roblox’s end.

Fast flags are being used as cheats

Just because some flags can be used maliciously does not mean the system should be locked as you are suggesting. There are many flags Roblox would prevent from being changed which are useful or wouldn’t want shut off like many of the telemetry flags. Roblox should just be more careful with what they make flags instead of disabling the ability because a couple of people use it to walk fast which just gets patched anyways.

This is more of a 5am rant but I feel like y’all are too sensitive over “running the gaming experience”. People exploiting and cheating to ruin the game is obviously no fun because that ruins the entire game but people having oversized avatars and feee limited is funny rather than harmful and you guys should stop overreacting.

[heedicalking]

Crazy, I posted this a year ago and now the amount of cheaters has risen over 300% since…

Fast flags now seem like a minor issue now in comparison to the amount of script execution tools available, but removing some of the abusable ones would be good. Roblox should add more advanced graphics options so people didn’t have to rely on fast flags to tweak things. Roblox wants to be an engine for all games but not every game should use the same graphics scaling. Many games become unplayable when Roblox’s existing graphics settings get lowered due to how severely it cuts render distance.

[officialnabalt (yourlocalbuddy)]

the DFIntDebugFRMQualityLevelOverride is very useful for me
so my pc doesn’t have to ascend to heavens
please don’t remove it, thank you

[ItzAidfoplays390]

I wonder what led to this post suddenly getting very active again, I assume to has to do with Bloxynews recent Twitter post about Roblox soon removing the ability to adjust FFlags in an upcoming client release with no evident proof whatsoever? Not saying it’s not gonna happen, but no proof it is happening soon with an upcoming client release.

Back to the main topic. I think Roblox should either keep the ability to adjust a limited number of useful non-abusive FFlags or just add them as official settings with a UI interface to adjust them or even both.

Let me explain further, if they can’t add all of the useful non-abusive FFlags all at once right now, then they can gradually add them, and in the meantime allow these FFlags to be available to be adjustable.

It would also heavily benefit Mobile users to have advanced graphics quality controls. If the advanced graphics quality controls that Roblox is going to add is going to be more than just separating render distance from other parameters then it is going to be even more useful, effective and flexible.

Can we also please get the option to disable game purchase pop-ups in games and/or platform wide? There was an FFlag that would have the pop-up appear, but with it erroring preventing the purchase of gamepasses. Some cheaply made games, mostly tycoons, got buttons on the ground that activates the pop-up to purchase a gamepass, they’re put almost everywhere that you need to move on that it is hard to move without the pop-up showing every few seconds, which can result in accidentally purchasing a gamepass without user intention.

[GuilleLopezD]

As long as the FPS stays customizable im okay with it, i have a 165hz screen and i use Bloxstrap to get Roblox to run at that framerate since it isnt an option in the normal client.

[EmK530 (EmK)]

A cool solution for this would be vertical sync, but given how long it took for FPS editing in the client let’s give it a few more years lol

[Sky_ogg (Sky)]

you can change the framerate cap manually if you go to %localappdata%/roblox/globalbasicsettings_13.xml and find the FramerateCap line

[Extravi1 (Extravi)]

Now that fast flags will be limited moving forward, will users still be able to set a custom rendering API such as Vulkan, OpenGL, DirectX 11, and so on?

[ItzAidfoplays390]

@ItzAidfoplays390

I wonder what led to this post suddenly getting very active again, I assume to has to do with Bloxynews recent Twitter post about Roblox soon removing the ability to adjust FFlags in an upcoming client release with no evident proof whatsoever? Not saying it’s not gonna happen, but no proof it is happening soon with an upcoming client release.

Bloxstrap dev(s) also talked about it happening in their Discord server, albeit without providing any proof. So I guess it’s really happening soon. It would be cool for Roblox to give us details on how it will be done though. Let’s just hope for the best.

[d_reamweaver (Castorice)]

With the removal of changing fflags locally, will true full screen (Alt + Enter) be added back (not borderless windows (F11)? We currently have to add it manually through this fast flag:

"FFlagHandleAltEnterFullscreenManually"

Additional Information below:
Add support for Fullscreen - Feature Requests / Engine Features - Developer Forum | Roblox

[angeryka2]

I use fast flags to improve my gameplay experience by changing rendering features so my PC does not explode, i feel like Roblox should keep flags that cant be abused as this might be detrimental to thousands of users who use Fast Flags everyday for a better experience.

[BANDERA2606 (ryz)]

So uh, why not to block only some fast flags which are being used to “cheat” in games, instead of blocking ALL fast flags at all. For example, lot’s of them are used to improve roblox perfomance on low-end PC/laptop, and they do really help and work (I can personally confirm this as I use them myself.)

[wilsontulus5 (bunnwils)]

@BANDERA2606

lot’s of them are used to improve roblox perfomance on low-end PC/laptop

Other than custom framerates, downscaling texture quality, disabling anti-aliasing features, using another lighting engine, and using an older rendering engine, I don’t think these flags are really that useful in any kind of legitimate usage.

Lots of said “performance-improvement” flags could also introduce unfair advantages, and sometimes be used for cheating too, such as:

• Disabling blur / post-processing effects
• Reducing mesh/union quality by forcing LoD (level of detail) to the lowest level
• Disabling shadows

[Eagisa]

@Dogekidd2012 Hi, just wanted to point out that "FFlagHandleAltEnterFullscreenManually" used to be false by default until 2021, and then for some reason it was changed to true. It would be great if you could consider setting it back to false by default, since it allows true fullscreen (better input latency and FPS) without needing ClientAppSettings.json every update. Thanks!

[karlos_800 (karlos)]

Tbh, im not mad at roblox removing FFlags, they were meant to be used only by engineers an staff, not the general userbase.

[ItzAidfoplays390]

They first have to fix the bugs that appear with Exclusive Fullscreen (True Fullscreen) before enabling this FFlag and there are quite numerous bugs that occur with this fullscreen mode such as webview pages not appearing.

Also, I thought they added it back, what happened? Did they only add the FFlag back and didn’t enable it officially or meant to enable it officially and never did?

Add support for Fullscreen

Since all the discussion here I will add the feature back. Should be in a production release by next week (or at the latest the week after)

[ItzAidfoplays390]

That’s right, however it doesn’t change the fact that these FFlags provide functionality that could be very useful for the general userbase and aren’t available by default. If Roblox actually listened to its userbase and added functionality like advanced graphics quality controls and other useful functionality that FFlags offer nowadays and can’t be compensated then nobody is gonna ask to keep the ability to adjust client FFlags anymore.

[Dogekidd2012]

You shouldn’t have to meddle with internal flags in order to get good performance on low-end computers.

[TimeFrenzied (Chicken Jockey)]

@GABA8

fflag modification is removed instead of removing specific fflags

@karlos_800

im not mad at roblox removing FFlags

@BANDERA2606

instead of blocking ALL fast flags at all.

@angeryka2

i feel like Roblox should keep flags that cant be abused

@d_reamweaver

With the removal of changing fflags locally

They aren’t removing all fflags. Specific widely used fflags will be put on a whitelist and ideally implemented as client settings in the future.

FFlag DebugAllowHttpInNetworkedDMs does not affect game:HttpGetAsync() function in the Roblox Client, but only in the Roblox Studio

Hi Broken Spawn, This is correct; certain FFlags will be allowed. However, the list of allowed FFlags is not finalized yet and, even after finalization, will be subject to change. Debug flags are less likely to end up on the allow list. Also, for Studio, FFlags will be allowed as usual.

Fast flags are being used as cheats

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.

Dunno where people got the idea that all flags are being removed from (bloxstrap, matt worded his announcement very poorly, maybe on purpose) but this is not happening according to the aforementioned responses.

No clue why this post would suddenly become active other than that.

If you guys remember, something similar to this happened before on a massive scale to the point where even I got baited into thinking bloxstrap was getting people banned.

@Dogekidd2012

You shouldn’t have to meddle with internal flags in order to get good performance on low-end computers.

Well we do, so I don’t really know what to say about that. The most used performance flag seperates graphics quality and render distance, allowing you to see much farther without adding extra unnececary things since you can barely see anything on low graphics quality. Some games are genuinely unplayable since these are tied together.