FilteringEnabled Property is Being Deprecated

What I mean to say is that, before you could turn FilteringEnabled off for the sole purpose of messing with old scripts/gear. Now you can’t even do that. So old gear is perma-broken.

huh? i still have no idea what your talking about.

Even if you could do this why would you if you A) already knew the behavior and B) had no use for it in a real game. In my opinion gear is also outdated.

1 Like

Pretty cool update, will probably clear up a lot of confusion among new developers.

Also, before you reply about how this will ruin your game, they’re not removing FE, they’re removing the toggle for FE because once they forced FE the toggle did nothing and caused a bunch of confusion. If your game didn’t break in 2018 when they removed Experimental Mode you’re fine.

2 Likes

im confused because i have absoloutly no clue what it was in the first place.

1 Like

Your join date says you joined in late 2018. Filtering Enabled had already been mandatory then, so you don’t need to worry about this.

That’s exactly why they removed this, because people were getting confused.

1 Like

Finallllyyyyy. Continuing to support FE toggle is just asking for new scripters to get more confused at this point.

4 Likes

im not a scripter. im asking what it actauly does or is for.

1 Like

I don’t see the part where I complained I just asked a question

2 Likes

It was for client → server replication for objects and properties. Before FE, anything done on the client would replicate to the server (i.e if someone deleted the map, it would be deleted for everyone). It was a property to have your game follow this behaviour. Since FE is now forced enabled on every game by default, the property has no actual use anymore.

1 Like

Exactly! I’ve always felt that there is little to no difference between FE on or off, and I don’t think almost any major games don’t use FE. It just helps improve game protection and all that. Who keeps it off?!

Edit: It’s 12 am, I can’t phrase things correctly. It’s basically a free anti-cheat, who doesn’t use it?

1 Like

Uh… you realise FE is not optional, right? All games are forced to use it, regardless of what this property has been set to for a long time now, so of course you wouldn’t notice any differences between “enabling” and “disabling” it.
Prior to FE being a thing, exploiters could cause anything to replicate which meant they had a lot of control (bring players, destroy buildings, etc…) The addition of FE basically means that client has no control over most things, and when it does, it’s usually limited.

3 Likes

so basicly it sets stuff to either be client side or server side?

1 Like

To an extent, yes. If you, for example, created an object using a local script then only the client that has that local script will see it and the others won’t. Some objects and properties replicate to the server regardless of FE however. For example, you character model replicates, which is why things like speed exploits exist. If something is created/edited by the server then all clients will see it. (as long as it’s not located in ServerStorage or ServerScriptService)

With FE disabled (no longer an option), clients can create objects and edit properties from their local machine and all the players will see the changes. This behaviour basically allowed exploiters to completely ruin a player’s experience in a game their playing because they could edit the skybox, blast bypassed music, etc.

FE gives developers more control over their game’s security.

You can read this for more information: Client-Server Model | Roblox Creator Documentation

Ight, hear me out. Backwards compatibility?

There are many old games on Roblox that broke when FE was forced on for all games.

3 Likes

It’s not for backwards compatibility, original poster said this feature is cannot be disabled:

So there is no point to keeping this checkbox visible.

1 Like

To reiterate, the property has done nothing for years. You have not been able to disable FE for years, it has been enabled this whole time even if this property was false. Anything broken has been broken for years. This specific property change breaks effectively nothing. This is not the place to complain about FE being on permanently, that ship has sailed. Please read OP more carefully.

CC @omgcchheeessee @noot20000 @GamebringerDev @DataBrain @metatablecatmaid

11 Likes

Just out of curiosity, does this mean FE will become read-only?

1 Like

What with the games that require FilteringEnabled to be disabled?

1 Like

FilteringEnabled has been forced enabled since late 2018. No game on Roblox has FE disabled.

2 Likes