honestly quite incredible

honestly quite incredible

Also after checking your profile;
Your work looks really cool too! Keep it up, earned a follow from me. c:

When doing raycasts, you can detect these ghost parts rather than the actual player using some collision groups, this way you can reasonably do raycasts on the serverside with much less lag problems than usual.

There's more to it, but that's the gist of it!
Thank u for ur interest! :3
Means a lot.

These ghosts are under workspace.Camera on the server's side, so it does not replicate at all. (very important)

The parts that have ghost versions should be whatever's important for hitreg, and are also not interpolated, no real need.

Outside of this distance it just reverts to normal Roblox rep.

The server itself can't simply Pivot/CFrame the sending client with the info it recieves, since that would replicate back to them and just... Not work.

So it spawns a "ghost" for each player and their body parts.
Moving those instead.

If they're ragdolled they send the CFrames of any limbs that have moved too.

The server then does two things:
Forward it to any clients within a reasonable distance from the sender. Who then use it as an interpolation input, details aren't important, neither is the implementation in specific.

Sorry for the late response! I don't check my socials often.
I'll try to summarize it as best I can, but it'll have to be multiple posts.

Clients send the current CFrame of their HumanoidRootPart every 60th of a second or so, precision doesn't matter. Notably only if it's moved since last try.

EWWW WHAT DID THE AUDIO BALANCING DO TO IT

that hair is very gender <3