Opening an Old Place Version that has packages that got updated, will open the place with all packages updated to the Latest Version

[MarwanVRG4 (Miro)]

This is not a crucial bug, but it is not very pleasant because this means if I have to open an old place with packages. Then, I simply cannot do it without restoring ALL of the packages to the version I want, which will update the package in all places that have it. And in my case, this is even worse because I am trying to open an old version of a place that is in a Testing experience for the main game, which uses the same packages. So it is very complicated, and there is no real simple solution for it. Like for example, I now just published the version with new packages and now there is no way for me to restore and publish the version with the “old” packages

Beta Features Used: Dragger QoL Improvements, Face Capture, Import Queue, Incremental typechecking and autocompletion in studio, Live Animation Creator, New Luau Type Solver, New Studio Camera Controls, Next Gen Explorer, Studio solid modeling improvements, UI Drag Detectors, Unified Lighting, Video Uploads

Expected behavior

When you open an Old version of a place that has packages, it should just restore whatever package version or just delete the packages and show the local version of that model.

[devlvn]

I actually think this is intended behavior.
Do you have “AutoUpdate” enabled for your packages? If yes, this is definitely intended. You can read it here in the documentation of packages: Packages | Documentation - Roblox Creator Hub

[MarwanVRG4 (Miro)]

Yes, I do have it enabled, but that was because I didn’t want to manually update all the packages in every place every time I changed them. I didn’t think such a problem would appear, I still think that when opening a local old version of a place with packages, it should just show the version of the package at the time when the version was saved.

[devlvn]

Well, you can always restore your old version if that helps.
But I honestly think there is no need for improvement here, because if you want to avoide this from happening, you can just disable AutoUpdate.

However, if you really want to have this changed, I suggest you write a feature request, because this is not a bug.

[Ionelycore]

I made a feature request very similar to this a while ago, if this is what you’re on about. I don’t really see it as a bug on its own, but having the option to instead only use the local version would help.

Load any place with the option to disable all package's AutoUpdate

As a Roblox developer, it is currently too hard to open places that have packages with AutoUpdate enabled. I’d like to open an older version of my place, but this becomes very tedious when all packages in your game automatically get updated to the latest version, not the version that existed when you published the version (e.g. archiving, reverting). While this is what AutoUpdate is generally for, I do wish there was some way to open a place but disable AutoUpdate instantly, as the reasons of h…

[weeek53]

Thanks for reporting this. I submitted this as a feature request for package mass update. However, we do not plan on working on this feature now.