This topic was automatically opened after 10 minutes.
this is awesome!
100% gonna improve my workflow on studio
thanks
7 Likes
Does this mean packages like for avatar? Or is this another meaning
2 Likes
Those are called “Characters” now. Packages are the reusable prefabs in Studio which auto-update.
5 Likes
Excellent.
2 Likes
This is amazing! I know this ain’t only for building but I’ve only tested with these so far and it’s just perfect!
12 Likes
Finally, i’ve been using packages for quite a while now and I remember how annoying it was using them like a year ago. I kept getting moderated for no absolute reason and I had to re-create the packages and put them back into each place of my game. Fortunately that issue has been resolved some time ago.
One change I don’t really like is this:
I don’t see the point of this? It will just be more of a hassle having to re-enable it everytime I edit a package.
1 Like
Reusable easily updatable content is not a metaverse concept lol
If you modify a package and it auto-updates it’ll overwrite your changes. Thats typically unwanted behavior.
4 Likes
Any videos about this?
Ah I see, so it depends on the situation/user preference. Thanks for explaining.
1 Like
It just released it’s too early to ask this right now but it’s pretty understandable to understand look at the post I made.
It works with scripts / builds but audio will not play so idk if there is point adding audio.
I always wanted to use packages, but the only one fluke I saw is their availability online…
I must be wrong of course, but can someone basically get to the marketplace page of your package and just get all your stuff like that? If yes, it’s a real privacy concern I’m not ready to look into… I really wanted to use those for obvious easniess reasons but I’m still reluctant to it…
Can someone cast a light on all this? Thanks in advance!
1 Like
Are there any plans to make it so that when you publish a package it goes live in every place that it’s used in instead of having to re-publish each individual place for them to be live?
6 Likes
Wow, this is amazing. This will really improve production massively. Thanks ROBLOX!
1 Like
Thank God. I was just having an issue with that a few days ago with the payphones around my game’s map, where I wasn’t able to publish changes because they were seemingly “modified” packages.
1 Like
Packages in the toolbox are in the “Inventory / My Packages” or “Creations / Group Packages” sections or in the Asset Manager under Packages. The privacy tab in the package details dialog allows you to control access to a package. The design is to enable people to collaborate on packages without exposing all other contents of the place.
So I can create a package:
Then edit the permissions (Right click in Explorer + Package Details + permissions tab):
You can see the asset id 11498290642, and even go to the library page:
(My Private Package - Roblox)
However, Roblox Studio backends will prevent unauthorized users from accessing the package contents. You can still copy / paste the instances making up a package between instances of Studio or you can save out the parts via Studio and send the RBXL or RBXM files to other users, but it won’t let unauthorized users download the contents of the packages to update them, etc.
5 Likes
Great change. What would be really great now, is if we could commit these changes, even if it’s not the master place.
2 Likes
Will I have to click this every time I open a script in a package or will this get changed in the near future? My entire project is nested in packages across multiple places so having to click this every single time I open any script is going to be very annoying.
5 Likes
Really happy that we can publish experiences without publishing the packages now. That happened to be an incredibly workflow damaging blocker especially when keeping development copies of a place. I’ve had to delve into some bad workarounds without this feature available.
The best workflow would be having the same package assets in both the live and development areas but only shipping finished changes from the development copy to the live. Since changed packages couldn’t be published, we always had to ship changes in parallel which defeats the purpose of a development copy because the live version would carry a potentially broken feature.
A number of my experiences have switched back and forward between using packages and not; they’re a powerful feature but this quirk blocked us on a lot of fronts especially when we do a lot of iteration. One of my experiences stopped using packages and started using a MainModule to inject changes between the development and live versions which is not a practice I support at all.
Thanks! 
3 Likes
This is exquisite, I love the changes done to packages recently
1 Like