|
| 07 Feb 2014 08:28 PM |
So, if you did not know:
Roblox recently added a new property to workspace called "FilteringEnabled" which prevents all client changes being replicated to the server.
This basically means that ALL exploits will not work when this is enabled, although it also means nothing can be changed via LocalScripts for other users (Still, you can change it. It will only be for you, though).
We need to allow more control over what LocalScripts can modify at a per-player basis!
So, I propose...
allowAccess(Instance Player, Instance Object, String Property)
Using this allows the Object.Property to be modified/called by the Player via LocalScripts.
IE (In a Script):
allowAccess(game.Players.Player1, workspace.Part1, 'Name') allowAccess(game.Players.Player2, workspace.Part2, 'Destroy')
(In a LocalScript in Player2)
workspace.Part1.Name = "Hello"
workspace.Part2:Destroy()
> Part1 is unchanged, however Part2 is destroyed.
(In a LocalScript in Player1)
workspace.Part1.Name = "Hello"
workspace.Hello.Size = Vector3.new(2, 2, 2)
> Part1 is renamed "Hello", but it is not resized as the client does not have access to that property. |
|
|
| Report Abuse |
|
|
| |
|
MettaurSp
|
  |
| Joined: 20 Mar 2010 |
| Total Posts: 3179 |
|
|
| 08 Feb 2014 10:05 AM |
| And a block function so we don't have to block everything allowing for a side of streaming control with the anti exploit :3 |
|
|
| Report Abuse |
|
|
|
| 08 Feb 2014 10:08 AM |
| So a disallowAccess function? |
|
|
| Report Abuse |
|
|
DataStore
|
  |
| Joined: 07 Feb 2012 |
| Total Posts: 8540 |
|
|
| 08 Feb 2014 10:24 AM |
Service:AllowAccess({game.Players.Player1, game.Players.Player2}, {Workspace.Part1, Workspace.Part2})
The first and second parameter should be a table, rather than singular objects. The third should be optional, so if it's blank it allows access to all properties.
Support. |
|
|
| Report Abuse |
|
|
tery215
|
  |
| Joined: 19 Aug 2009 |
| Total Posts: 3879 |
|
|
| 08 Feb 2014 10:28 AM |
support
testserver world isn't modifiable by testclient with Roblox Studio |
|
|
| Report Abuse |
|
|
|
| 08 Feb 2014 10:43 AM |
@DataStore: A table of strings containing the properties they are allowed to access?
We also should have something to allow all and no players access to certain properties, for mass changing.
Maybe also something to allow certain objectsto be instanced to certain other objects (Like bullets for guns) |
|
|
| Report Abuse |
|
|
| |
|
| |
|
| |
|
maxi1332
|
  |
| Joined: 23 Dec 2011 |
| Total Posts: 237 |
|
|
| 08 Feb 2014 05:03 PM |
Brain.exe has stopped working.
From what I understand, this is the ultimate Anti-Exploit. Then support.
"Let me guess, someone stole your sweet roll?' -Guard |
|
|
| Report Abuse |
|
|
|
| 08 Feb 2014 05:15 PM |
I have a better idea.
game.Players.Player1:allowAccess(method, "Remove")
Cheat engine turns on:
x = game.Players:GetChildren()
for i=1, #x do x:Kick() end
Script fails...
If they did this...
x = game.Players:GetChildren()
for i=1, #x do x:Remove() end
It would work... |
|
|
| Report Abuse |
|
|
|
| 08 Feb 2014 05:16 PM |
Actually, script 1 would fail anyway... Script 2 would also fail. I meant this:
x = game.Players:GetChildren()
for i=1, #x do x[i]:Remove() end
|
|
|
| Report Abuse |
|
|
|
| 08 Feb 2014 05:18 PM |
| Roblox doesn't use camel case so it would be more like AllowAccess but other than that this would be awesome for them to add. |
|
|
| Report Abuse |
|
|
| |
|
|
| 09 Feb 2014 06:35 AM |
@maxi1332: Its not the ultimate anti-exploit; we already have that.
Its an addition to the ultimate Anti-Exploit to allow games to work better with it. |
|
|
| Report Abuse |
|
|
|
| 09 Feb 2014 07:58 PM |
| More people support pl0x even though ideas on this forum never actually get added lolz. |
|
|
| Report Abuse |
|
|
| |
|
| |
|
| |
|
Kyuro
|
  |
| Joined: 03 Sep 2012 |
| Total Posts: 5800 |
|
|
| 02 Aug 2014 10:29 AM |
| SUPPORT! I want this SO badly. |
|
|
| Report Abuse |
|
|