update Open Source Docs from Roblox internal teams

Author: rbx-open-source-docs[bot]

content/en-us/art/accessories/creating-rigid/publishing.md

@@ -21,9 +21,9 @@ Adding your asset to the Marketplace involves 2 steps:
 
 To upload your accessory:
 
-1. In the **Explorer**, right-click your accessory object and select **Save to Roblox…** from the context menu.
+1. In the **Explorer**, right-click your accessory object and select **Save to Roblox…** from the contextual menu.
 2. In the **Asset Configuration** window, set the **Content Type** to **Avatar Item**.
-3. Complete the following fields (you can adjust them later):
+3. Complete the following fields (you can adjust these later):
 
    1. **Title**: The name of your accessory.
    2. **Description**: A short description of your asset.

content/en-us/art/accessories/from-existing.md

@@ -288,7 +288,7 @@ The publishing process involves three major steps:
 
 If you intend to sell the asset on the Marketplace, use the following steps to begin the validation and upload process:
 
-1. In the **Explorer**, right-click your accessory object and select **Save to Roblox…** from the context menu.
+1. In the **Explorer** window, right-click your accessory object and select **Save to Roblox…** from the contextual menu.
 2. In the **Asset Configuration** window, set the **Content Type** to **Avatar Item**.
 3. Complete the following fields (you can adjust them later):
 

content/en-us/art/blender.md

@@ -602,7 +602,7 @@ The "UV" in UV editing stands for the axes on the 2D image map that you use duri
 
 Because 3D objects use the X, Y, and Z axes in the 3D space, 3D creation applications typically use U and V to avoid confusion when referring to coordinates in 2D image space. That being said, many Blender UI workflows still use X and Y, so it's helpful to know the 2D space equivalent axis.
 
-When you unwrap a 3D object, all active faces flatten into the 2D space in the UV Editor to make up the **UV map**, and different sections of the model split into separate groupings, commonly referred to as **UV islands**. For example, if you were to unwrap a standard Blender cube, each face becomes its own UV island in the UV map.
+When you unwrap a 3D object, all active faces flatten into the 2D space in the UV Editor to make up the **UV map**, and different sections of the model split into separate groupings, commonly referred to as **UV islands**. For example, if you were to unwrap a standard Blender cube, each face would become its own UV island in the UV map.
 
 <GridContainer numColumns="2">
   <figure>

content/en-us/parts/models.md

@@ -20,10 +20,12 @@ Characters, such as avatars or NPCs, are a single `Class.Model` containing the a
 
 ## Create models
 
-When you **group** objects together, they automatically become a `Class.Model` object.
+When you **group** objects together, they automatically become a `Class.Model` object. However, you can also insert an empty `Class.Model` object into the Workspace, then manually add child objects to the model.
 
-1. In the 3D viewport or the **Explorer** window, select every object that you want to group into a model.
-1. Right-click on one of the objects and select **Group**, or press <kbd>Ctrl</kbd><kbd>G</kbd> on Windows or <kbd>⌘</kbd><kbd>G</kbd> on Mac. A new `Class.Model` object displays with all of the objects that make up the model nested underneath.
+To create a model using the grouping method:
+
+1. In the **Explorer** window or 3D viewport, select every object that you want to group into a model.
+1. Right-click on one of the objects and select **Group**, or press <kbd>Ctrl</kbd> + <kbd>G</kbd> on Windows or <kbd>⌘</kbd> + <kbd>G</kbd> on Mac. A new `Class.Model` object displays with all of the objects that make up the model nested underneath.
 
    <img src="../assets/modeling/model-objects/Model-Group-Simple.png" width="320" alt="A close up view of the Explorer window. A Model object is highlighted with three nested children." />
 
