The concept is too hard to explain in a devforums post, actually to clarify, it’s too hard if you’re lazy to clarify on a devforums post.
Basically, think of these as portals
In one portal (client) I have my arm tilting up, that’s the world that only I’m in, or in this case the player.
Each player has their own separate purple (client) portal that has their own things, but the server does not have that information, so nobody else can see that but the people in that purple portal. Everyone is in the blue (server) portal though.
But, there is a way for a purple portal to communicate with the main blue portal, and that’s with remote events.
This is the rundown on how client server model works. This applies with what your trying to do. The purple portal has the character’s arm angled up, but the blue portal does not have that information, so no one else can see it but the player’s separate purple portal, this can also be the same in reverse. The server can command that one client to have a certain piece of information no one else’s purple portal has.
So, whenever you want client → server | server → client, use remote events.
That’s the basics but that is the best I can give for devforums. Everytime your character’s arm angle changes on the purple portal, use a remote event to tell the blue portal the new angle.
local script = client (purple portal)
script = server (blue portal)
module script (can be both)
If you actually want to know how to send information across these boundaries, here’s remote event docs that you can read.
