I can’t begin to thank ya’ll for this one. As a developer, I had to write pretty terrible code to optimize for large selection changes; which would inevitably cause the desired plugin behaviour, which relies on this event, to slow down studio.
I wonder if that fixes freezes when selecting, and copying deeply nested high instance count models. It’s such a bad problem that I began writing my own explorer plugin.
When reloading a single plugin or all plugins, the Output window will automatically be cleared to make any fresh output from the new run of the plugin(s) stand out clearly.
Can this be made as a setting? If I want to ensure that my plugin’s unloading capabilities are working, this has now become quite a bit more difficult. There’s already a “Clear output on start” option. So maybe a “Clear output on plugin reload” option? Wouldn’t mind if it defaulted to true, but it would be nice to have the ability to toggle this.
bunch of performance improvements and i like it, keep it up!!
Is this a practical concern you ran into and could share or just a theoretical worry?
I’m having trouble imagining what you would need to test here beyond statically created Instances being removed which you can easily see without the output. It’s not like you can safely save to the DataStore or network in your Unloading handler.
What if I clear the output before the unloading handler gets run?
Isn’t LuaCow usually the one who gives us the release notes?
This release notes had to be manually assembled thanks to weird release dynamics around the holiday season and person who did that isn’t the usual one (also why it came after the 607 one).
This fellow has a killer avatar though, I’m not complaining.
Bad news is it caused a regression and had to be disabled, so it’s not actually Live yet, it needs some amendments.
I see.
Could you explain to me what a regression means in this context? Just want to fully understand what you mean.
I understand to regress means to return to a previous state, but how does that apply here?
Sorry for the inconvenience. 
You can generally read “caused a regression” as “It fixed what it was trying to fix but broke something else that was previously working correctly”.
Hope the team had a end of december holiday!
Looking forward to all the beta’s coming out this year, roblox as an engine is beginning to get a little closer to the usability and moreover customizability of more mainstream engines. Keep up the good work!
Glad that they fixed the PivotTo() glitch, that has confused me several times
Yup, 0.6s sounds like not a big deal but sometimes for me it would get stuck resulting in 10s+ wait
this is actually insanely useful, if i were to add all the time up i prob would save around 25 minutes a day when I’m testing.