Mass updating packages in several places is tedious

[cloakedyoshi]

If you update all packages in multiple games within your universe:

The changes aren’t pushed live unless you open up each place and publish that place.

Having to open each place to do alt + p is annoying, non-intuitive, disruptive to my workflow, and wastes time:

There should be some form of option to allow for this, as that was the beauty of LinkedSource scripts.

Instead of force updating those places, I think the best solution would be to make it so that packages with the PackageLink set to “AutoUpdate” always grab the newest form of that package.

This means old servers continue to function properly while devs no longer have to manually update each place. Additionally, this gives more use to the “AutoUpdate” trait of a PackageLink.

[Natisb]

"Update All" feature of Packages does not work at all

The “Update All” feature present within the Game Explorer flat out fails to function at all. Packages in other places will retain older versions and not actually update. This error, in testing so far, occurs 100% of the time. Repro Setup and Performance: This setup is a fairly long process, so please follow each step carefully. Step 1: Create a new baseplate. Publish this baseplate to Roblox. Step 2: Open the Game Explorer window and add a new place to the Game. The name does not matter. Ste…

The response to this post may help with your issue, what you’re describing seems like intended behaviour.

[cloakedyoshi]

That is so not cash money. Thanks for directing me there, I wasn’t able to find a post about it. Moving this to a feature request.

[Shedletsky]

Roblox needs a cash money team to work solely on cash money solutions.

[cloakedyoshi]

Figure I’d update this thread cause of the bump.

Using “Publish Whole Game” is a very close solution, but it doesn’t have the versatility of package hotfixes (without publishing the game) that LinkedSources once supplied.

[nsgriff (griffted)]

We understand the use case desired here, and are working on potential solutions. I cannot guarantee a timeline.

[cloakedyoshi]

Mass updating packages in several places is tedious

Figure I’d update this thread cause of the bump. Using “Publish Whole Game” is a very close solution, but it doesn’t have the versatility of package hotfixes (without publishing the game) that LinkedSources once supplied.

Nevermind, this doesn’t work 100% of the time and can break games as a result. This doesn’t update packages perfectly.

[cloakedyoshi]

This very close solution is now impossible due to the removal (?) of the “Publish Whole Game” option.

[TheRings0fSaturn (SaturianNightmare)]

This is one of the main reasons I’m avoiding packages with a ten foot pole and why I think other developers should as well - not to mention this is why I’m rewriting my game from the ground up since I relied too heavily on packages.

An option of “Publish Updates To All Places” should be mandatory.

Currently, Packages lack a lot of core functions I want for me to even consider using them.

[DataBrain (Amber)]

Hey, I would like to bring this up again, as working with packages is absolutely essential for maintaining my current experience which has many places in the same universe.

Given that publishing multiple packages at once was apparently a bug (Can't publish multiple packages at same time - #4 by DataBrain), multiplexing packages through the auto-update feature would significantly improve my process in automatically pushing my experience to production, as currently it’s a much harder process.