- Create a package from a “Folder” instance
- Create a “Script” package, place it within the folder package
- Publish your changes to the “Folder” package
- Insert a second “Script” package into the workspace
- Change something about the workspace “Script” package
- Publish your changes to the workspace “Script” package
- Observe that your “Folder” package now requires you to publish it to get those new changes, it can no longer AutoUpdate
A less abstract example for clarity
My “GameCore” PackageLink is set to AutoUpdate. It contains several packages within it, namely “global_Banlist”.
I use these packages in other experiences, but I only use the “GameCore” package in this specific experience.
If I ever update global_Banlist, my GameCore package is rendered useless. It will never automatically update. I have to manually “discard” the changes for it to automatically fetch the most recent global_Banlist. Conversely, I can erase and re-insert my GameCore package - which is the whole thing packages is supposed to prevent.
The topmost package should automatically fetch the newest version of its nested packages when “AutoUpdate” is set to true. This used to be the case; otherwise, there’s no point in having “AutoUpdate” inaccessible for the nested packages.
AutoUpdate is now useless with nested packages. You must either “publish” the new change on every occurrence of this main package, or you must erase and replace each package manually.
Issue Area: Studio
Issue Type: Other
Date First Experienced: 2023-02-01 00:02:00 (-08:00)
Date Last Experienced: 2023-02-01 00:02:00 (-08:00)