It’s very difficult to simply detect if an attribute has been changed in a rollback by the server due to the simple fact that an attribute change in the server is not reflected in GetAttributeChangedSignal() by the client (as shown here).
I’ve read that this was disabled to prevent rollbacks/resimulations (correct me if I’m wrong, but I think they’re the same thing?) from triggering the signal. However, this is now preventable with a simple RunService:IsResimulating() check at the start of any of the connected functions (similarly to how IAS can be handled).
Therefore, I think the GetAttributeChangedSignal() calls should fire on the client, regardless of whether it came from the server or not.
7 Likes
I also don’t get why this is a thing. It’s just a value.