Flag reference
This page renders the same table that ships inside the manager. Every row is a flag the project knows about, rated for how much you should trust it on current clients.
01The five ratings
| badge | meaning |
|---|---|
| supported | Maintained by the project and validated against recent clients. |
| tweaks | Harmless feel/cosmetic/performance adjustments. |
| community | Shared by players, not yet vetted by the project. |
| placebo | Known to do nothing observable. Harmless, but expect nothing. |
| rejected | Known harmful, breaking, or pointless upsell plumbing. Off by default for a reason. |
The manager never applies rejected flags unless you force it, and it shows a red strip when you do.
02The table
Type a name or search by group. Click a row's checkbox to mark it for the current instance.
| flag | rating | kind | type | note |
|---|
03Applying
Flags are written as files into the client's FastFlags folder. Lurelock writes one .txt per flag in the FInt/FFlag/DFInt/DFFlag naming convention. Every written file is listed in the instance manifest, so removal is a manifest replay in reverse — exact, and fast.
04The stash
Flags you want to keep but not apply right now go to the stash. The stash is per-profile, not per-instance, and survives across client versions. Typical use: park a flag you're testing for a friend before committing it to an instance.
05Limits
- Flag membership tracks client releases, not your wishes. A supported rating can go stale; re-check after a client update.
- Roblox renames and retires flags without notice. The table lists what's commonly in the wild, not the contents of a min-file.
- Two flags doing the same job (looking at you,
DFIntTaskSchedulerTargetFpsvsFIntDesktopFPSCap) can fight. The manager warns when you enable conflicting rows in one instance.