Merge branch 'main' into RDC-RIA-2025-END

Author: IgnisRBX

content/common/navigation/cloud/reference.yaml

@@ -93,6 +93,14 @@ navigation:
     path: /cloud/features/user-profiles
   - title: Users
     path: /cloud/features/users
+  - title: '' # doesn't show anywhere
+    path: /cloud/features-revamp/
+    type: cloudfeature
+    source: /reference/cloud/openapi.json
+  - title: '' # doesn't show anywhere
+    path: /cloud/domains/
+    type: clouddomain
+    source: /reference/cloud/openapi.json
   - heading: Open Cloud API Reference
   - title: Cloud
     section:

content/common/navigation/engine/tutorials.yaml

@@ -127,6 +127,8 @@ navigation:
     section:
       - title: Save player data
         path: /tutorials/use-case-tutorials/data-storage/save-player-data
+      - title: Create a custom leaderboard
+        path: /tutorials/use-case-tutorials/data-storage/create-leaderboard
   - heading: Advanced paths
   - title: Overview
     path: /tutorials/curriculums/curriculum-overview

content/common/navigation/scale/discovery.yaml

@@ -24,6 +24,3 @@ navigation:
     path: /production/promotion/social-media-links
   - title: Share links
     path: /production/promotion/share-links
-  - title: Get featured on Roblox‑owned channels
-    path: /production/promotion/get-featured-on-roblox-owned-channels
-

content/common/navigation/scale/overview.yaml

@@ -5,8 +5,6 @@ navigation:
 - heading: Experience discovery
 - title: How it works
   path: /discovery
-- title: Get featured
-  path: /production/promotion/get-featured-on-roblox-owned-channels
 - title: Ads
   path: /production/promotion/ads-manager
 - heading: Localization

content/en-us/assets/tutorials/data-storage/DataStoreTutorial2.png

@@ -90,19 +90,21 @@ After you add the webhook, use it to configure the bot with the following steps:
 
 <TabItem label="Discord">
 
+Check out Discord's [documentation](https://discord.com/developers/docs/topics/oauth2#bot-vs-user-accounts) for latest instructions.
+
 1. Navigate to the [Applications page](https://discord.com/developers/applications).
 1. Create a new application and name it to `GDPR Bot`.
 1. The system redirects you to the **General Information** settings of the bot. Copy and save its application ID in a secure place.
 1. Under the settings menu, select **OAuth2**.
-1. Under the **Default Authorization Link** section, expand the **Authorization Method** dropdown and select **In-app Authorization**.
-1. Add the **bot** scope and the **Administrator** permission. Save your changes.
-1. Under the **OAuth2** settings, select the **URL Generator** subcategory.
-1. Select the **bot** scope and the **Administrator** permission.
+1. Navigate to the **OAuth2** settings
+   1. Enable the **bot** scope, a list of additional Bot Permissions displays.
+   2. Add the **Administrator** permission. Save your changes.
+   3. Save the generated URL.
 1. Copy the generated URL. Leave the application settings page unclosed.
 1. Navigate to the generated URL. Select the target server. Click the **Continue** button and then the **Authorize** button.
-1. Navigate back to application settings page of your bot. Under the settings menu, select **bot**.
+1. Navigate back to application settings page and navigate to the Bot settings.
 1. Under the **Privileged Gateway Intents** section, enable **Message Content Intent**.
-1. Under the **Build-A-Bot** section, save the bot token in a secure place for later steps. If you don't see the token, click the **Reset Token** button to generate a new one.
+1. In the Bot settings > **Build-A-Bot** section, save the bot token in a secure place for later steps. If you don't see the token, click the **Reset Token** button to generate a new one.
 
 </TabItem>
 </Tabs>

content/en-us/cloud/webhooks/automate-right-to-erasure.md

@@ -5,7 +5,7 @@ description: Inspire is an annual global online event where creators come togeth
 
 Inspire is an annual global online event where creators come together to exchange ideas, learn from workshops led by top creators, and collaborate to boost connections within the community. By participating, you can share your knowledge and host workshops for the broader creator community.
 
-See [Roblox Learn](https://www.youtube.com/@RobloxLearn) for content from Inspire 2024.
+See [Roblox Learn](https://www.youtube.com/@RobloxLearn/streams) for content from Inspire 2025.
 
 <figure>
 <Chip

content/en-us/creator-programs/inspire.md

@@ -396,21 +396,21 @@ Particle flipbook textures let you animate a particle's texture over its lifetim
 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.
 
 <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>
+	<figure>
+		<Alert severity="success">
+		<AlertTitle style={{paddingBottom: '8px'}}>Compatible flipbook texture size</AlertTitle>
+		An example compatible texture is 1024&times;1024 in size with a `Enum.ParticleFlipbookLayout.Grid4x4|Grid4x4` layout, since the texture's dimensions are divisible by 4 and each frame becomes 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.
+		</Alert>
+	</figure>
+	<figure>
+		<Alert severity="error">
+		<AlertTitle style={{paddingBottom: '8px'}}>Incompatible flipbook texture size</AlertTitle>
+		An example incompatible texture is 100&times;100 in size with a `Enum.ParticleFlipbookLayout.Grid8x8|Grid8x8` layout, since the texture's dimensions are not evenly divisible by 8 and 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 evenly divisible by 10.
+		</Alert>
+	</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.
+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" />
 
@@ -428,7 +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`.
+- **Custom** &mdash; 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:
 

content/en-us/effects/particle-emitters.md

@@ -220,16 +220,20 @@ To access your rewarded video ad metrics:
     <td>The number of rewards granted for video ad views in your experience. <br /><br /> Different lines show you this metric for different ad placements inside the experience.</td>
   </tr>
   <tr>
-    <td>**DUV (Daily Unique Views)**</td>
+    <td>**DUV (Daily Unique Viewers)**</td>
     <td>The number of unique users who have viewed one or more video ads in your experience in a day. A view is defined by an impression. <br /><br /> This data is updated with 1 day delay.</td>
   </tr>
   <tr>
     <td>**AEPDUV (Average Earnings Per Daily Uniquer Viewers)**</td>
     <td>The earnings generated per daily unique viewer for rewarded video ads. <br /><br /> This data is updated with 1 day delay.</td>
   </tr>
   <tr>
-    <td>**DUV/DAU (Daily Unique Views/Daily Active Users)**</td>
-    <td>The percentage of unique users who have viewed a video ad in a day divided by the total number of users who joined your experience that day. <br /><br /> This data is updated with 1 day delay.</td>
+    <td>**Eligible Daily Active Users**</td>
+    <td>The number of unique daily visitors to your experience who were eligible to see Rewarded Video ads. <br /><br /> This data is updated with 1 day delay.</td>
+  </tr>
+  <tr>
+    <td>**DUV/eDAU (Daily Unique Viewers/Eligible Daily Active Users)**</td>
+    <td>The percent of ads eligible visitors to your experience, known as Eligible Daily Active Users, who saw at least one ad on a day. <br /><br /> This data is updated with 1 day delay.</td>
   </tr>
 </tbody>
 </table>