Just something I wanted to suggest for legacy support this change was made in 2015. Previously games were allowed to set the FE state on/off from a server script, it was like this from when it was introduced until mid 2016. I’ve recently come across a few games that used this and are now broken as a result because it’ll now throw and error an refuse to play nicely. I remember at that current time the dev that I spoke to only used it at the start of the script as a double measure (in-case he forgot to turn FE on) the game would be safe still. It’s frustrating that a few years later a change was made that broke the game and the developer fell off the face of the earth. At one point, FE was not available in game.Workspace meaning setting it via script was mandatory, if it can’t be replaced with a warning it would be neat if FilteringEnabled could be set to true via script but notfalse
Can we make it so it’s not an error and a warning and default the place to FE off for safety reasons? This will allow games to preserve their legacy state of the developers that are in-active/abandoned the games.
So because FE is being set from a ServerScript it may be possible for a client to inject code before it’s set. As a safety measure, if a game tries to set FE from a script don’t error (allowing the game to keep running) but warn and keep the place FE disabled
In my opinion, FE should be enabled by default, not the other way around. Developers should try to develop their games with FE in mind from the start, and only disable FE if they are making a game that needs it to be disabled. I don’t support the idea that this option should be enabled/disabled through scripts, as it is now a “game setting” called “Experimental Mode” and I think the FE property of “Workspace” should be removed to avoid confusion.
You misunderstood just like me. He’s suggesting that attempting to set FilteringEnabled just warn and keep whatever FE it previously had (in this case, off). Removing the property in general will break many old games that, for whatever reason, check, maybe for a fruitless anti cheat script. Deprecating it makes more sense.
To clarify, in 2015 the game.Workspace.FilteringEnabled property had to be written to using a script (e.g.game.Workspace.FilteringEnabled = true) but this changed later on to have a property in the game.Workspace that you could turn on via the explorer window.
This in turn broke games that set that value because as shown above, it errors preventing the script from continuing on. This change is purely to support legacy games that still use the legacy method of writing the FE status from a server script. Instead of erroring, I am proposing that it gets changed to a warning allowing the game to continue - but as a safeguard, keep FE off. Not to mess with the defaults
We are not going to change this behavior unfortunately. Please contact those developers and ask them to update their games to not attempt to set FilteringEnabled.
