I thought they were conflating attributes w/ properties, and typically player stats so to say are stored as some value type instance inside the player instance itself.
1 Like
This is an issue with accessing the GetAttribute member in Player, not that FPS isn’t a member of player.
Attributes return nothing if the attribute is undefined.
To the OP:
That code should work. LocalPlayer will always have a value in a LocalScript and the or Players:GetPropertyChangedSignal("LocalPlayer"):Wait() would never be reached.
It might be worth investigating to see if it’s this line, and not another line with the same call
1 Like
From what I have seen, I was right, it takes too long to put the attributes since the script exceeds 800 lines, that and that the script had to load all the data