Merge branch 'main' into patch-3

Author: IgnisRBX

content/en-us/art/accessories/accessory-fitting-tool.md

@@ -253,20 +253,11 @@ When fitting rigid accessories, a bounding box appears around the mannequin indi
   </figure>
 </GridContainer>
 
-#### Generate legacy accessory
-
-At this time, if you intend to sell your rigid accessory on the Marketplace, you must select **Generate Legacy Accessory** instead of **Generate MeshPart Accessory**. PBR textures are not yet supported for legacy accessories and the tool automatically applies your colormap to your mesh's textureID.
-
-<img src="../../assets/accessories/accessory-fitting-tool/Generate-Legacy-Accessory.png" alt="A dropdown appears above the GenerateMeshPartAccessory when expanded, displaying a Generate Legacy Accessory option."/>
-
-## Creating accessory
+### Create accessory
 
 You can create the accessory at any time. The tool applies any fit changes and generates the appropriate Accessory instance in the workspace depending on the type of accessory selected and any configurations applied.
 
-When you are ready to generate your accessory:
-
-1. If you are creating a **rigid accessory**, use the dropdown and select **Generate Legacy Accessory**.
-2. If you are creating a **layered accessory**, select **Generate MeshPart Accessory**.
+When you are ready to generate your accessory, select **Generate MeshPart Accessory**.
 
 <GridContainer numColumns="2">
   <figure>
@@ -279,10 +270,6 @@ When you are ready to generate your accessory:
   </figure>
 </GridContainer>
 
