Ever since 671, AncestryChanged now fires on character parts whenever the player disconnects, this didn’t happen before and only started happening on the recent update, making me have to do two checks to make sure that the player left.
Expected behavior
For AncestryChanged to not fire on character parts whenever the player leaves.
Check your workspace PlayerCharacterDestroyBehaviour setting. if it is Default, explicitly set it to enable or disable to check if this is the cause of behavioural change
This has been enabled, but it only fired on Character now the character body parts.
Hi, thanks for posting!
This is working as intended. When a player disconnects, we expect AncestryChanged to fire for all descendants of the player model.
