Lock all parts on game start (anti-exploit)

Help and Feedback Scripting Support
#1

I noticed that with the standard set of btools that you create in most exploits, you cannot click on/select locked parts, exactly how they behave in studio. I’ve noticed that there’s somehow a way for exploiters to delete parts in an FE enabled game and having it show up for all players. I was wondering whether having a script that locks all parts at the start of the game would help with this? I’ve seen it in some places also where there’s a localscript that ensures there’s, let’s say 5, transparent non-collidable parts that are locked over the camera so when the exploiter attempts to use a delete tool they can only delete the invisible parts right in front of the camera that keeps regenerating. Anyway, what do you guys think of it? Does anyone have any other ideas? Thanks.

1 Like
#2

The client-server model does not allow that to happen; you can’t see the deleted parts from their client. The only way this happens is due to an exposed remote or non-FE’d games.

Locking might work, unless the exploiter manages to inject a script that unlocks everything.

Oh, and this block of text is hard to comprehend without proper paragraphing(not necessary).

2 Likes
#3

This is an XY problem. A better solution is to figure out how they are doing this, and they are most likely using a remote event somewhere.

For future reference, here’s how you’d do it.

for i,v in pairs(workspace:GetDescendants()) do
    if v:IsA('BasePart') then
        v.Locked = true
    end
end
2 Likes
#4

It must be a remote then, and yeah sorry about this turning into an XY problem

#5

It’s FE so it must be a remote then. I forgot to mention explorer script that can just show all parts in the game like the explorer in studio so it could help but wouldn’t be a complete fix.

#6

A exploiter can just unlock everything or do workspace.Part:Destroy(), best thing to do is check for collisions through the server.

2 Likes
#7

Either you have an insecure remote or they have network ownership of the part (though I do not believe deletions replicate, even if a user has network ownership of a part).

Locking a part isn’t really going to do anything. Most exploits ignore the property.

I also feel sad that no one references my XY problem thread and jumps straight to linking the website. Tear drop.

1 Like