-<Alert severity = 'warning'>
-Rigid accessories that you intend to sell on the Marketplace require a `Class.SpecialMesh` and don't support [SurfaceAppearance](../../art/modeling/surface-appearance.md). Use the [Generate Legacy Accessory](#generate-legacy-accessory) option when creating your accessory.
-</Alert>
-
 With an accessory successfully created, you can now try the following:
 
 - Equip the accessory on an avatar-ready character by drag and dropping the accessory on an existing model, or using [HumanoidDescription](../../characters/appearance.md#humanoiddescription).

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

@@ -7,7 +7,7 @@ In many cases, you may want to convert a premade model from your modeling
 software into an accessory on Roblox. If you are looking to create your
 accessory from scratch, see [Create accessories](./creating-rigid/index.md).
 
-Using a provided 3D reference file, this tutorial covers each step in the workflow to properly configure and export a 3D model with PBR textures from Blender and generate your own rigid accessory in Studio. After you create the accessory, you can upload it to the Marketplace, save it to your toolbox, and use it in your own experiences.
+Using a provided 3D reference file, this tutorial covers each step in the workflow to properly configure and export a 3D model with PBR textures from Blender and generate your own **rigid accessory** in Studio. After you create the accessory, you can upload it to the Marketplace, save it to your toolbox, and use it in your own experiences.
 
 <Alert severity = 'info'>
 This tutorial only covers rigid accessories, and does not cover the process of converting more advanced clothing or character body models.
@@ -173,87 +173,13 @@ You've completed the exporting section of this tutorial. If desired, download a
 
 Studio's 3D Importer provides a quick and easy way to import third-party 3D assets into your projects. The importer provides object previews and error-checking to ensure that your asset meets Studio's general 3D requirements.
 
-To import your asset:
-
-1. In Studio, navigate to the toolbar's **Avatar** tab and select the **3D Importer**.
-2. In the file browser, select the `.fbx` file saved locally. The 3D Importer loads a preview of the object.
-
-      <img src="../../assets/art/accessories/creating-rigid/3D-Importer.png" />
-
-   1. If textures don't load for your asset, you can manually import your textures in Step 4.
-
-3. Select **Import**. The asset populates in your workspace as a `Class.Model` with the appropriate textures applied as a `Class.SurfaceAppearance`.
-
-   1. If textures didn't load correctly, add them manually. You may need to save and publish your experience in order to access the [Asset Manager](../../projects/assets/manager.md).
-
-      1. In the **Asset Manager**, click the **Import** button.
-      2. Upload your image files.
-      3. After moderation clears for your image, select the `Class.MeshPart` parented within your imported `Class.Model`.
-      4. Add a `Class.SurfaceAppearance` child to your `Class.MeshPart`.
-
-         <img src="../../assets/art/accessories/creating-rigid/Adding-Surface-Appearance.png" />
-
-      5. In the `Class.SurfaceAppearance` properties, click each property value and assign the appropriate texture image from the asset dropdown:
-
-         1. Set the **ColorMap** to the **\_ALB** texture image.
-         2. Set the **MetalnessMap** to the **\_MTL** texture image.
-         3. Set the **NormalMap** to the **\_NOR** texture image.
-         4. Set the **RoughnessMap** to the **\_RGH** texture image.
-
-            <img src="../../assets/art/accessories/creating-rigid/Surface-Appearance-Asset-Dropdown.png" />
-
-<Alert severity = 'success'>
-After successful import, your model object should populate in your project as a `Class.Model` with the appropriate textures applied. See [3D Importer](../../art/modeling/3d-importer.md) for additional information on import settings and troubleshooting.
-</Alert>
+To import your asset, check out the latest information on [importing rigid accessories](./importing.md).
 
 ## Convert
 
 After importing your asset into Studio, you can begin **fitting** your imported object to a mannequin and **converting** the `Class.Model` object into a `Class.Accessory`. When fitting and converting your accessory it's important to use the **Accessory Fitting Tool (AFT)** to correctly preview the placement and apply the correct configurations to your accessory.
 
-To fit and generate your accessory:
-
-1. In the toolbar's **Avatar** tab, open the **Accessory Fitting Tool** (AFT).
-2. In the new AFT panel, select the **Part** field and, in the workspace, select the accessory `Class.MeshPart` object in the workspace and press **Next**.
-
-   <img src="../../assets/art/accessories/creating-rigid/AFT-Select-Mesh.png" />
-
-3. On the Asset Type page, select the **type** of asset and the expected **body scale**. Press **Next** when complete.
-
-   1. This tutorial uses a **Hat** asset with an **Proportions Normal** scale.
-   2. Body scale is typically set based on the original sculpting and sizing of the asset. See [Body Scale](../../art/accessories/body-scale.md) for additional information on rigid accessory scaling.
-
-      <img src="../../assets/art/accessories/creating-rigid/AFT-Select-Type.png" />
-
-4. On the preview screen, select one of the humanoid characters as a mannequin:
-
-   1. In the Avatars section, select a humanoid base body character.
-   2. In the preview panel, deselect the previous selection. Only the humanoid body displays in the preview window.
-
-      <img src="../../assets/art/accessories/creating-rigid/AFT-Add-Avatar-Panel.png" />
-
-5. Using both the AFT preview window and the workspace, adjust the position, scale, and rotation of the accessory.
-
-   1. Use the AFT preview window and your mannequin as an accurate preview of how your asset fits on the character. The clothing mannequin in the workspace does not accurately portray how rigid accessories attach.
-   2. In the workspace, use the **Move**, **Scale**, and **Rotate** tools to adjust the positioning of your rigid accessory.
-   3. If you accidentally select something else, click back into the AFT panel to reselect the accessory and resume your adjustments using the transformation tools.
-
-      <video controls src="../../assets/art/accessories/creating-rigid/Fitting-Mask.mp4" width="100%"></video>
-
-6. After previewing and fitting your asset, select the **dropdown** next to **Generate** button to select **Generate Legacy Accessory** to create the Accessory and add it to your explorer.
-
-   - For rigid accessories that you intend to sell on the Marketplace you must use the [Generate Legacy Accessory](./accessory-fitting-tool.md#generate-legacy-accessory) option when creating your Marketplace accessories.
-   - PBR textures automatically convert to basic textures for these legacy accessories.
-
-   <img src="../../assets/accessories/accessory-fitting-tool/Generate-Legacy-Accessory.png" width = "30%" alt="A dropdown appears above the GenerateMeshPartAccessory when expanded, displaying a Generate Legacy Accessory option."/>
-
-<Alert severity = 'success'>
-After successful fitting and converting, your 3D model should populate in your project as a `Class.Accessory`. With this `Class.Accessory` you can perform any of the following:
-
-- [Upload the accessory](../../art/accessories/creating-rigid/publishing.md) to the Marketplace.
-- Use the accessory in your current experience by equipping it to character models with [HumanoidDescription](../../characters/appearance.md#humanoiddescription), or by dragging and dropping the accessory under the appropriate character `Class.Model` object.
-- Save the accessory to your [Toolbox](../../projects/assets/toolbox.md) to share or use within any of your experiences.
-
-</Alert>
+To convert your asset into a `Class.Accessory`, check out the latest information on [converting rigid accessories](./importing.md#convert-rigid-accessories).
 
 ## Upload and publish
 

content/en-us/art/accessories/specifications.md

@@ -275,7 +275,13 @@ You can use tools like the [Accessory fitting tool](../../art/accessories/access
 </tbody>
 </table>
 
-### Attachment points
+## Textures
+
+Textures created for accessories must meet Roblox's [texture specifications](../../art/modeling/texture-specifications.md).
+
+- Non-albedo maps (RGH, MTL, NOR) for rigid accessories cannot exceed 256x256.
+
+## Attachment points
 
 `Class.Attachment` objects indicate where an accessory model attaches to a point on a character body. Whether you are creating rigid or [layered](./layered-clothing.md) accessories, Studio's [Accessory Fitting Tool](../../art/accessories/accessory-fitting-tool.md) automatically adds and configures the appropriate `Class.Attachment` with the following specifications:
 
@@ -343,8 +349,6 @@ Accessories, such as clothing items, which stretch and fit around any character
 
 Your items must meet the following requirements before you upload them to the Marketplace to sell:
 
-- Rigid accessories that you intend to sell on the Marketplace require a `Class.SpecialMesh` and don't support [SurfaceAppearance](../../art/modeling/surface-appearance.md).
-  - Use the [generate legacy accessory](./accessory-fitting-tool.md#generate-legacy-accessory) option when creating your accessory.
 - Ensure that your items adhere to the [Marketplace program guidelines](../../marketplace/marketplace-policy.md).
 - Whenever applicable, ensure that your items adhere to Roblox's [custom mesh specifications](../../art/modeling/specifications.md).
 - Object `Class.MeshPart.Material|Material` is set to `Plastic`.

content/en-us/art/modeling/texture-specifications.md

@@ -85,7 +85,7 @@ See the following requirements for `Class.SurfaceAppearance` assets:
     <tr>
       <td>256×256</td>
       <td>2×2×2</td>
-      <td>Hair, shoes, tank tops, t-shirts, shorts, short skirts.</td>
+      <td>Hair, shoes, tank tops, t-shirts, shorts, short skirts. <br/><br/>256x256 is the **maximum budget** for non-albedo maps (RGH, MTL, NOR) for [rigid accessories](../accessories/specifications.md#textures).</td>
     </tr>
     <tr>
       <td>512×512</td>

content/en-us/art/validation-errors.md

@@ -450,7 +450,7 @@ See the following for more information on layered accessories:
   </tr>
   <tr>
     <td>Missing WrapLayer on layered clothing accessory `%s`. You need to create a child WrapLayer and try again.</td>
-    <td>Make sure you converted your model into a layered accessory (you might have [converted to a rigid accessory](../art/accessories/accessory-fitting-tool.md#generate-legacy-accessory) instead or selected the wrong asset type).</td>
+    <td>Make sure you converted your model into a layered accessory (you might have [converted to a rigid accessory](../art/accessories/accessory-fitting-tool.md#rigid-accessories) instead or selected the wrong asset type).</td>
   </tr>
   <tr>
     <td>The maximum vertex density has been exceeded. Reduce the number of vertices that are very close to each other.</td>

content/en-us/assets/accessories/accessory-fitting-tool/LC-Hierarchy.png

@@ -56,8 +56,7 @@ Expansion rewards.
 
 ### Daily Engagement Rewards
 
-Creators earn 5 Robux each day if their experience is one of the first three an Active Spender plays
-for 10+ minutes.
+Creators earn 5 Robux each day if their experience is one of the first three an Active Spender plays for 10+ minutes.
 
 <table>
   <thead>
@@ -76,6 +75,40 @@ for 10+ minutes.
   </tbody>
 </table>
 
+Daily Engagement Rewards pays Creators 5 Robux for each user who spends at least 10 minutes in their experience over the course of the day. To qualify, the experience must be one of the first three experiences that the user visits that day, and the user must spend at least 10 minutes in it. Users must be Active Spenders (meaning they must have spent at least $9.99 in the past 60 days) for their sessions to be eligible.
+
+<h6 style={{marginTop: '36px'}}>Example 1</h6>
+
+An Active Spender visits 5 experiences during the day in the following order:
+
+1. Experience A for 2 minutes
+2. Experience B for 5 minutes
+3. Experience C for 10 minutes
+4. Experience D for 5 minutes
+5. Experience A for 10 minutes
+6. Experience E for 15 minutes
+
+Experience A (where the user spent a total of 12 minutes), Experience C (where the user spent 10 minutes), and Experience E (where the user spent 15 minutes) each earn 5 Robux that day.
+
+Experience B and Experience D do not earn 5 Robux because the user didn't spend 10 or more minutes in them that day.
+
+<h6 style={{marginTop: '36px'}}>Example 2</h6>
+
+An Active Spender visits 5 experiences during the day in the following order:
+
+1. Experience A for 2 minutes
+2. Experience B for 10 minutes
+3. Experience C for 15 minutes
+4. Experience D for 5 minutes
+5. Experience E for 15 minutes
+6. Experience A for 15 minutes
+
+Experience A (where the user spent a total of 17 minutes), Experience B (where the user spent 10 minutes), and Experience C (where the user spent 15 minutes) each earn 5 Robux because they were the first three experiences the user visited and spent at least 10 minutes in that day.
+
+Experience D does not earn 5 Robux because the user only spent 5 minutes in it.
+
+Experience E also does not earn 5 Robux because it was the fourth experience the user visited that day, even though they spent over 10 minutes in it.
+
 ### Audience Expansion Rewards
 
 The audience expansion rewards system compensates Creators for bringing New Users to Roblox or for

content/en-us/assets/accessories/accessory-fitting-tool/Rigid-Hierarchy.png

@@ -164,13 +164,13 @@ To create a snapshot of your memory allocation:
 
 ### Analyze memory usage
 
-The tool provides five views that you can select from to view your Luau memory allocation based on different views:
+The tool provides many views into Luau memory usage:
 
 - **Graph** — Shows an aggregated memory usage tree, with each node representing an object with memory allocated.
 - **Object Tags** — Shows memory sizes and counts by runtime types, such as `function`, `table`, and `thread`.
-- **Memory Categories** — Shows memory sizes and counts by the engine-assigned memory categories. The engine assigns a memory category to an object at allocation time.
-- **Object Classes** — Shows memory sizes and counts by engine classes that your scripts use and store their instances, such as `EnumItem`, `Animation`, `CFrame`.
-- **Unique References** — Shows counts and total numbers of instances that don't have a parent in the data model and are only reachable by scripts, along with all paths that pin the instance object.
+- **Memory Categories** — Shows memory sizes and counts by engine-assigned memory categories. The engine assigns a memory category to an object at allocation time.
+- **Object Classes** — Shows memory sizes and counts by engine classes that your scripts use and store their instances, such as `EnumItem`, `Animation`, `CFrame`. Critically, this view does not show memory usage within the engine itself, only the Luau VM.
+- **Unique References** and **Unparented Instances** — Shows counts and total numbers of instances for **unique references** or **all remaining references** that don't have a parent in the data model and are only reachable by scripts. Also shows all paths that pin the instance object.
 
 #### Graph
 
@@ -180,7 +180,7 @@ The **Graph** view is the most detailed and complex view among all Luau heap vie
 - Self — The memory directly allocated for the data structure itself, excluding the memory usage by any content it contains.
 
 <Alert severity="info">
-The graph view displays elements smaller than 2KB as a single `…` node.
+The graph view displays elements smaller than 2 KB as a single `…` node.
 </Alert>
 
 <img src="../../assets/studio/console/Graph-View.jpeg" width="800" alt="An example Graph view" />
@@ -201,13 +201,13 @@ The root of the tree graph is `registry`, which stores all engine and Luau refer
 
 The **Memory Categories** view shows memory sizes and counts by memory categories, which the engine assigns to objects at allocation time. By default, the memory category has the same name as the script, or you can assign custom memory category names using the `debug.setmemorycategory` function.
 
-#### Unique references
+#### Unique references and unparented instances
 
-The **Unique References** view shows memory usage of instances that don't have a parent in the data model and are only reachable by scripts, along with all paths that pin the instance object. This view has two metrics:
+The **Unique References** and **Unparented Instances** views are related. Both show memory usage of instances that don't have a parent in the data model and are only reachable by scripts, along with all paths that pin the instance object. The only difference is whether the instance is a unique reference or not. Both views show two metrics:
 
-- **Count** — Shows the number of instances with the same name that are reachable from the same path, such as multiple instances named `Dragon` in the same table.
-- **Total Instances** — Shows the total number of objects inside those roots, such as all parts, scripts, and sound objects that construct a `Dragon` instance.
+- **Count** — The number of instances with the same name that are reachable from the same path, such as multiple instances named `Dragon` in the same table.
+- **Total Instances** — The total number of objects inside those roots, such as all parts, scripts, and sound objects that construct a `Dragon` instance.
 
 <img src="../../assets/studio/console/Unique-Reference-View.jpeg" width="800" alt="An example Unique Reference view" />
 
-This view is useful for identifying unnecessary connected instances, which you need to disconnect when you no longer need them. If you see many unexpected instances in this view, check out the paths holding them and evaluate whether they are necessary.
+These views are useful for identifying unnecessary connected instances, which you need to disconnect when you no longer need them. If you see many unexpected instances in this view, check out the paths holding them and evaluate whether they are necessary.