Server remote events

[sand phoenix]

So I've been coding my game like usual but I've came to a tragic revelation. My vfx are client sided only.. now I know I can use a fire server with a remote event to change the players equipped burst trail for each button. But is there a more compact way to make this client to server interaction?

I check the equipped trails by using a string value saved inside the player when they enter the game

For reference btw

[amber torrent]

brutha theres no other way than remote evnts if u wanna communicate with client to server

[sand phoenix]

OK just didn't know if there was some technical wizardry that could compact it more so thought I'd ask 👍

[harsh topaz]

another way would be to rely on data that is replicated from client to server, such as humanoid state and possibly animations and make the server almost entirely passive on the character, but for things you don't have this convenient replication yea remotes are the way to go

[chilly juniper]

yeah let's make parts have the network ownership for a player and the CFrame of the parts describes a f32 that we can use for data transfer that's such a reasonable and reliable way to do that yes indeed

[harsh topaz]

i dont think you understood a single word of what i just said

[chilly juniper]

no, that is pretty much exactly what you were saying

the same is the default about player characters

as for the other side of your comment about letting the server keep its details, good

but that is not what I was saying

[harsh topaz]

i hate to be the umm actually guy but, umm, actually, that was not at all what i was saying, and if you'll read it more closely you'll notice i never said anything about network ownership of any parts or cframing at all. i only mentioned humanoid state and animations, which your client sends to the server regardless without any extra work. this happens to work because of network ownership, but notice how i didn't mention it at all. secondly if you'll look closer at OP's question, they asked about replicating vfx on the character. depending on the vfx, i was saying if you can get it from info already replicated then use that.

[chilly juniper]

you didn't mention it, but it is included nonetheless

[harsh topaz]

at this point you might be wondering why, why would i say to use the data replicated from the client in this way instead of remote event? What possible reason could i possibly have to do that?

why would i come on the internet and spread lies and propoganda?

[chilly juniper]

um actually it's "propaganda"

[harsh topaz]

and the answer to that question is quite simple. it's because it's not lies, or propoganda. it is simply the fact that remotes will be received before physics data is, which means if you use remotes for say the spawnpoint of an effect on your character, it will be ahead of the character's actions, before the character has actually performed the action. video demonstration here. So i repeat, if you can get it from replicated physics such as humanoid state, then do so, otherwise just have to accept this remotes-are-faster-than-physics fact of roblox.

for reference the blue trail is physics replication, the purple block is remote event

notice how the purple block is far in front of the character on player 1's screen, and on the server

https://tenor.com/view/mic-drop-obama-barack-gif-13411519

[chilly juniper]

or, hypothetically, don't use network ownership

ez fix

i feel like you think i'm insane

but in reality, you can avoid character replication through ownership altogether