Attachment0/Attachment1 Gets Cleared When Changing Parent Of AlignOrientation To Nil

[Fm_Trick (Trick)]

Reproduction Steps

Set AlignOrientation.Parent to nil and Attachment0/Attachment1 will also be set to nil.

Expected Behavior

Attachment0/Attachment1 properties should not be changed unless set manually (as it was before)

Actual Behavior

local part = script.Parent

local alignOrientation = part.AlignOrientation

print(alignOrientation.Attachment0, alignOrientation.Attachment1) -- Attachment, Attachment

alignOrientation.Parent = nil

print(alignOrientation.Attachment0, alignOrientation.Attachment1) -- nil, nil

Workaround

Set Attachment0 manually after changing parent from nil

Issue Area: Engine
Issue Type: Other
Impact: Moderate
Frequency: Constantly
Date First Experienced: 2022-12-08 17:12:00 (-07:00)

This behaviour was changed without alerting the community and thus resulted in broken games.

[ordinarygamer212]

This has also been an issue for me. Yesterday it was working just fine, but today it has broken my game and made it unplayable until I had to work around it. Hopefully it wasn’t intended.

[Floo_d]

Reaaallly relieved that its not just me experiencing this!

This bug resulted me in removing a movement feature in my game temporarily until I could find a fix. I didn’t realize the attachment properties were being set to nil.

hopefully this bug gets resolved.
by the way thank you op for discovering this! i was able to put a fix in my game

to add: this issue is also occurring with the LinearVelocity constraint as well. Which could also mean other constraints which rely on attachments are affected by this too.

[APandaPoet (熊熊熊)]

Update: It should be resolved now.

---

Thanks for reporting! We are looking into it.