THE SHORT ANSWER
Roblox Studio version 743+ introduces Package Overrides in beta. Developers can now edit package instances (change properties, add instances) while maintaining a live link to the source package. Studio records each change as an override and reapplies it after source updates. Visual indicators (blue dots, green plus signs) show overrides in Explorer. Revert options exist in Properties and right-click menus. Usability improvements include removal of warning dialogs, auto-update support for edited packages, better status icons, full version history, and ability to publish parent packages with modified children. Known issues: Team Create requires all participants to enable the beta; nested
- Package Overrides let developers edit package instances locally while preserving the link to source package updates
- Studio tracks changes as overrides (property edits, added instances) and reapplies them automatically on update
- Visual indicators: blue dots for modified instances, green plus for added instances, parent indicators for nested changes
- Revert options in Properties window (per-property) and right-click Package menu (bulk revert)
- Usability improvements: no more warning dialogs, auto-update works on edited packages, full version history, publish parents with modified children
- Requires Studio 743+, enabled via File > Beta Features > Package Overrides
- Team Create sessions need all users on beta; nested package overrides have known update conflicts
Package Overrides arrive in Studio Beta
Roblox has released Package Overrides as a Studio Beta feature, addressing a long-standing limitation: customizing a package instance previously meant cutting it off from future source updates. With the beta enabled in Studio version 743 or later, developers can now modify package instances — changing properties, adding new instances, adjusting attributes — while Studio records each change as an override. When the source package publishes a new version, those overrides are reapplied on top of the update.
The feature is opt-in via File > Beta Features > Package Overrides, requiring a Studio restart. Existing packages and links remain unchanged until the beta is activated.
How overrides work in practice
The announcement uses a car package example: a developer uses the same car package across multiple places but wants one instance painted a different color. Previously, repainting broke the update link. Now, the color change becomes an override. When the package author later adds new tires or chrome trim, every instance receives those updates, and the repainted car keeps its custom color.
If both the source and the local override modify the same property, the local change wins. If an update deletes an instance that had overrides, those overrides are dropped. When publishing a package, any overrides on that instance become part of the new version.
Visual indicators and revert controls
Explorer now shows override state at a glance:
- Blue dot on an instance marks a changed property, attribute, or parent relationship
- Green plus marks an instance added locally
- Parent instances of marked items also display a dot, making nested changes discoverable
In the Properties window, each overridden property or attribute gets a revert icon. Linked properties (such as Color and BrickColor) revert together. For bulk actions, right-click an instance and choose Package > Revert Overrides on Instance, or right-click the package root and choose Package > Revert Overrides. Standard undo (Ctrl+Z / Cmd+Z) works on reverts.
Usability improvements beyond overrides
The beta removes several friction points that existed around package editing:
- Warning dialogs (including the Modified Packages dialog) are gone when editing or reverting packages
- Auto-Update can now stay enabled on packages that have been edited
- Package icons and tooltips now show state: latest version, pinned, pinned with updates available, or has overrides (blue dot)
- Publishing a parent package that contains modified child packages now works
- Version history displays every version with its notes, not just the latest 50
Known issues and Team Create guidance
Two significant caveats exist in this beta. For Team Create sessions, Roblox recommends every participant enable the beta. Edits made from a Studio without the beta are not tracked as overrides, so a subsequent package update may discard them.
Nested packages have a specific bug: when updating a parent package, an override saved inside a nested package can be mistaken for a local edit, causing the nested item to retain an old value instead of picking up the update.
What comes next
Roblox says APIs and nested package behavior are the next focus areas. The team will iterate based on feedback before rolling Package Overrides out to all users. Developers using Team Create should coordinate beta adoption across their team to avoid lost edits.