This has been mentioned before, but the original topic didn’t get enough attention. Hopefully this one might do.
This bug occurs when you reset through the menu with BreakJointsOnDeath set to false, while standing on any BasePart that is unanchored.
I mainly used a chassis model of mine to reproduce the bug, since that’s how I first found it. But i’ve tried with other types of parts and got it to happen too, both in studio and the game client.
Humanoid events such as .Died and even .HealthChanged are not fired, and RespawnTime is completely ignored, meanwhile, the character is dead on the client, but it is actually still (somewhat) alive on the server. Changing Health to 0 or moving the character far enough from the part in the server will actually kill the character.
This is a quite serious issue for me, since I am working on a game with vehicles in it, and BreakJointsOnDeath is disabled in favor of a ragdoll module use in the game. (i. e. a player is sitting or standing on a vehicle, and they decide to reset, chances are they will remain ‘dead’ there until they managed to somehow be moved away from the vehicle, get actually killed or by leaving the game.)
My thoughts on this bug is that it might be related to the network ownership change that happens automically with nearby players, considering the fact that characters die normally when far enough from the BasePart they were standing on.
I have been thinking about doing something like that (Changing the reset button callback). I currently haven’t tried that, might aswell try that later.
Late reply and kind of a bump, but @LuaShoe’s method works effectively. Setting up a RemoteEvent and firing it on the client when the player’s character dies, and if the character is still alive server-side, the event will kill it, here’s a quick example:
--local script
local Players = game:GetService("Players")
local ReplicatedStorage = game:GetService("ReplicatedStorage")
local RemoteEvent = ReplicatedStorage:WaitForChild("RemoteEvent")
local Player = Players.LocalPlayer
Player.Character.Humanoid.Died:Connect(function()
RemoteEvent:FireServer()
end)
--server script
local ReplicatedStorage = game:GetService("ReplicatedStorage")
local RemoteEvent = ReplicatedStorage:WaitForChild("RemoteEvent")
RemoteEvent.OnServerEvent:Connect(function(Player)
if Player.Character.Humanoid.Health == 0 then return end
Player.Character.Humanoid.Health = 0
end)
I guess I will be using this workaround until the bug is fixed.
This is still not fixed. Users are experiencing “infinite deaths” in my game since we use a custom character spawning method, meaning CharacterAutoLoads is disabled. Because of this bug, the .Died event never fires and players get permanently stuck. This is an extremely annoying bug and deters the experience of a lot of players.
Not sure if it’s related, but I got the same issue while I was working on some custom characters, expect that the Died event doesn’t fire on the server even when standing on any kind of part, anchored or not.
However, I noticed that if I go in first person after the death on client, the event then fires. More generally, I noticed that the event doesn’t fire on the server if the character is not moving (so typically when we reset from the Roblox menu), so I have a quick workaround consisting of applying an impulse through the AppyImpulse method on all parts of the character when Died event fires on the client, and now it works.
I hope this gets fixed. I already have some workarounds for other issues too in my games and it is becoming annoying not to do things intuitively.
I noticed the same thing while playing in vr, they also used a custom spawning method. I ended up dying repeatedly.
This might be a different bug with similar appearance since it’s vr, but it’s similar enough that it warrants posting here.
This needs to be fixed.
I can confirm that this bug is still happening. When Humanoid.BreakJointsOnDeath is set to false, the Humanoid.Died event will 100% of the time fire on the client and not on the server. This bug impacts any game where Player.CharacterAutoLoads is set to false. One can only fix this by setting up a RemoteEvent and making it fire whenever the local player’s character dies.
I made a ragdoll script today and found this issue as well. Similarly to what OP said, this happens whenever I am standing on an unanchored part or near the object (e.g. touching).