of     1   

complexo
#227616636Thursday, November 16, 2017 10:35 PM GMT

It'd help a lot with servers that have extremely huge maps.
GodShowsTheWay
#227616679Thursday, November 16, 2017 10:37 PM GMT

you can you can fire remotes from the server to specific clients and the client will create the relevant map part locally
complexo
#227627077Friday, November 17, 2017 4:26 AM GMT

That's not replication. It's good enough for games with static terrain, but it makes things way more complicated for games with changing terrain.
OzzyFin
#227629121Friday, November 17, 2017 6:32 AM GMT

We don't have much tools for rendering so you have to leave that job to ROBLOX. Toggle StreamingEnabled in Workspace. Don't create projectiles for clients that are far away from it but leave checks like that for the client to decide, don't make the server do too much work.
complexo
#227630877Friday, November 17, 2017 9:22 AM GMT

I know I shouldn't create projectiles for distant clients, but the entire point of this thread is to ask if I can avoid creating projectiles for distant clients.
OzzyFin
#227631509Friday, November 17, 2017 10:12 AM GMT

When the server tells a client to create a projectile: if distanceToCharacter <= renderDistance then --create the projectile else --dont create the projectile end ???
complexo
#227642677Friday, November 17, 2017 8:21 PM GMT

Replication is automatic.
OzzyFin
#227643362Friday, November 17, 2017 8:48 PM GMT

The proper way to create a projectile is have each client have their own and the server have its own. The server projectile can be destroyed on the clients. The client projectile is only for the visual effect and the client can decide whether to render it or not.
complexo
#227644181Friday, November 17, 2017 9:14 PM GMT

Creation and destruction are both extremely performance-costly operations. Is there really no way to prevent the projectile from ever being created for clients in the first place?
OzzyFin
#227646173Friday, November 17, 2017 10:19 PM GMT

No, there is not. Destroying is definitely not an "extremely" performance-costly operation. You're fine.

    of     1