this also happened with mine I used a lot LESS of loops and a lot LESS remote events to solve it I used strings to determine specific tasks for one remote event that helps lower down lag another way is to lower down use of remote events that may or may not solve the problem
this sounds worse than his current problem
how does it sounds worse? mind giving me a reason
using āa lot of remote events and a lot of loopsā is not better than this, itās still very memory costly, the only thing that would make sense would be the server freezing and sending a ton of packets
i said NOT using alot of loops and remote events bruh
wait oop sorry haha i forgot to add LESS sorry lol
oh, misread that then, still, he tried using remote events and it didnāt improve it, letās just end this here until Alvin comes back with new info
yea and again sorry for the misunderstanding lol
1 Like
My customer manager script (which is what requires the pathfinder module) does sometimes show high usage, activity of 9% at times and also server memory does rise to high levels over time.
1 Like
Well, youāre the only one that has access to the script so there isnāt much we can help with from this point onwards unless you share it with us.
I suggest looking to see if things fire more times than expected, Iām somewhat dumb so I canāt think of anything else lol
Have you thought of rounding the values to some decimal point(letās say maximum 2 decimal digits)? That way the string which getās encoded/decoded and the client receives will be much smaller.
Did you manage to fix it? Seen no update for 21 hours so Iām curious about what happened
Hi everyone, thought Iād give an update!
I found the cause of this problem. When I was developing my A* pathfinder I generated parts for each node to visualise paths. That meant hundreds of parts were being created on the server for each path, and being replicated to the client. I had set these parts to be invisible, and although I did delete them once the path had been created, they would still replicate to the client and cause a huge buildup of packets whilst the path was being generated.
So, for 10 NPCs, that would mean a huge amount of parts per pathfinding call. All I had to do was remove the code that generates these parts as theyāre no longer needed. The game feels MUCH more responsive and faster now that I removed this code.
So, if anyone else has a similar problem, just keep checking your scripts for any parts or objects which may be replicating to the client every few seconds.
Big thanks to everyone who gave their help and support 
16 Likes