We understand the use cases here and want to address this in the future. Once again, Mass Updates will not change nested Packages. Now, I’d like to show you Auto-Updates in action:
This means that if you publish a Package copies modifications to the cloud version of your Package, it will not persist the Auto-Update boolean. Auto-Updates do not persist on inserted Package copies.This is due to how we currently handle modifications of Package copies.
Auto-Updates is not available for nested Packages.There are two things I would like for you to keep in mind with this feature: Once enabled, your Package will be automatically updated as soon as changes are published to your Package including Packages that are in different Places across your Game. Auto-Updates is configured at the Package copy level under the PackageLink object. Auto-Update, everything.Īuto-Updates is a powerful addition to the family. The length of time a feature will be in beta is determined on a feature-by-feature basis. In the mean-time you can run over to this post to enroll in our Beta program to get early access. After a brief beta period of our… beta feature… feature(?!) we will be enabling this option for everyone. Some of you may notice that option is not there.
0 kommentar(er)
