Weird problem with HumanoidDescription

[Scriptos]

At the bottom of the first post of the thread that you linked, it states that your method of waiting for the ancestry of the character to change is broken and that you have to check for the parent first. It even provides code for the fix.

@TheGamer101

This change could break code which is relying on the current ordering of events. For example, this will break code which is waiting for the character to be added to the Workspace as follows.

player.CharacterAdded:connect(function(character)
    -- With the new ordering AncestryChanged won't be fired because the character will already be in the Workspace
    character.AncestryChanged:wait()
    -- do stuff
end)

The changes required to so that code is compatible with the new event ordering should be minimal, the above example can be changed to the following during the migration period.

player.CharacterAdded:connect(function(character)
    -- When the new ordering is enabled it will be guaranteed that the character is in the Workspace when CharacterAdded is fired.
    -- This check is temporary to migrate from the old event ordering
    if not character.Parent then
        character.AncestryChanged:wait()
    end
    -- do stuff
end)

[dcampeon (dororl)]

That’s for the new event ordering, which isn’t released yet, apparently it’s on hold or something like that.

[Scriptos]

It says “during the migration period” so I took it to mean that’s what you do right now as you wait for the change to be live.

Edit: Didn’t realise that it’s all the way from April and keeps getting delayed.

[colbert2677 (ImagineerColbert)]

This is a different (and unrelated) circumstance. Characters do not have their appearance automatically loaded and replaced via HumanoidDescriptions. Automatic appearance loading is disabled and substituted for starter character assets. Armour pieces and weapons are attached to the character via accessories.

[Goldthyr]

Applying HumanoidDescription with a package thats not default R15 package results in stuff being parented to nil This is a problem