Meaning all changes to the table have to go through the metatable, allowing me to log them using the print and warn functions visible in the code above. Since the module returns this metatable, the only reference to the PlayerData table is held within the Stats modulescript. When you require the modulescript, it returns a table full of functions linked to the PlayerData via a metatable. Basically the player’s data is stored in a modulescript under the player called “Stats”. You haven’t given much into how the data is processed after being added to the table, it’s hard to help without knowing what to look for. It appears to always be the same 3 things that pop up.īumping since I urgently need help on this, I can provide additional information if neededĮdit: Here’s the playerdata I’m currently using: I’ve also noticed in the microprofiler, when the spike occurs almost everything else is dropped except my GameCoordinator script and two other things. (even the smallest change like HP healing from 99 to 100 will cause lag) The amount of data you update the table also doesn’t affect the lag spike.The rate at which you update the table doesn’t affect the lag spike.Lag spike will occur ~3-5 seconds after updating any value in the table.If you change any value in the table to something other than what it currently is (e.g.The indices range from cash, inventory, basedata, to status effects, passives, and base stat boosts. Now the table is somewhat large (not millions of indices like you’d expect for lag) at 55 indices.

I’ve been debugging and analyzing the microprofiler and eventually found that the lag is caused by updating values in a table that stores the player’s data. Recently I’ve been experiencing frequent (maybe every 3-5 seconds?) large lag spikes while testing my game that last ~1.5 seconds.

Roblox studio lag