I found out the hard way that apparently class:destroy() won’t run on client-sided components if the instance is destroyed by the server. The cause is that AncestryChanged gets disconnected on the client before it can run. Instance.Destroyed would probably fix this, but it still hasn’t been added =(
1 Like