Excruciatingly strange issue

I must’ve spent hours on this dumb thing last night, and it still refuses to work completely.

Basically, I’m using tween service to animate a rotation value that determines where the door should be rotated. It has a max value of 25 either positive or negative. You can also turn on a flashlight, but if it’s determined that the door is still being animated upon, the user is not able to use their flashlight. For whatever reason, the function still returns true even though you can see in the picture the current value of RotationOffset is 25. And the absolute value of 25 is still 25, so 25 ~= 25 should actually be false? And yet it returns true and prevents me from using the flashlight when I should be able to…

Here’s what we got:

Roblox is screwing with me. Appreciate any help

This has got to be some weird crap with NumberValues, my guess is that it’s some sort of floating point imprecision bug that I can’t visually see at the surface, there’s no reason for this garbage to happen.

2 Likes

This is actually an engine bug with NumberValues. The number is still treated as a float despite me visually seeing it holds a value of 25. I tried rounding its value and that worked once, then I tried again and it didn’t work.

Roblox is honestly so bad sometimes, these issues shouldn’t even be in existence.

I guess I have to spend hours rewriting this crap due to their own ridiculous caveats.

2 Likes