Hooking a .Changed to an object (Such as a Part or a Frame), and switching their colors (not confirming), causes the event to fire numerous times. It caused a little bit of a headache for me, because I was testing a TeamColor change (that should only happen every so often), and I was not expecting that.
I think if you’re able to cancel out of switching the property, it shouldn’t fire.
You changing them via script or via color picker thats built into studio?
Because if the latter, yeah its gonna fire multiple times because the BrickColor changes every time your mouse hover’s over a new color, regardless of selecting it or not, because thats how you get that real-time viewing of brickcolors.
The latter, I am aware of that.
But I feel somewhat like it shouldn’t fire.
This isn’t a bug, its an intended behavior. If you feel like it shouldn’t happen, then you might wanna change this to a feature request, because it is not a bug.
Okokok
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.