Merge branch 'main' into main

Author: IgnisRBX

content/common/navigation/cloud/reference.yaml

@@ -5,18 +5,18 @@ description: Get comprehensive API reference documentation for Open Cloud.
 
 With Open Cloud, you can access Roblox resources through standard REST APIs, which lets you build everything from command line automation tools to complex web apps. The Open Cloud APIs support HTTPS and use [API keys](./auth/api-keys.md) or [OAuth 2.0](./auth/oauth2-overview.md) for authentication. You can update experiences, restart servers, work with your data stores and memory stores, manage user restrictions, list inventory items, and much, much more.
 
-## About the APIs
+## About this reference
 
-Roblox has four categories of HTTP REST API:
+This reference documentation is broken into two sections:
 
-- Open Cloud v2
-- Open Cloud v1
-- [Legacy with API key and/or OAuth 2.0 authentication](legacy.md)
-- [Legacy with cookie authentication](legacy.md)
+- A [feature-based section](features/accounts.md) that categorizes APIs by use case (Avatars, Game Passes, Users, etc.).
+- A [section that separates endpoints by system](/cloud/reference/DataStore#List-Data-Stores) (Open Cloud v2, v1, or legacy).
 
-Whenever possible, use Open Cloud v2, Open Cloud v1, or legacy endpoints that support API key and/or OAuth 2.0 authentication. These APIs have strong stability guarantees and regularly add new resources.
+**Both sections** contain the full list of available API endpoints; use whichever helps you find what you need.
 
-Legacy API endpoints with cookie authentication can incorporate breaking changes without notice and have minimal stability guarantees. We don't recommend them for production applications.
+Whenever possible, use Open Cloud v2, Open Cloud v1, or [legacy endpoints that support API key and/or OAuth 2.0 authentication](legacy.md). These APIs have strong stability guarantees and regularly add new resources.
+
+Legacy API endpoints with cookie authentication can incorporate breaking changes without notice and have minimal stability guarantees. We don't recommend them for production applications. The legacy API has been known by various names over the years, including the Roblox site API, the web API, and the classic API.
 
 <Alert severity="info">
 Roblox also offers [webhooks](./webhooks/webhook-notifications.md), which can notify your applications when certain events occur, such as refunds or changes to subscriptions.

content/en-us/assets/studio/general/Emulator-Viewport-VR.jpg

@@ -7,7 +7,7 @@ This page covers common patterns with the Open Cloud APIs, particularly around m
 
 ## Paths
 
-To make a request to the Open Cloud APIs, you must first form a URL. This URL is a combination of the base URL (`https://apis.roblox.com/cloud/v2`), the Open Cloud API path (for example, `/universes/{universe-id}/places/{place-id}/user-restrictions`), and any query parameters (for example, `?maxPageSize=25`). A full request URL might look like this:
+To make a request to the Open Cloud APIs, you must first form a URL. This URL is a combination of the base URL (`https://apis.roblox.com/cloud/v2`), the Open Cloud API path (for example, `/universes/{universe_id}/places/{place_id}/user-restrictions`), and any query parameters (for example, `?maxPageSize=25`). A full request URL might look like this:
 
 ```json
 https://apis.roblox.com/cloud/v2/users/4687549151/inventory-items?maxPageSize=100
@@ -17,8 +17,8 @@ Many paths, including the example above, have **path parameters**, designated by
 
 Some resources have multiple path patterns, visible under the **Resource Paths** header in the API reference. For example, the URL for [List User Restrictions](/cloud/reference/UserRestriction#List-User-Restrictions) can be either of the following:
 
-- `https://apis.roblox.com/cloud/cloud/v2/universes/{universe-id}/user-restrictions`
-- `https://apis.roblox.com/cloud/cloud/v2/universes/{universe-id}/places/{place-id}/user-restrictions`
+- `https://apis.roblox.com/cloud/cloud/v2/universes/{universe_id}/user-restrictions`
+- `https://apis.roblox.com/cloud/cloud/v2/universes/{universe_id}/places/{place_id}/user-restrictions`
 
 You can probably infer the difference between the two: some user restrictions apply to an entire universe (experience), whereas others apply to specific places within a universe. Aside from the small addition to the path and extra path parameter, the calls are identical.
 
@@ -34,7 +34,7 @@ If you specify `maxPageSize` in your request, some methods return paginated
 results—essentially partial responses:
 
 ```json
-GET /cloud/v2/users/{userId}/inventory-items?maxPageSize=25
+GET /cloud/v2/users/{user_id}/inventory-items?maxPageSize=25
 
 {
   "inventoryItems": [
@@ -44,12 +44,23 @@ GET /cloud/v2/users/{userId}/inventory-items?maxPageSize=25
 }
 ```
 
+```json
+GET /cloud/v2/universes/{universe_id}/data-stores?maxPageSize=25
+
+{
+  "dataStores": [
+    ...
+  ],
+  "nextPageToken": "datastore1"
+}
+```
+
 If a response includes a value for `nextPageToken`, use that value in the
 `pageToken` parameter of the subsequent request to retrieve the next page. When
-`nextPageToken` is empty, you've reached the end of your results:
+`nextPageToken` is empty or omitted entirely, you've reached the end of your results:
 
 ```json
-GET /cloud/v2/users/{userId}/inventory-items?maxPageSize=25&pageToken=aaaBBB
+GET /cloud/v2/users/{user_id}/inventory-items?maxPageSize=25&pageToken=aaaBBB
 
 {
   "inventoryItems": [
@@ -59,6 +70,16 @@ GET /cloud/v2/users/{userId}/inventory-items?maxPageSize=25&pageToken=aaaBBB
 }
 ```
 
+```json
+GET /cloud/v2/universes/{universe_id}/data-stores?maxPageSize=25&pageToken=datastore1
+
+{
+  "dataStores": [
+    ...
+  ]
+}
+```
+
 Aside from the `pageToken`, you must use the same query for pagination to work
 properly. Altering any filter parameter results in a 400 error.
 

content/en-us/cloud/index.md

@@ -2,7 +2,7 @@
 title: include
 ---
 
-The **Controller Emulator** lets you accurately emulate gamepad input directly in Studio. The default controller is a generic gamepad but you can select alternatives for PlayStation, Xbox, and Quest devices from the upper‑left picker menu.
+The **Controller Emulator** lets you accurately emulate gamepad input directly in Studio. The default controller is a generic gamepad, but you can select alternatives for PlayStation, Xbox, and Quest devices from the upper‑left picker menu.
 
 <img src="../../assets/studio/general/Test-Tab-Emulation-Controllers.png" width="840" alt="Emulate Device Controllers button indicated in Test tab" />
 

content/en-us/cloud/reference/patterns.md

@@ -2,10 +2,10 @@
 title: include
 ---
 
-The **Device Emulator** lets you emulate various devices directly in Studio, providing insight on how controls operate on a mobile device or how [on-screen UI](../../ui/on-screen-containers.md) displays on different screens and aspect ratios.
+The **Device Emulator** lets you emulate various devices directly in Studio, providing insight into how controls work on mobile devices, consoles, and VR headsets, as well as how [on-screen UI](../../ui/on-screen-containers.md) elements display on different screen resolutions and aspect ratios.
 
 <img src="../assets/studio/general/Test-Tab-Emulation-Device.png" width="800" alt="Device button indicated in Test tab" />
 
-In emulation mode, you can select devices from the **device selector** dropdown menu above the 3D viewport to emulate less powerful devices and test [streaming-enabled](../../workspace/streaming.md) experiences where 3D content dynamically loads/unloads based on available memory. You can also adjust the **view&nbsp;size** and change the **orientation** between landscape and portrait modes.
+In emulation mode, you can select devices from the **device selector** dropdown menu above the 3D viewport to emulate less powerful devices and test [streaming-enabled](../../workspace/streaming.md) experiences where 3D content dynamically loads and unloads based on available memory. You can also adjust the **view&nbsp;size** and change the **orientation** between landscape and portrait modes.
 
 <img src="../assets/studio/general/Editor-Window-Emulation-Options.png" width="840" alt="Emulation options above the 3D viewport" />

content/en-us/includes/studio/controller-emulator.md

@@ -280,6 +280,4 @@ end
 
 ## Controller emulation
 
-<BetaAlert betaName="Gamepad Emulator" leadIn="This tool is currently in beta. Enable it through " leadOut="." components={props.components} />
-
 <ControllerEmulator components={props.components} />