update Open Source Docs from Roblox internal teams

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

content/common/navigation/cloud/reference.yaml

@@ -47,8 +47,6 @@ navigation:
     path: /cloud/features/badges
   - title: Bans and blocks
     path: /cloud/features/bans-and-blocks
-  - title: Chats
-    path: /cloud/features/chats
   - title: Connections
     path: /cloud/features/friends
   - title: Creator Store
@@ -318,12 +316,6 @@ navigation:
         versions:
           - name: v1
             path: /cloud/legacy/gameinternationalization/v1
-      - title: Game join
-        type: cloudlegacy
-        ignoreTranslation: true
-        versions:
-          - name: v1
-            path: /cloud/legacy/gamejoin/v1
       - title: Games v2
         type: cloudlegacy
         ignoreTranslation: true

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

@@ -26,7 +26,7 @@ If you meet certain account requirements, you can sell your custom meshes as acc
 
 See the following specifications for general geometry:
 
-- **Budgets** - Individual meshes can not exceed 10,000 triangles. Avatar items have their own individual budget requirements for [characters](../../art/characters/specifications.md) and [accessories](../../art/accessories/specifications.md).
+- **Budgets** - Individual meshes can not exceed 20,000 triangles. Avatar items have their own individual budget requirements for [characters](../../art/characters/specifications.md) and [accessories](../../art/accessories/specifications.md).
 - **Watertight** - All geometry must be watertight without exposed holes or backfaces.
 - **No N-gons** - Meshes must be in quads where possible.
 - **Volume** - Meshes cannot be 0 thickness and must have some volume.

content/en-us/assets/data/data-store/Data-Stores-Manager-Page.png

@@ -8,7 +8,14 @@ With the Data Stores Manager, you can browse and monitor your data stores, their
 ## Access the Data Stores Manager
 
 <Alert severity="info">
