Recently (most likely after of the 358 release) destroying a part on the server doesn’t always replicate to the client. This seems to happen if the part has its Parent property set to a locally created object on the client.
Expected behavior would be for the part to always be destroyed, regardless of where it’s parented on the client.
Two parts are created on the server. Once replicated to the client, one part has it’s parent set to a locally created folder. A few seconds later both parts are destroyed on the server, but only one part is removed on the client (see output below).
Yep, confirming this. Change in last update that breaks replication when object is reparented locally (in FE-true context). This likely should be marked [ROBLOXCRITICAL]. Will be making a post with what I’ve got.
The feature has been disabled. The feature is sticky per user connection, so users will continue to be affected by this until they teleport or disconnect + rejoin.
I’ve noticed this issue occurring most of time if you parent a part to a locally created object at around the same time the object gets destroyed on the server.
To reproduce this in Coeptus’ place file, you have to change the wait()s circled in red in the PartParenter LocalScript and PartCreator Script to the same number:
