Introducing Package Diffs!

[lovedanihonjin]

We’re thrilled to introduce package diffs, a step forward in expanding the diffing capabilities in Studio. From today, this feature is available to all for any package you can access.
New to packages? Learn how to get started here.

With package diffs, you can:

• Compare any two selected package versions
• View the 3D visual diff of the final output
• View the properties diff for any instance
• View the script diff across all scripts
• Understand changes to the package hierarchy

Try using package diffs to:

• Review updates and their impact on your copy
• Compare your local changes against the latest version
• Understand the content of past versions before restoring

Package diffs highlight our latest tech advancements in Studio. For the best experience, we suggest using this feature for package versions that are created after this release.

---

Feature Highlights

1. Getting Started

Select “Compare Package Versions” in the Explorer menu. This option is available for all packages that you have access to.

2. Version Selector

Select any two versions of a package to compare. When there’s an incoming update, the default view compares your local copy with the incoming version. Otherwise, it defaults to comparing your local copy with the latest version.

3. Package Hierarchy

Select instances to navigate diff views. Understand changes to the hierarchy with the following indicators:

• Changed instance
• Added instance
• Deleted instance

4. 3D Visual Diff

If your package contains a 3D object at its root, use the "Visual Overview" tab to view the visual diff.

View controls

• Pan with a drag/click of the left mouse
• Rotate with a drag/click of the right mouse
• Zoom using the mouse wheel
• Press the “f” key to refocus and center views
• Controls are synchronized across panels

The “Visual Overview” tab will always display the final 3D output in this release. While visual diffs for 2D objects and descendants outside the root aren’t currently supported, we’re committed to enhancing this feature based on your feedback.

5. Properties Diff

Read-only properties diffs are available for all instances. Understand changes to properties with the following indicators:

• Changed property or attribute
• Added attribute
• Deleted attribute

6. Script Diff

Script diffs are available for all scripts. Script diffs in packages use our existing diff component, ensuring that upcoming improvements benefit all.

---

Kudos for reaching the end!

Your early feedback will be instrumental in guiding future decisions and enhancements. Dive in and let us know!

Special thanks to the Robloxians who made it happen:

@Brienneofthetarth, @cruiser_forever, @strange_times, @MrMark2u, @BobaTops, @eugenekim159, @Rusi_002, @yipiokay, @CurbM0nkey

[ramdoys (Ram)]

This is so cool!! Let’s trot!!

[RoyallyFlushed (Royal)]

Oh. My. God! I have been wanting something like this for as long as I can remember!

No more will I have to worry about whether or not I modified something in a package that wasn’t a script.

[RobloxPhil2009 (Kobe)]

This is very nice!
No more worries in modifying something in package!

[leonbee0 (leon)]

Really great update I will be able to control my packages better. I can’t wait to try it!

[xalwaleedx (MinimumWageEmpIoyee)]

WOAH! This is amazing. Oh my god!
The dev team is crazy. These improvements for packages are ridiculously crazy!

[Steeq]

Cool, can something like this also be added for place versions of a game, so you know the changes of saved versions of the game?

Better English: “Could a feature be implemented to log the changes between different saved versions of the game for better tracking?”

[Maxoratus (Badass Max)]

i dont know what it is, but this is cool!

[corncob567 (Corncob)]

Another common Roblox W
Keep cranking out features like this.

Now if only we had a way to publish all of the places in a universe at once - that would keep my dev team from having to go into each and every place and publish changes whenever we update a single package.

[liqznaa (Nae)]

Neither do I, but this sounds cool

[Dimon9lul (Dimon)]

Another W update for modellers!! Btw, will there be any updates for translators? I don’t remember any in a while…

[lovedanihonjin]

This is great feedback. Having to manually “re-publish” a place takes away from the magic of mass-updating packages. I noted this feedback, and keep it coming <3

[AbstractAlex]

@lovedanihonjin

Having to manually “re-publish” a place takes away from the magic of mass-updating packages.

This is the #1 reason we don’t use packages for any of our games, and use InsertService + Models instead.

World Zero has over 50 uniquely built worlds/dungeons, so it would be impossible to update the game!

[lovedanihonjin]

Take a peek at our roadmap (if you haven’t already) under " Grow and engage your audience" > “Break down language barriers.” Let us know if you have additional thoughts!

[Dekkonot]

Is this the sort of thing we’d ever get a form of API exposed for? It’d be great to use it for Rojo!

[Alex645ca]

A way to do this for two games that aren’t part of the same universe would be nice too - one of my games has two different versions that are the same file with mechanic changes based on game.PlaceId, but it pre-dates the entire universe system so they’re not actually linked at all.

On top of this I made a hub place later that’s a group game, while the two aforementioned are under my profile. Real messy, but I don’t want to just move them because of the existing datastores and whatnot.

[leonbee0 (leon)]

A version of Rojo was released in the past weeks so that it can be examined in detail when changes are made to the project. If you want to take a look, it’s here.

Rojo v7.4.0-rc3

[Dekkonot]

I’m one of the developers for Rojo, I’m all too aware!

Having to create our own visualizer for property differences and scripts is a lot of work though, so if Roblox has one it’d be awesome if we could just have access to it instead.

[hyde12345678]

Roblox just casually creating some of the best updates: