If anybody wants to try mine out I put it here to test it:
umm, ok, I dragged the partā¦ thanks for looking at itā¦ I thought it had detection of and object and emits it when it is closer to itā¦
also what is different between play and run, I have always been doing Play in the past. thanks
It does but you have to move it to start the process. It didnāt do anything till i dragged it around.
Run is just like looking at the server vs client. It doesnāt launch the client when you choose Run.
You could do the same thing if you used Play but youād have to switch to Server view to drag the part around.
I figured out where you went wrong. Youāre dragging the wrong part. Donāt drag the effect part, drag the heli part (the invisible one).
I think you made the wrong one transparent.
ok, thanks, I will play around with it moreā¦a .rbxl file would be so coolā¦ but I guess this should not be that hard for me to set upā¦
I guessā¦
it is welded to the main part, so it cant fall into the void
Thank you! Pretty cool to see it in an actual game
Do you actually think live servers RENDER the game?
Ofc not, so this is still client-sided. It just has a network object attached to it rather than being handled completely locally, so thatās how it replicates.
In Studio, you are both the server and the client thus you can āseeā what the server sees, but in actual live servers i donāt think they render anything, they just data.
Altrough i do think this should be just done completely locally since particle emitters donāt need a network object attached to them.
It would be nice if you used Attributes for the configuration
Edit:
So iāve decided to improve your script by using Attributes also removed the Heartbeat event to instead be a regular while loop with task.wait(.2)
heli_script_improved.rbxm (7.9 KB)
Good call, I also didnāt use the heartbeat, I used a loop interval of 1/15 or .06666ā¦
Iām still not sure of the impact on a busy server with 10 or 15 of these helis running this loop.
I assume maybe if this was a client script then it could work on a busy full server