I noticed a problem with using wait() or task.wait() function on client script. Sometimes the task.wait() event is triggered sooner than supposed to and it’s not normal is it something to do with client latency I’m trying to make a duration of 0.5 seconds of increasing exp while at the same time waiting 5 seconds before adding up the total of exp on the speed level
But it seems that after the first 5 seconds the whole total gets added up on each 0.5 seconds each
I also don’t understand an issue why does the event is being fired 2 times by the studio and client after I restart the game with data savings and increasing the level on treadmill
A memory leak would explain why a function connected to an event is running multiple times, but I’ll need to see the whole script to be able to confirm
As for why task.wait is being ignored, you might need to add a debounce to correct that problem
For the memory from my understanding and analyzing it has to do with data that was not saved properly and I was right down the hat as for the task.wait() I have no idea I think it has to do with client latency