[BUG]: Automatic rewrite of DFIntCSGLevelOfDetailSwitchingDistanceL23 to L24 breaks Roblox Whitelist compatibility

[dangerabbieabbie-hash]

Describe the bug

There is a forced automatic correction bug in the FastFlag Editor. When a user manually inputs DFIntCSGLevelOfDetailSwitchingDistanceL23, Voidstrap automatically rewrites it to L24 upon saving or closing the application.

According to the official Roblox DevForum Whitelist, L23 is the active and verified flag for geometry level of detail switching distance. By forcing the change to L24, Voidstrap breaks compatibility with the official whitelist. This causes the Roblox client to completely ignore the line and marks it with a gray "X" in the presets and the Tag Unknown preset inside the interface.

Expected behavior

Voidstrap should leave DFIntCSGLevelOfDetailSwitchingDistanceL23 untouched so the Roblox engine can read it correctly, instead of auto-correcting it to an invalid modern naming equivalent (L24).

Feature Request / Native Presets Suggestion

For players running Roblox on low-end hardware (such as Intel Celeron N4020 processors with limited RAM), having to manually input advanced optimization flags is tedious. It would be an amazing quality-of-life update if Voidstrap could include the following extreme optimization FastFlags as native, selectable presets (with blue checkmarks):

1. Particle Control:

   • FFlagDebugDisableParticleEmitters (Set to True to completely disable heavy particles like smoke/fuego/explosions).
   • FIntParticlePoolSize (Set to 0 to minimize particle memory allocation).

2. Advanced Rendering & Shadows:

   • DFFlagDebugPauseVoxelizer (Set to True to pause heavy volumetric lighting calculations on integrated GPUs).
   • FIntRenderShadowIntensity (Set to 0 to fully eliminate dynamic shadow depth).
   • FIntRenderShadowmapBias (Set to -1 to prevent shadow calculation overhead).
   • FFlagNewLightAttenuation (Set to False to force legacy, lightweight light rendering).

3. Textures & Interface Optimization:

   • DFFlagTextureQualityOverrideEnabled (Set to True).
   • DFIntTextureQualityOverride (Set to 0 to force 1x1 low-res textures without breaking global illumination).
   • FIntTextureCompositorLowResFactor (Set to 1 to significantly lower avatar texture composition weight).

Safety and Compliance Note (No Risk of Warnings)

Please note that all the suggested FastFlags above are completely safe to implement as native features. They are strictly part of the official, public Roblox DevForum Whitelist. Roblox explicitly allows players to modify these specific variables for accessibility and performance reasons, meaning there is absolutely ZERO risk of Roblox issuing automated system warnings, bans, or taking actions against the Voidstrap repository for integrating them.

Thank you so much for your continuous effort in maintaining this optimization tool.

[dangerabbieabbie-hash]

I would like to propose a few new Fast Flags that I’ve been looking into. These FFlags are completely safe and won't cause any issues or risks to the client. In fact, they are very effective and would specifically help boost performance on low-end computers. It would be awesome if these could be added to the project, as they would really help a lot of users out there. However, I am not pushing or obligating you to do it at all! It's just a suggestion—it would simply be really great to see them included. Thanks for your time and all your work on the launcher.