Connection between server and client

[jaunty comet]

I am making a single player cube combination rng game. Currently cubes are spawned on the server (Though its super buggy, they get flung, you can noclip through them sometimes).

I want to Clone those cubes to the client, and just leave them in some storage for server.

Whenever a combination is made on the client, the change gets replicated to server too.

Basically, all cubes on server and cloned to client must be equal.

How would i go about the logic on that?

i currently have 1 main server script, that uses multiple modules for the logic

Keep in mind, i want the game to (eventually) have cube saving

[rancid ether]

i just skimmed through the script i don't know how the player is suppose to combine the cubes but don't make them client side if you don't want them cheating

being buggy/being fling may be cause the cube is being spawned in the ground while being unanchored

[jaunty comet]

its a single player, it doesn't matter

[jaunty comet]

its spawned above ground, like 10-20 studs above

[jaunty comet]

i just need to know how to make the cubes from server replicate to client, and from client to replicate to server

or is it better to have the spawn script on client and then have a table of all cube data on the server?

[rancid ether]

i don't understand, anything that's placed into workspace or replicated storage is going to be replicated to client

[jaunty comet]

I want the cube to exist visually on the client, but not on the server

[rancid ether]

why?

well it doesn't matter

you can just use a folder and create an object with object values for server side

create it in replicated storage so client sees it

then create it visually like that

[wintry bolt]

use a method called effect to client replication

if you want to replicate a effect on the client, use a remote to tell the server you want to create it, then let the server fireallclients to all the clients for what the desired outcome

[feral summit]

then why not clone on server?

[wintry bolt]

too many effects that arent properly handled over time can slow the server for every player that's fresh to the server or joined hours ago

having it replicate to the client allows for the server side to be clean and still preform very well with minimal risk of performance leaks

[feral summit]

he's trying to sync it with server?

then just do it on server?

[wintry bolt]

elaborate

[feral summit]

what.

[wintry bolt]

he said he doesnt want it on the server

NOT on the server

[wintry bolt]

^

you can also see this method be used in some popular games nowadays too just to remove the risk of leaks, its really efficient

[feral summit]

nah u get it wrong

memory leaks cant be caused by cloning

im sure he wants to reduce bandwiths

[wintry bolt]

let me give you scenerios

you have a very old server with multiple parts in the workspace, dozens of effects that arent deleted. do you suggest that this wont lag the server over time? roblox is a good engine, but not that good.

if you have a old server with the replication method instead, it'll create a fresh new plate for the user, reducing the amount of initial lag, future lag, and hopefully give the user a clean experience

im not arguing with you like some power play, im just simply helping him get what he wants

[feral summit]

yea to reduce bandwiths and lags

[feral summit]

then when u are cloning on fking client

notify server

and tell

this combination is made

if the objects are static

then it'd be better to just clone on server

since no physics replication onto client

[jaunty comet]

Yall are confusing me, i am getting different suggestions