|
| 04 Jan 2015 08:11 PM |
Recently, a new exploit is going around involving hopperbins. This exploit can affect all games that are using FilteringEnabled AND games that are not using filteringenabled. If you own a game, make sure to create an anti-exploit script using the following instructions.
However, first, I'd like to cover how it works. This is how it works, in a nutshell: 1. The player inserts a HopperBin into his or her backpack 2. The player modifies the type of hopperbin to a build tool 3. Because hopperbins are replicated, any changes to the world that the player makes will replicate to other clients - even when FilteringEnabled is on!
Here's code for protecting your game - please note that this will kick all players if you have a HopperBin in StarterPack (You really shouldn't - they're deprecated):
game.Players.PlayerAdded:connect(function(player) -- When a player joins the game player:WaitForChild("Backpack").ChildAdded:connect(function(child) -- When an object is added to the player's inventory if child:IsA("HopperBin") then -- If it's a HopperBin, then player:Kick() -- Kick the player end end) end) |
|
|
| Report Abuse |
|
|
| |
|
|
| 04 Jan 2015 08:21 PM |
game.Players.PlayerAdded:connect(function(player) -- When a player joins the game player:WaitForChild("Backpack").ChildAdded:connect(function(child) -- When an object is added to the player's inventory if child:IsA("HopperBin") then -- If it's a HopperBin, then child:Destroy() end end) end) |
|
|
| Report Abuse |
|
|
|
| 04 Jan 2015 08:28 PM |
game.Players.PlayerAdded:connect(function(player) -- When a player joins the game player:WaitForChild("Backpack").ChildAdded:connect(function(child) -- When an object is added to the player's inventory if child:IsA("HopperBin") then -- If it's a HopperBin, then player:Kick() -- Kick the player local message = Instance.new("Message", game.Workspace) message.Text = "ONCE AGAIN THE DAY IS SAVED, THANKS TO THE POWERPUFF GIRLS" wait(4) message:Destroy() end end) end) |
|
|
| Report Abuse |
|
|
|
| 04 Jan 2015 08:33 PM |
game.Players.PlayerAdded:connect(function(player) -- When a player joins the game player:WaitForChild("Backpack").ChildAdded:connect(function(child) -- When an object is added to the player's inventory if child:IsA("HopperBin") then -- If it's a HopperBin, then player:Kick() -- Kick the player print("ONCE AGAIN THE DAY IS SAVED, THANKS TO THE POWERPUFF GIRLS") end end) end) |
|
|
| Report Abuse |
|
|
|
| 04 Jan 2015 08:47 PM |
| Game makers will also need an anti-forcefield script because that's the other exploit that has been circling around the community. |
|
|
| Report Abuse |
|
|
|
| 04 Jan 2015 08:55 PM |
"Game makers will also need an anti-forcefield script because that's the other exploit that has been circling around the community."
I agree so much.
We should all get together and make an official anti-exploit script. It would use creative ways to prevent exploiters.
I could write a script that gets rid of forcefields just as easily as the op could getting rid of hopperbins, but hopperbins are outdated, forcefields aren't.
Sometimes people randomly get ForceFields from AFK scripts and other things, so we would have to find a way to identify that it was not in the inital scripting of the place
|
|
|
| Report Abuse |
|
|
|
| 04 Jan 2015 08:57 PM |
| That'll be easy. Just make a ForcefieldEnabled BoolValue in the player. When the developer wants the player to have a forcefield, set the value to true. If the value is false and the player has a forcefield, kick the player. |
|
|
| Report Abuse |
|
|
johny220
|
  |
| Joined: 30 Oct 2011 |
| Total Posts: 4584 |
|
|
| 05 Jan 2015 01:26 AM |
| if your game uses hopperbins that are given to you, you're basically screwed. |
|
|
| Report Abuse |
|
|
|
| 05 Jan 2015 01:38 AM |
| I agree with johnny here, the script should have something to detect other than just hopperbins, like maybe the serverstorage could have a model called 'AllowedBins' with all the hopperbins that a player can lawfully have, and then detect when a player enters AND when their backpack has something added to it, run a check to see if it's a hopperbin, then, if yes, run a check to see if it's in the allowedbin model, if no, kick. |
|
|
| Report Abuse |
|
|
|
| 05 Jan 2015 12:47 PM |
> local message = Instance.new("Message", game.Workspace) > message.Text = "ONCE AGAIN THE DAY IS SAVED, THANKS TO THE POWERPUFF GIRLS"
It's 2015 and we're still using Message objects. Wat. |
|
|
| Report Abuse |
|
|
Sinonon
|
  |
| Joined: 29 Nov 2014 |
| Total Posts: 22 |
|
|
| 05 Jan 2015 06:03 PM |
They aren't exploiters, they are SCRIPT KIDDIES.
Big difference guys, exploiters are the people who legitimately find the exploits. Script kiddies are the children who run around abusing and using them + usually leaking them.
|
|
|
| Report Abuse |
|
|
johny220
|
  |
| Joined: 30 Oct 2011 |
| Total Posts: 4584 |
|
| |
|
Malsumis
|
  |
| Joined: 07 Apr 2010 |
| Total Posts: 1461 |
|
|
| 07 Jan 2015 09:19 AM |
| Along with the force field exploit just turn the force fields off in the spawn point. That may help? |
|
|
| Report Abuse |
|
|
|
| 07 Jan 2015 07:45 PM |
| Still won't work. Because it's activated differently, probably not a script because they were patched. Maybe through a console command based exploit? |
|
|
| Report Abuse |
|
|