It might just be me but doesn’t this seem hacky? In this post, I’m reading, it shows that it is just being multiplied to spin without having to rely on a seperate variable constantly updating alongside and setting it back? (tried it already though but didn’t work, might be because I’m doing something wrong 
)
I think you are thinking of when setting the old cframe of the part *cframe.angles(math.rad(n), 0, 0) that would not be good. But since you are making a new cframe it should not matter.
And no, for me it is perfectly smooth
I got it working with for i = 0, 359, 3 do loop
I meant as in:
while true do
wait()
local NumValue = 0
NumValue = NumValue + 1
-- Using NumValue for it
-- Setting it back to 0
-- Is constantly being done, reconnected and disconnected
end
Isn’t that somewhat hacky to store a variable for that or somewhat can be bad for performance?
@coworkerplus, I’m pretty sure that will just do it once unless it is done in a loop 
yeah i put it in a while true do loop so there is no wait time when the for loop ends
Set local NumValue = 0 outside the loop and from what i know that should work perfectly fine, if you just remember to set it to 0 when it reaches 360.
1 Like
pretty sure that just made it 100 times more complicated than it had to be, wouldn’t that loop the for loop which leads to looping the loop aka:
Loops within Loops.
@index_nil, I’ll use your method than, thank you 
However, if anybody has a better way of updating the value, please reply, but I’ll mark @index_nil as solution since he helped, thank you
1 Like