Root detaches from the character upon death

When an avatar dies, the HumanoidRootPart is detached from the character.
To clarify, I do not know whether this is the bug or if there is a streaming bug. The reason for this bug report is that this behavior, or something affected by it, is causing streaming to stream everything out and then stream everything back in, causing a lot of lag and being visibly jarring.

If your character is standing on a tall place and the root falls below, in situations where streaming is more aggressive, this can cause the map to seemingly “reload”, due to instances streaming out and then back in upon respawning.

I am not sure when this started occurring, but it is a somewhat new behavior that did not use to exist years ago. (or at least not as evidently; not sure exactly whether the issue is this or a streaming related change; either way, I’ve fixed this in SCP: Roleplay by welding the root to the torso when the character dies)

Avatar Joints Upgrade does not affect this behavior.

I have included a repro file in the private message below.

A private message is associated with this bug report

root detachment public repro.rbxl (60.5 KB)

The issue:

With the root being welded:

You can always use RigidConstrains or AlignPositions for this.

Or welds.

But if I remember correctly, it has existed for a long time now.

When you have BreakJointsOnDeath on, it will always detach, if you don’t and use a custom ragdoll system, that could be detaching it?

Whether this behavior has existed for a while or not, it has never caused issues until recently. (assuming that it has in fact existed for a long time)

I don’t know if this is actually a bug or not, but either way I was told it’d be best to file a bug report so that it can be investigated.

The HumanoidRootPart’s CanCollide property is indeed changed by the ragdoll system we’re using, but it’s never been an issue before.

It is very much not normal to have the entire map unload and load back in when you die; the reports for this only started occurring this year and had never been a problem for the past 6 years.

All the bug reports for this are pretty recent; seems to have started around June from what I can see via bug reports.
(examples below)

I was about to mention that in my original post but it seems I missed mentioning that.

Yeah of course.