-  If you're the owner of an experience or the group owner of a group-owned experience, you have access to the Data Stores Manager by default. To give access to members of your group, [grant them permission](../../projects/groups.md#roles-and-permissions) to **View Data Stores Manager** or **Edit all group experiences**.
+If you're the owner of an experience or the group owner of a group-owned experience, you already have full access to the Data Stores Manager by default.
+
+To give members of your group access to the Data Stores Manager, you can [grant them one of the following permissions](../../projects/groups.md#roles-and-permissions):
+
+- **View Data Stores** lets them view the Data Stores Manager page in the Creator Hub.
+- **Edit Data Stores** lets them delete keys.
+- **Delete Data Stores** lets them delete data stores.
+- **Edit all group experiences** gives them full access to all of the functionality of the Data Stores Manager.
 </Alert>
 
 To access the Data Stores Manager:
@@ -18,6 +25,9 @@ To access the Data Stores Manager:
 
 <img src="./../../assets/data/data-store/Data-Stores-Manager-Page.png" alt="Overview of Data Stores Manager page displaying the Summary section, the Data Stores list, and the Keys list." />
 
+<br/>
+<br/>
+
 The **Summary** section of the Data Stores Manager page includes the **Total Size** and the **Storage Limit** of your data stores. The Total Size is calculated by adding the number of bytes consumed by all existing keys in your experience, and the Storage Limit is calculated based on your experience's lifetime user count. For more information about storage limits, see [Limits](./error-codes-and-limits.md#limits).
 
 ## View data stores and keys
@@ -37,3 +47,22 @@ To further drill down into each specific data store, you can:
 - Select a key entry, select a version under **Version History**, and click **Compare Version** to compare the current key entry version with the version you selected.
 
 <img src="./../../assets/data/data-store/Data-Stores-Manager-Compare-Versions.png" alt="Comparison of two key entries in a data store." />
+
+## Delete data stores and keys
+
+<Alert severity="info">
+When you schedule a data store for permanent deletion, that data store immediately becomes inaccessible. Any attempts to read or write to its entries will fail.
+</Alert>
+
+To schedule a data store or key for permanent deletion:
+
+1. Go to Creations and select an experience.
+2. Go to **Configure** > **Data Stores Manager**.
+3. Click the **Action** menu next to the item you want to delete.
+4. Click **Mark for Deletion**.
+
+There is a cooldown period between when you delete a data store or key and when that item is actually deleted. During this cooldown period, you can undo the deletion and restore the item to its normal state.
+
+To restore a data store, click the **Action** menu next to the data store you want to restore and then click **Restore**, or call the [`UndeleteDataStore`](/cloud/reference/DataStore#Cloud_UndeleteDataStore) method from the Open Cloud API.
+
+To restore a key, call the `Class.GlobalDataStore.UpdateAsync|UpdateAsync` method from the Engine API or the [`UpdateDataStoreEntry`](/cloud/reference/DataStoreEntry#Cloud_UpdateDataStoreEntry__Using_Universes_DataStores) method from the Open Cloud API.

content/en-us/cloud-services/data-stores/data-stores-manager.md

@@ -56,6 +56,20 @@ Data store rate limits for the [Open Cloud v1](/reference/cloud/datastores-api/v
         </ul>
       </td>
     </tr>
+    <tr>
+      <td>Delete</td>
+      <td>
+        <ul>
+          <li>Delete Data Store</li>
+          <li>Undelete Data Store</li>
+        </ul>
+      </td>
+      <td>
+        <ul>
+          <li>300 requests/minute/universe</li>
+        </ul>
+      </td>
+    </tr>
   </tbody>
 </table>
 

content/en-us/cloud/guides/data-stores/throttling.md

@@ -100,12 +100,12 @@ The `Class.ParticleEmitter.Color|Color` property tints each particle's texture t
    **keypoint** that determines the color value of the property at that point in
    the particle's lifetime.
 
-	 <img src="../assets/studio/general/ColorSequence-White-Keypoints-Labeled.png" width="640" alt="Keypoints labeled in color sequence popup" />
+    <img src="../assets/studio/general/ColorSequence-White-Keypoints-Labeled.png" width="640" alt="Keypoints labeled in color sequence popup" />
 
 1. Click the keypoint at the start of the color sequence, click the
    small square next to **Color**, and select a color from the popup window.
 
-	 <img src="../assets/studio/general/ColorSequence-Red-White.png" width="640" alt="Color sequence popup from red to white" />
+ <img src="../assets/studio/general/ColorSequence-Red-White.png" width="640" alt="Color sequence popup from red to white" />
 
 1. If you want particles to change their color near the end of their
    lifetime, click the keypoint at the end of the color sequence, click the small square next to **Color**, and select a color from the popup window.
@@ -393,9 +393,24 @@ Particle flipbook textures let you animate a particle's texture over its lifetim
 
 <video src="../assets/lighting-and-effects/particle-emitter/Flipbook.mp4" controls width="800" alt="Flipbook looping over the four particles in its texture"></video>
 
-To use particle flipbooks, the flipbook texture must be of pixel dimensions 8×8, 16×16, 32×32, 64×64, 128×128, 256×256, 512×512, or 1024×1024. If the texture isn't a square with one of these dimensions, you can't set flipbook's properties in the [Properties](../studio/properties.md) window.
+To use particle flipbooks, the texture's dimensions must be divisible by the number of frames in the layout grid. If the texture's dimensions are not compatible with the layout grid size, a warning appears next to the `Class.ParticleEmitter.FlipbookLayout|FlipbookLayout` property in the [Properties](../studio/properties.md) window.
 
-The flipbook texture can have a frame layout of 2×2, 4×4, or 8×8. For example, the following 1024×1024 image has an 8×8 layout, so it's suitable for a 64‑frame animation.
+<GridContainer numColumns="2">
+  <figure>
+    <figcaption>
+    <Alert severity = 'success'>Valid flipbook texture size</Alert>
+    </figcaption>
+      A 1024&times;1024 texture with a `Enum.ParticleFlipbookLayout.Grid4x4|Grid4x4` layout. The texture's dimensions are divisible by 4, so each frame is 256&times;256. Similarly, a 1024&times;512 texture with a custom layout of 8&times;4 is compatible because 1024 is divisible by 8 and 512 is divisible by 4.
+  </figure>
+  <figure>
+    <figcaption>
+    <Alert severity = 'error'>Incompatible flipbook texture size</Alert>
+    </figcaption>
+      A 100&times;100 texture with a `Enum.ParticleFlipbookLayout.Grid8x8|Grid8x8` layout. The texture's dimensions are not divisible by 8, so the frames cannot be divided evenly. Similarly, a 1024&times;1024 texture with a custom layout of 10&times;10 is incompatible because 1024 is not divisible by 10.
+  </figure>
+</GridContainer>
+
+The flipbook texture can have a frame layout of 2×2, 4×4, 8×8 or custom. For example, the following 1024×1024 image has an 8×8 layout, so it's suitable for a 64‑frame animation.
 
 <img src="../assets/lighting-and-effects/particle-emitter/8x8-Explosion.png" width="512" alt="Sample texture for particle flipbooks" />
 
@@ -413,6 +428,7 @@ Once you've specified a valid flipbook [texture](#texture) for the emitter's `Cl
 - **Grid2x2** &mdash; 2&times;2 frames for a 4-frame animation.
 - **Grid4x4** &mdash; 4&times;4 frames for a 16-frame animation.
 - **Grid8x8** &mdash; 8&times;8 frames for a 64-frame animation.
+- **Custom** &ndash; A custom grid size defined by `Class.ParticleEmitter.FlipbookSizeX|FlipbookSizeX` and `Class.ParticleEmitter.FlipbookSizeY|FlipbookSizeY`.
 
 To further customize the flipbook behavior, you can adjust the following properties:
 
@@ -427,7 +443,9 @@ The `Class.ParticleEmitter.FlipbookMode|FlipbookMode` property determines the ty
 - **OneShot** &mdash; Play through the animation only once across the particle's lifetime. With this setting, the `Class.ParticleEmitter.FlipbookFramerate|FlipbookFramerate` property doesn't apply; instead, the framerate is determined by the particle's `Class.ParticleEmitter.Lifetime|Lifetime` divided evenly by the number of frames in the animation. **OneShot** animations are useful for clear non-repeating animations, such as an explosion that creates a puff of smoke and then fades out.
 - **PingPong** &mdash; Play from the first to the last frame, then in reverse from the last to the first, repeating throughout the `Class.ParticleEmitter.Lifetime|Lifetime` of the particle.
 - **Random** &mdash; Play the frames in a random order, blending/crossfading from one frame to the next. This can be useful for organic particle textures at low framerates, such as stars slowly twinkling between subtly different shapes.
+
 </TabItem>
+
 <TabItem label="FlipbookStartRandom">
 The `Class.ParticleEmitter.FlipbookStartRandom|FlipbookStartRandom` property determines whether each particle begins at a random frame of the animation instead of always starting at the first frame. One use case is to enable this property and also set `Class.ParticleEmitter.FlipbookFramerate|FlipbookFramerate` to zero, causing each emitted particle to be a static frame chosen randomly from the flipbook texture.
 </TabItem>