Instance.Changed and DataModel.ItemChanged signals no longer firing for script.Source property

Today one of our entire workflows was broken because of what we suspect is this flag being enabled.

We rely on “hot-reloading” script source changes to our scripts in Studio Play mode so that we can rapidly prototype gameplay parameters without having to restart the Studio Play instance every time.

As we know, it takes a non-trivial amount of time to get Studio play tests running, so we have devised ways to mitigate those time costs and this is one of those major workflows that is now no longer feasible to do. This would be a major blow to our productivity if it continues to be released as-is.

Expected behavior

We want script.Source signals to continue firing while in studio so we can listen to script changes that can immediately be applied to playtesting gameplay for rapid prototyping.

3 Likes

Thank you for the report.

We have re-enabled the signal for Source for the time being and we might keep the Plugin level properties like that still visible in the future as those are not exactly the target of non-scriptable/inaccessible properties that we need to limit.

5 Likes