Keruro
|
  |
| Joined: 23 Nov 2013 |
| Total Posts: 2327 |
|
|
| 21 Jun 2015 01:34 AM |
Becouse it will make all scripts disabled on your place. Found it by myself. And thats why developers dont put FilteringEnabled |
|
|
| Report Abuse |
|
|
NotAshley
|
  |
| Joined: 16 Jan 2014 |
| Total Posts: 14257 |
|
|
| 21 Jun 2015 01:38 AM |
If you're trolling, good one.
If not, you should seriously look up what FilteringEnabled does, since the reason your scripts are breaking is because it changes the way scripts behave. |
|
|
| Report Abuse |
|
|
Keruro
|
  |
| Joined: 23 Nov 2013 |
| Total Posts: 2327 |
|
|
| 21 Jun 2015 01:41 AM |
OOOOH! Thanks. But if i put no filteringenabled bans will be more reasonable on my game. |
|
|
| Report Abuse |
|
|
NotAshley
|
  |
| Joined: 16 Jan 2014 |
| Total Posts: 14257 |
|
|
| 21 Jun 2015 01:46 AM |
There's a lot more to it, but to understand FilteringEnabled, you need to visualize how ROBLOX works.
There's the server, which is the game itself, hosted by ROBLOX. It stores most of the data about the game as its running.
Then there's the clients. Your computer, and the computer of everybody connected, is a client. Your input does stuff (mostly to your player and character) and your client "replicates" (sends) data to the server so it can tell all the other clients where you are and what you're doing.
LocalScripts run on clients, and regular scripts run on the server. FilteringEnabled adds a new layer of security by, for the most part, breaking the connection between the two, and LocalScripts won't be able to do things that directly interact with the server's shenanigans. You need to use RemoteEvents and RemoteFunctions to make LocalScripts communicate with regular scripts to make things happen. |
|
|
| Report Abuse |
|
|
| |
|