I've attached a PoC which contains a RopeConstraint with two attachment points and a rbxmk script to demonstrate the issue.
When loading this model into rbxmk the Attachment0 and Attachment1 properties on the RopeConstraint are discarded cause the ClassIsA check used to decode these properties only checks the parent class of the value.
I've attached a PoC which contains a RopeConstraint with two attachment points and a rbxmk script to demonstrate the issue.
When loading this model into rbxmk the
Attachment0
andAttachment1
properties on the RopeConstraint are discarded cause the ClassIsA check used to decode these properties only checks the parent class of the value.Ref PoC.zip