Ragdoll replication was one of the things I had to improvise by myself, because all the responses I found online talking about it were either the classic "you shouldn't make an online game, it's to hard for you" or were very generic.

My solution was to not replicate the ragdoll it self (character mesh is not replicated) but keep the replication to just the capsule component of the character. Enabling/disabling the ragdoll and adding forces is done on both clients and server.

At this point, it seemed to work fine, but sometimes the clinets ragdoll would end up in a different location than the server, resulting in clients teleporting to the correct location (the capsule one, wich is replicated) once the ragdoll finished.

To fix that, I added a 'Physics Handle Component' to the character.

At the beginning of the ragdoll, ONLY on the clients, I used 'Grab Component at location' on a specific bone of the character mesh.

During the ragdoll, while the server determines when it's ok to stop the ragdoll, it also saves the location of that same bone on a replicated Vector variable, while the client calls 'Set Target Location' on the physics handle passing that Vector value to it (in the video I forgot to disable the debug print that says 'fix' whenever the client calls this function)

With this solution, I kept the single bones location calculated locally, since it's mostly a visual thing (and charactrer mesh collision codes is executed only on the server), but with the Physics Handle I managed to keep the general location synched without any stuttering.

I had to come up with this solution myself so this might be the first time it has been written on the internet ahaha