Skip to content
robloxragdoll.org logo, a tilted blue square Ragdoll.org
Menu

Ragdoll on death after the November 2026 change

Since 11 November 2026 Roblox destroys a character right after CharacterRemoving handlers run. Ragdoll-on-death code that waits before touching the dead character now finds nothing. The fix: copy or clone first, then wait.

Updated · by the robloxragdoll.org editors

A robot dummy stuck with arrows falls over, Ragdoll Frenzy thumbnail
Image: Roblox / JustEvolve, official game thumbnail.

What breaks

Roblox’s announcement is specific: Destroy is called on Character models right after CharacterRemoving handlers run, and on Player instances five seconds after PlayerRemoving handlers run. Anything that reads a character’s children after yielding in CharacterRemoving, or tries to re-parent the destroyed character, fails.

The first public bug report shows the classic pattern: on death the game tags the character, waits a frame, clears Player.Character, then defers moving the character into a workspace.Ragdolls folder. After the change, that deferred move errors and the corpse vanishes.

Clone first, then let the original go

local Players = game:GetService("Players")
local corpses = workspace:WaitForChild("Ragdolls")

local function makeCorpse(character)
  character.Archivable = true
  local corpse = character:Clone() -- before any yield
  for _, d in corpse:GetDescendants() do
    if d:IsA("Script") or d:IsA("LocalScript") then d:Destroy() end
  end
  local hum = corpse:FindFirstChildOfClass("Humanoid")
  if hum then hum.BreakJointsOnDeath = false end
  corpse.Parent = corpses
  -- now ragdoll the clone with your module or constraint code
  return corpse
end

Players.PlayerAdded:Connect(function(player)
  player.CharacterRemoving:Connect(function(character)
    makeCorpse(character) -- no task.wait() before this line
  end)
end)

The clone is a new model the engine does not clean up, so it can lie in the world as long as you like. Remember to remove old corpses yourself (a cap per player, or a timer) — the memory leaks this change was meant to stop can come back through your own folder.

Saving values from a leaving player

The same rule applies to PlayerRemoving, and Roblox’s announcement shows it: read player.UserId and any leaderstats values at the top of the handler, then yield to save. The engine keeps the Player for five seconds after your handlers run, but only weakly, so do not count on it.

A jeep drags a ragdoll on a rope, Ragdoll Sandbox thumbnail
Image: Roblox / Rise To Top, official game thumbnail.

The Disabled switch is temporary

Setting Workspace.PlayerCharacterDestroyBehavior to Disabled restores the old behaviour, and a reply on the bug report suggested it as the quicker fix. Roblox’s announcement calls it a temporary measure: at the end of February the opt-out ends and the property is removed. Use the switch to buy time, not as the fix. Players wondering why bodies vanished can read the player-side explanation.

FAQ

How do I make players ragdoll when they die in Roblox?

Set BreakJointsOnDeath to false and ragdoll the character (or, since 11 November 2026, a clone of it made in CharacterRemoving before any yield) with BallSocketConstraints or a ragdoll module.

Why does my corpse disappear after respawn?

The character is destroyed right after CharacterRemoving handlers run. Clone it before yielding and keep the clone.

Can I just set PlayerCharacterDestroyBehavior to Disabled?

For now, but Roblox says the opt-out ends at the end of February, when the property is removed.

Sources

How numbers and codes are collected: methodology.

Advertisement