:Destroy from the Client on something that is inside LocalPlayer.Character will not fire .Destroying on the Server

[Club_Moo]

Yeah. This seems like the direct result of the lack of documentation [and making a new policy] for the against-the-FE-grain of having client destructive control of the Character.
Over the years many have posted on the subject and many improvement ideas have been shared as well.
The fact that this has been “swept under the rug” I bet is the reason it was “forgotten” about.

The article on the fixed Destroy() replication (and new Destroying Event) talks about how it is
Server-to-Client, and only mentions in passing the security implications of it going the other direction.

Destroy() Can Now Replicate to Clients

Greetings Developers, Coming soon, calls to :Destroy() on the server will replicate to clients. What exactly does this mean? TL;DR: Try changing the ReplicateInstanceDestroySetting under Workspace to Enabled for your experiences and see how they are affected, as we plan to enable it by default in the future. Current Behavior You may have noticed that currently when you call :Destroy() on an Instance, that Instance will be destroyed, meaning that it and all its descendants: Will have their …

Given this, it appears that the special-case of the local character may have been completely overlooked.

And given this post, it’s not unreasonable at all to assume that this should work Client-to-Server:

Instance:Destroy() Only Replicates Parent = nil Change

It’ll fire regardless of where the Destroy came from (the network, Lua code, or C++ engine code). And engine code always uses Destroy where appropriate. Though it should be noted that there are some cases where Destroy is not used, mostly in the case of Studio commands (for instance the Delete key in Studio does not Destroy things because you could not undo their removal if it did).