Simple request: a bool in starterplayer that lets us enable/disable resetting from the esc menu.
12 Likes
This’d also work perfectly as an addition to :SetCore().
4 Likes
Yeah, the reset button is a CoreGui thing rather than something specific to players, so SetCore would be more appropriate. StarterPlayer’s properties are also kind of numerous as it is, so with SetCore we can avoid bloating it.
I totally agree. If you didn’t know, though, you can disable this in a hacky way by renaming the humanoid.
Could add a poll.
I’ve been waiting for this forever.
Feature requests don’t really need polls.
3 Likes
Could easily added to SetCore, wouldn’t even need to iWait.
EDIT: Somehow I totally missed Polyhex’s post, while I remember reading EchoReaper’s response to it…
Blame the early morning I guess?
1 Like
Could also put the below into a localscript:
local player = game.Players.LocalPlayer;
local character = player.Character;
local humanoid = character.Humanoid;
humanoid.HealthChanged:connect(function(health)
humanoid.Health = 100;
end)
in a localscript if your players aren’t meant to die (e.g. you use a custom health system)
This is how I stop the reset button working in my game. 
You can already deny players from dying by using SetStateEnabled() and then the enum for dead (idk the exact code). Not perfect if you actually want to both disable the reset button and use kill blocks in your game, but hey, it’s something. I do remember that about a year ago, maybe even longer, it was said that they didn’t want to add such properties because they wanted to keep the menu exactly the same for all games. I agree though that such a property would be useful.
That’s actually what I’m doing, the problem is that since I have filtering enabled, the server doesn’t see the health change when reseting.
No idea what you’re saying…
You’re using SetStateEnabled from the client, right?
Yes, I disable the dead state on the client. When I reset, the client sees the health go to 0 but the server still sees it as 100.