@@ -109,6 +111,10 @@ See [Model Streaming Controls](../workspace/streaming.md#model-streaming-control
 
 When you upload or import a `.gltf`, `.fbx` and `.obj` model file to the cloud using the [3D Importer](../art/accessories/creating-rigid/importing.md), Roblox represents it as a cloud-based asset with a unique corresponding ID. This cloud-based asset system allows you to store models through Roblox and reuse them across the platform in various contexts without maintaining local copies as part of each saved Studio experience.
 
+<Alert severity="info">
+There is a limit of 15,000 unique assetIds that can be referenced in a single model.
+</Alert>
+
 To upload a model you made in Studio:
 
 1. In the **Explorer** window, right-click your model. A contextual menu displays.
@@ -127,10 +133,16 @@ To upload a model you made in Studio:
 
 ## Distribute models
 
-You can distribute models to the [Creator Store](../production/creator-store.md) for other creators to use within their own experiences as long as each model only references open use assets or restricted assets that you have created. Once you distribute a model, all newer versions include the same restictions even if you later unlist it from the Creator Store.
+You can distribute models to the [Creator Store](../production/creator-store.md) for other creators to use within their own experiences as long as each model only references:
+
+- Open use assets.
+- Restricted assets that you created, excluding audio and video.
+- Free assets from the Creator Store, including audio and video.
+
+Once you distribute a model, all newer versions include the same restrictions even if you later unlist it from the Creator Store.
 
 <Alert severity="info">
-If you want to distribute a model with a child audio or video asset, you must distribute the audio or video asset on the Creator Store before making them a child of the model for the audio or video to be audible and visible at runtime.
+If you want to distribute a model with a child audio or video asset that you created, you must distribute the audio or video asset on the Creator Store before making them a child of the model for the audio or video to be audible and visible at runtime.
 </Alert>
 
 As with any asset, all models must adhere to the [Community Rules](https://en.help.roblox.com/hc/articles/203313410), [Terms of Use](https://en.help.roblox.com/hc/articles/115004647846), the [DMCA Guidelines](../production/publishing/dmca-guidelines.md) regarding copyright and Creator Store [asset moderation](../production/creator-store.md#asset-moderation) rules. When creating models for the Creator Store:

content/en-us/production/creator-store.md

@@ -174,7 +174,7 @@ Assuming the asset is in your [inventory](../projects/assets/toolbox.md#inventor
 <TabItem label="Explorer">
 To upload an asset from the [Explorer](../studio/explorer.md) and distribute it in the Creator Store:
 
-1. In the [Explorer](../studio/explorer.md) hierarchy, right-click the asset you'd like to distribute and select **Save to Roblox...** from the context menu.
+1. In the **Explorer** window, right-click the asset you'd like to distribute and select **Save to Roblox...** from the contextual menu.
 2. In the **Asset Configuration** window that opens, confirm and/or update asset details such as **Title** and **Description**. Additionally:
 
    - For **Content Type**, make sure **Development Item** is selected.

content/en-us/production/sell-on-creator-store.md

@@ -6,7 +6,7 @@ description: An explanation of Creator Store seller accounts, their prerequisite
 You can sell [plugins](../studio/plugins.md) on the Creator Store for **United States Dollars** (USD). Roblox offers a market-leading revenue share for these sales, as only taxes and payment processing fees are deducted.
 
 <Alert severity="info">
-You will soon be able to sell [models](../parts/models.md#upload-and-distribute-models) on the Creator Store for **United States Dollars** (USD). You can create a seller account and start uploading models now.
+You will soon be able to sell [models](../parts/models.md#distribute-models) on the Creator Store for **United States Dollars** (USD). You can create a seller account and start uploading models now.
 </Alert>
 
 In order to set any USD prices and sell your assets, you must have a **seller account**. Roblox administers seller accounts through **Stripe**, a third-party payments provider. If you meet Roblox's eligibility [requirements](#for-sellers), you can fill out Stripe's [application form](#complete-the-application-form) to create a seller account.

content/en-us/projects/assets/packages.md

@@ -17,26 +17,32 @@ The most efficient workflow is to [create a package](#create-packages), [share i
 
 ## Create Packages
 
-You can create a package from any single object or any single parent and children branch of objects. If you want to create a package for a single object, we recommend adding it to a `Class.Model` grouping first so that you can add, remove, or scale instance within the package later without breaking the package.
+You can create a package from any single object or any single parent and children branch of objects. If you want to create a package for a single object, add it to a `Class.Model` grouping first so that you can add, remove, or scale child objects within the package later without breaking the package.
 
-1. In the **Explorer** window or 3D viewport, right-click the desired object and select **Convert to Package**.
+<Alert severity="info">
+There is a limit of 15,000 unique assetIds that can be referenced in a single package, and you must have permission to use all included assets. For more information, see [Asset privacy](privacy.md).
+</Alert>
+
+To create a package:
+
+1. In the **Explorer** window or 3D viewport, right-click the object you want to turn into a package, then in contextual menu, select **Convert to Package**.
 1. In the new window, fill in the package details. In particular, if you're working in a [group](../../projects/groups.md), set **Ownership** to the appropriate group in which you have permission to create/edit group experiences.
 
    <Alert severity="warning">
    Ownership transfers are **not** supported by the asset system, so carefully consider the owner when creating a package.
    </Alert>
 
 1. Click **Submit**.
-1. After the conversion completes, the object receives a "chain link" symbol in the Explorer window to identify it as a package. Additionally, you can see a new **PackageLink** object parented to the object.
+1. After the conversion completes, the object receives a "chain link" symbol in the **Explorer** window to identify it as a package. Additionally, you can see a new **PackageLink** object parented to the object.
 
    <img src="../../assets/studio/packages/PackageLink-Explorer.png" alt="A maple tree model in the Explorer window with the package icon next to it." width="215" />
 
-1. (Optional) Select the **PackageLink** object and enable `AutoUpdate` in the **Properties** window. Note how the icon changes to indicate that the package is set to automatically update.
+1. **(Optional)** Select the **PackageLink** object and enable `AutoUpdate` in the **Properties** window. Note how the icon changes to indicate that the package is set to automatically update.
 
    <img src="../../assets/studio/packages/PackageLink-Explorer-Auto.png" alt="A maple tree model in the Explorer window with the auto-update package icon next to it." width="215" />
 
 <Alert severity="error">
-Don't delete or move the **PackageLink** instance! Doing so for any package copy converts the copy back into a normal object and loses package capabilities such as ability to update when there's a new version.
+Don't delete or move the **PackageLink** object! Doing so for any package copy converts the copy back into a normal object and loses package capabilities, such as ability to update itself when there's a new version.
 </Alert>
 
 ## Insert packages
@@ -65,21 +71,21 @@ Be careful when inserting assets that you didn't create into your experiences, a
 
 ## Publish package changes
 
-You can publish any changes you make to a package as a new version to make them available to other copies of the package throughout the place and across all experiences. Note that it's **not** required to publish a modified package before publishing a place (the modified version is saved along with the place for future iteration).
+You can publish any change to your package as a new version, making your updates available to other package copies throughout the place and across all experiences. It's **not** required to publish a modified package before publishing a place because the modified version is saved along with the place for future iteration.
 
 To publish changes to a package:
 
 1. In the **Explorer** window or 3D viewport, right-click the modified copy and select **Publish to Package**.
-1. If a package copy has [auto-update](#automatic-updates) turned on, it immediately pulls in the updated version when you open the place that contains them. Other copies get a white dot on the package icon that indicates an update is available. You can [individually update](#update-outdated-copies) or [mass-update](#mass-updates) them as needed.
+1. If a package copy has [auto-update](#automatic-updates) turned on, it immediately pulls in the updated version when you open the place that contains them. Other copies get a white dot on the package icon that indicates an update is available. You can [individually update](#update-outdated-copies) or [mass-update](#mass-updates) all copies.
 
    <img src="../../assets/studio/packages/Package-Update-Available.png" alt="Two packages in the Explorer set to auto-update, and one with an update available." width="215" />
 
 1. **(Optional)** Add a description of your changes:
 
    1. Right-click the package and select **Package Details**.
-   1. In the Asset Configuration window, select **Versions**.
+   1. In the **Asset Configuration** window, select **Versions**.
    1. Under your most-recent change, select **Add**.
-   1. Describe your changes and click **Submit**.
+   1. Describe your changes, then click the **Submit** button.
 
 ## Update outdated copies
 
@@ -97,7 +103,7 @@ To update one or more package copies to the latest version:
 
 Extensive use of packages may result in many package copies across multiple places in an experience. In addition to [individual syncing](#update-outdated-copies) and [automatic updates](#automatic-updates), you can update all copies of a package through **mass updating**.
 
-1. (Recommended) Close other Studio instances with any of the experience's places open; this prevents another unsaved instance of a place from potentially overwriting your updates.
+1. **(Recommended)** Close other Studio instances with any of the experience's places open; this prevents another unsaved instance of a place from potentially overwriting your updates.
 1. In the **Explorer** window or 3D viewport, right-click the desired package and select **Update All**.
 1. Choose all places in the experience or some subset of places and click **Update**.
 
@@ -113,6 +119,8 @@ Mass updating packages automatically **saves** the selected places but does not
 
 To make syncing easier, you can set a package copy to update automatically whenever a newer version is published. Auto-update of the package copies will take place when a place is opened in Studio.
 
+To automatically update package copies:
+
 1. In the **Explorer** window, expand the package's hierarchy tree and select its **PackageLink** object.
 
    <img src="../../assets/studio/packages/PackageLink-Explorer.png" alt="A close up view of a packaged chandelier model in the Explorer window. The PackageLink object is highlighted." width="215" />
@@ -125,11 +133,13 @@ Automatic updating does not apply to [modified](#modifying-packages) package cop
 
 ## Share and access levels
 
-You can grant permission to friends, experiences, groups, or specific group user roles so that they can freely use your packages in their creations. For more information on asset access, see [Asset privacy](privacy.md).
+You can grant permission to friends, experiences, groups, or specific group user roles so that they can freely use your packages in their creations. Once you share a package, all future versions of that package have the same restrictions even if you later revoke package sharing. For more information on asset access, see [Asset privacy](privacy.md).
 
 <Tabs>
   <TabItem key = "1" label="To collaborators">
 
+In order to share packages with other collaborators, the package must only contain references to assetIDs that you created or have explicit permission to use.
+
 To change package permissions for a collaborator, such as a friend or group:
 
 1. In the **Explorer** window, **Toolbox**, or **Asset Manager**, right-click the desired package and select **Package Details**.

content/en-us/projects/assets/privacy.md

@@ -27,7 +27,7 @@ The asset privacy system controls which creators and experiences can use the ass
 In order for a collaborator, such as an individual creator or group, or an experience to use one of your restricted assets, you must explicitly grant permission before it's visible or audible at runtime. Once a collaborator or experience has **explicit** permission to use a restricted asset, they also receive **implicit** permission to use the asset in a variety of additional scenarios. For more information, see the following subsections.
 
 <Alert severity="warning">
-If a restricted asset is a child of an open use model or package from the [Creator Store](../../production/creator-store.md), creators and experiences must have explicit permission to use the restricted asset in order for the asset to be visible or audible during runtime. For example, if a model includes a `Class.Sound` object with a restricted assetID, the open use model remains visible, but the restricted audio cannot play.
+If you receive a model or package from the [Creator Store](../../production/creator-store.md) that was **created** _after_ late May 2025, all of its underlying restricted assets are visible or audible during runtime. For any assets created prior to this date, you must receive explicit permission to use each restricted asset in order for them to be visible or audible during runtime.
 </Alert>
 
 ### To collaborators

content/en-us/reference/cloud/toolbox-service/v1.json

@@ -218,6 +218,18 @@
               "nullable": true
             }
           },
+          {
+            "name": "includedInstanceTypes",
+            "in": "query",
+            "description": "When searching for models, this filters that the following [Instance](https://create.roblox.com/docs/reference/engine/classes/Instance) types are included in the model.",
+            "schema": {
+              "type": "array",
+              "items": {
+                "$ref": "#/components/schemas/ModelInstanceType"
+              },
+              "nullable": true
+            }
+          },
           {
             "name": "includeOnlyVerifiedCreators",
             "in": "query",
@@ -814,6 +826,10 @@
             "type": "boolean",
             "nullable": true
           },
+          "includeOnlyValidCreators": {
+            "type": "boolean",
+            "nullable": true
+          },
           "filterForVisibleAssets": {
             "type": "boolean",
             "nullable": true
@@ -947,6 +963,35 @@
         "description": "Representation of a model asset.",
         "nullable": true
       },
+      "ModelInstanceType": {
+        "enum": ["Script", "MeshPart", "Decal", "Animation", "Audio", "Tool"],
+        "type": "string",
+        "description": "A list of model instance types. See Toolbox.Service.Models.Internal.InstanceCounts and [Instance](https://create.roblox.com/docs/reference/engine/classes/Instance) for more details.",
+        "x-enumNames": [
+          "Script",
+          "MeshPart",
+          "Decal",
+          "Animation",
+          "Audio",
+          "Tool"
+        ],
+        "x-enum-varnames": [
+          "Script",
+          "MeshPart",
+          "Decal",
+          "Animation",
+          "Audio",
+          "Tool"
+        ],
+        "x-enum-descriptions": [
+          "Script",
+          "MeshPart",
+          "Decal",
+          "Animation",
+          "Audio",
+          "Tool"
+        ]
+      },
       "ModelSubType": {
         "enum": ["Ad", "MaterialPack", "Package"],
         "type": "string",