Option to honor ScreenGui.ResetOnSpawn if ScreenGui is not direct child of StarterGui

[EtNowis]

with a normal ScreenGui directly under StarterGui, and its ResetOnSpawn = false, when the player character respawn, its LocalScript is not run again. which is the desired behaviour

However, tested with ScreenGui under Model and Folder, and its ResetOnSpawn = false, when the player character respawn, its LocalScript is run again, suggested that their ScreenGui are reseting.
sample.rbxl (61.4 KB)

Because the usual way of making package is to place it under a Folder or Model and then convert it into a package, this is important that the ResetOnSpawn behaviour should stay consistent.

Edit:
turns out it is bug reported before. so i change this into feature request.
Giving that some serious behavioral changes such as ‘SignalBehaviour’ are made possible with Options in ‘workspace’;
It shall be welcomed to have this HonorResetOnSpawn = default/always option available in StarterGui > Behaviour list

[YuNoGuy123]

This is seemingly intended behavior as per the developer documentation, I doubt it’s going to change. It’s super obnoxious though and I wish there was a way to disable this behavior.

[EtNowis]

could you point me to the doc for that behavior please? i might have missed that description.
and if that’s the case, then this would be a feature request instead of bug

[bvetterdays (roman)]

Already reported & labeled as intentional behavior due to backwards compatibility :

ScreenGui property "ResetOnSpawn" doesn't work when the Gui is inside of a folder

Hi David, thank you for the report! Unfortunately, this is a behavior change that would not be backwards-compatible. Experiences that depend on the existing behavior of ResetOnSpawn applying only to direct descendants would break. We will update the documentation to make clear that this is the expected behavior.

[EtNowis]

thanks. and s**t the title didn’t show ‘similar topics’ reported before so i kind of reposted the issue.
i can move it into feature request though.

[wallofgarlic (garlic)]

there is another post that kind of explains why it cannot be as well that was made just recently.

Functions connected to events through an ObjectValue pointing to an Instance in different ScreenGui are not running

Because it just loops through StarterGui:GetChildren and applies the rules to each child, it doesn’t explore the entire hierarchy. Imagine if you had one ScreenGui with Reset = false and another with Reset = true in the same folder… what would it even do with the folder? Or even worse a ScreenGui with Reset = false inside of one with Reset = true. Once you start exploring the idea of it looking deeper in the hierarchy you end up with a lot of awkward questions.