Preventing the Player from dying / Reseting

[sage compass]

This is the code I found on dev forums:

local StarterGUI = game:GetService("StarterGui")

repeat
    local success = pcall(function()
        StarterGUI:SetCore("ResetButtonCallback", false) 
    end)
    task.wait(1)
until success

My only problem with it is that I am pretty sure that exploiters can just reenable the ResetButton as this must run on the client.

Is there any other way to prevent the Player from Reseting?

[silk oracle]

idk

[shy tundra]

** You are now Level 3! **

[sage compass]

❤️‍🩹

[lone kindle]

are you trying to prevent hackers to do anything?

if it is that you just can't

[sage compass]

I can't prevent exploiters from dying?

@lone kindle

Nvm i just tested and you are right. Only thing i can do is make them unable to respawn ig

[lone kindle]

yeah client side you cannot prevent hackers from doing anything, sad

[scarlet vale]

Nah you can’t, even if you disable the reset button they can just :Destroy() the lp head and it’ll kill them iirc

[proper notch]

Maybe you could ban them if they die but weren't supposed to

[sage compass]

A little harsh i would say as an anti cheat

[atomic trout]

What game are you making

[sage compass]

Some kind of FFA fighting game

[atomic trout]

So it's fine if the player resets, right?

[sage compass]

yeah. But not always

[atomic trout]

did you know .Touched is client sided

[sage compass]

It is. Kinda. Because the player has control over its body. But the server can limit their control

[atomic trout]

Touched when fired on the client also fires on the server

It's interesting

https://www.youtube.com/watch?v=SFAwwmb8G6o

[sage compass]

Why is it so unreliable then

[atomic trout]

It's reliable with checks

[sage compass]

I'd rather stay with my :GetPartsBoundsInBox()

[atomic trout]

That's good