Option to disable property change events on instances

As a Roblox developer, it is currently too hard to efficiently change properties on instances in mass, as well as temporally stop checking for .changed events. Right now (as far as I’m aware) if you change properties it will always fire changed events, even if you don’t want it or are not using them.

If Roblox is able to address this issue, it would improve my development experience because it could allow for more optimized changing of instances as well as an easy and intuitive way to temporally stop checking for .changed events. I’m not a Roblox engineer and I do not know how these events work behind the scenes but I do know that :BulkMoveTo() contains a way to disable some of the .changed events and this does have a noticeable performance improvement!

My main use case is to enable highly optimized instance modifications where ever possible and where ever an experience developer chooses. I can think of atleast 10-20 different locations I would implement this right now without hesitation. I do a lot of dynamic script based animations with parts and ui all the time. I would love to be able to make these operations faster to enable a smoother play experience for my players.

I would love to hear from a Roblox developer on the specifics on weather or not this would be possible! Thanks for reading! :3

10 Likes

1 up on this.

My game barely relies on changed events.

I have no use of .Changed().
I have two uses of .GetPropertyChangedSignal(), one for camera ViewportSize and one for textbox text.

Every time a property changes with no event connection, it just seems like a waste of resources if it’s going to fire in the background. My aforementioned uses of changed events already have very simple workarounds.

It would greatly improve resource usage if all changed events were just togged off.

3 Likes