I know this was solved already, but I would like to recommend to use GetPropertyChangedSignal("[THE PROPERTY]") because it would be more efficient, as it directly tracks a specific property, say for this instance, your Value property. Just a recommendation, though.
Sorry for bumping this thread but i just wanted to respond to this quote specifically that GetPropertyChangedSignal does not seem to work very well for me due to this error.
No it wouldn’t. .Changed for instances such as (IntValue, NumberValue, StringValue, etc.) will only fire for the .Value property so GetPropertyChangedSignal is just a bigger hassle to type, is less efficient because the .Changed passes in the new value so you don’t gotta re-access it, and is just unnecessary.
I figured that overall, and I do apologize for not including the specifics details, but mostly it’s a better alternative to know of and get used to, especially when considering other instances that you’d need to track a certain property of, and said instance has more than one property that could be changed. Though, thank you for correcting me.