That’s on god, we love you bitdancer :3
4 Likes
Im a bit out of the Exploiting branche, but wasnt there an old employee of SynapseX, who actually made an Ejector that can go around ByFrost?
4 Likes
PLEASE for the love of god, allow us to play games BEYOND 60 FPS if you’re going to disable fast flags. Please. I beg of you.
16 Likes
It was cool to force meshes to be at the lower quality, to force Future lighting, and to force Vulkan rendering while it lasted 
Oh well, looking forward to seeing what happens regarding the “good faith” ones!
11 Likes
I think that’s what they meant by “[first making] existing good faith flag flips unnecessary”, since framerate limit unlocking is probably the biggest reason people initially look to configure Fast flags., and they are actively working on making it an official feature.
9 Likes
In one of the updates there is a note for allowing FPS caps to be raised to 90,120 and 144
4 Likes
Ay i love herfdiug. Missin the times fastflags werent that popular.
2 Likes
Video creator here,
These have existed for a while now and I’m glad that it is finally getting patched, it was gatekept but inevitably bad actors got hold of it which was unfortunate.
6 Likes
Please make sure that whatever replaces the current fastflag system allows us to enable developer-oriented things such as betas in our client. My use-case for changing client flags is to test betas like EditableImages and aerodynamics outside of Studio before they officially launch.
5 Likes
What is your use case for this? This is currently not in our plans and it smells like Studio could be improved here.
3 Likes
I have quite a niche use case outside of what @Mauio64 described - I sometimes toggle on flags to help engineers determine whether a flag they’re wanting to enable will cause issues with certain aspects of my game. For example, a few weeks ago a flag was pushed regarding UI that caused a property used in my game to completely break and I was able to work with an engineer who was responsible for it to help test and identify the flag involved and see if the issues were corrected after they pushed a fix.
Yes, repro files can be used as an alternative but not for device-specific issues… going to miss helping out engineers with flags 
4 Likes
No please don’t it will disable the ability for me to revert to old CoreGui version and many many other things such as FPS unlocking with bloxstrap
Maybe solve this issue by making some abusive game breaking FFlags read-only? (aka you can’t edit them and they have only one value)
4 Likes
This behavior will not be preserved in the client, though you will still be able to change flags in Studio using whatever method you would be using today.
This simply isn’t sustainable and requires that we play cat and mouse and constantly make sure that specific FFlags can’t be abused. Also, even if this was added, it certainly wouldn’t include reverting to old CoreGui, as the end state of most flags is for the code it’s replacing to be completely removed for maintainability reasons–we would just be encouraging delaying the inevitable.
9 Likes
Well, I literally just stated my use-case. I use them to test features that make use of betas ingame before they launch, most often with several of our playtesters whom I can’t afford to give Studio access. I have these features built and tested before the betas go public so that when they do go public I can be relatively sure we’re good to go, and can just enable it.
I don’t know how Studio could be improved here, short of letting us enable fflags for our entire game inside of it, or some system that lets us host game servers from our PC and lets people join, respecting whatever fflags we set.
4 Likes
I see. This use case will definitely break, and were it to come back it would not be in this form (I expect us to never allow local flag editing on client after this). But it sounds a bit like better Studio permissions, like being able to Team Test with someone without giving them access, could help alleviate this somewhat…that or beta features being able to be tested in game which is a problem we face a lot regardless. No promises, just musing about what could potentially help.
6 Likes
This is the best case scenario in my opinion. Letting developers just use beta features in-game more often (even if they’re not necessarily stable yet) would go a long way, both for Roblox and developers.
I’ll gladly take Team Test being open for non-devs being supported though, and it’d be really useful outside of the context of testing Roblox betas… thinking it could generate a join-link much like how private servers work. That way, all we’d have to do is send one link to get people ingame and going, no need to configure permissions or anything.
8 Likes
If there was one FFlag that liked to use, it was the one that let’s the player hide all GUI, including BillboardGui and chat bubbles. It was arbitrary locked to being in a specific group (which was changeable using Bloxstrap, but I think this needs to be a feature anyone can use, mainly for screenshots and videos.
Some games use BillboardGui instances to guide the player towards quests and important locations, but these break immersion, especially if they’re drawn on top of everything like the Sonic Prime logo and characters’ head renders are in Sonic Speed Simulator:
With that FFlag configured and working, I could hide all BillboardGui instances by pressing CTRL+SHIFT+B.
This flag was also useful for getting completely clean screenshots, as it can hide all game and core GUI elements with other keyboard shortcuts.
People are emphasizing how important frame rates over 60 are, but this is so useful that I think it should become a proper feature before locking down FFlag modifications.
EDIT: Also, without this flag, the only people that can hide all GUI are exploiters, since they have control over CoreGui. It would be awesome if every player could hide any GUI when they wanted to take pictures. I know CaptureService exists and it can hide CoreGui for screenshots, but that will only work if a developer uses its functions in their game, and I doubt most of them will… Roblox can look beautiful at times (just look at Royale High’s Castle’s Heart realm), and it would be nice to capture that without any obstructions… 
18 Likes
Currently this functionality is restricted to devs-only unless you turn on the flag. Maybe they could open it up to everyone(?) but this would probably be a separate feature request.
3 Likes
Just as an FYI, this workflow will definitely be broken in the recent changes. I’m unsure if this is something we will want to bring back as a general thing, it is actually quite surprising to me that GUIs I can make would sometimes be able to be hidden (obvious cases being things like intentional blind UIs, aesthetic blurring/vignette UIs, etc). I think the better solution here is making it easier for developers to allow their games to have these kinds of viewer modes, probably through something like a dev module.
10 Likes