Merge branch 'main' into patch-4

Author: karl-police

content/common/navigation/engine/reference.yaml

@@ -1183,6 +1183,11 @@ navigation:
         type: engineapi
         source: /reference/engine/classes/HandlesBase.yaml
         ignoreTranslation: true
+      - title: HandRigDescription
+        path: /reference/engine/classes/HandRigDescription
+        type: engineapi
+        source: /reference/engine/classes/HandRigDescription.yaml
+        ignoreTranslation: true
       - title: HapticEffect
         path: /reference/engine/classes/HapticEffect
         type: engineapi
@@ -2933,6 +2938,11 @@ navigation:
         type: engineapi
         source: /reference/engine/classes/VelocityMotor.yaml
         ignoreTranslation: true
+      - title: VideoCapture
+        path: /reference/engine/classes/VideoCapture
+        type: engineapi
+        source: /reference/engine/classes/VideoCapture.yaml
+        ignoreTranslation: true
       - title: VideoCaptureService
         path: /reference/engine/classes/VideoCaptureService
         type: engineapi
@@ -4276,6 +4286,11 @@ navigation:
         type: engineapi
         source: /reference/engine/enums/HandlesStyle.yaml
         ignoreTranslation: true
+      - title: HandRigDescriptionSide
+        path: /reference/engine/enums/HandRigDescriptionSide
+        type: engineapi
+        source: /reference/engine/enums/HandRigDescriptionSide.yaml
+        ignoreTranslation: true
       - title: HapticEffectType
         path: /reference/engine/enums/HapticEffectType
         type: engineapi
@@ -4631,6 +4646,11 @@ navigation:
         type: engineapi
         source: /reference/engine/enums/NameOcclusion.yaml
         ignoreTranslation: true
+      - title: NegateOperationHiddenHistory
+        path: /reference/engine/enums/NegateOperationHiddenHistory
+        type: engineapi
+        source: /reference/engine/enums/NegateOperationHiddenHistory.yaml
+        ignoreTranslation: true
       - title: NetworkOwnership
         path: /reference/engine/enums/NetworkOwnership
         type: engineapi

content/en-us/art/characters/export-avatar-animations-from-maya.md

@@ -11,7 +11,7 @@ description: Explains the process for exporting avatar animations from Maya.
     <figcaption>R15 mannequin reference</figcaption>
   </figure>
   <figure>
-    <video controls src="../../assets/animation/exporting-avatar-animations-from-maya/Moving-Rig.mp4" alt="An angled side view of the same humnoid mannequin walking in place." width="40%"></video>
+    <video controls src="../../assets/animation/exporting-avatar-animations-from-maya/Moving-Rig.mp4" alt="An angled side view of the same humanoid mannequin walking in place." width="40%"></video>
     <figcaption>Example walking animation</figcaption>
   </figure>
 </GridContainer>
@@ -89,7 +89,7 @@ To export your avatar animation from Maya:
    1. In the menu bar, click **Windows**. A contextual menu displays.
    1. Hover over **Settings/Preferences**, then click **Plug-in Manager**. The **Plug-in Manager** window displays.
 
-      <img width="80%" img src="../../assets/animation/exporting-avatar-animations-from-maya/Plugin-Manager.jpg" alt="A close up view of the Windows dropdown menu in Maya. The Settings/Preferences menu item is highlighted, as well as the Plguin-in Manager submenu." />
+      <img width="80%" img src="../../assets/animation/exporting-avatar-animations-from-maya/Plugin-Manager.jpg" alt="A close up view of the Windows dropdown menu in Maya. The Settings/Preferences menu item is highlighted, as well as the Plug-in Manager submenu." />
 
    1. In the search field, input **fbxmaya**. The **fbxmaya.mll** plugin displays.
    1. Enable the **Loaded** and **Auto load** options.

content/en-us/assets/studio/general/Studio-Logo-Blue.png

@@ -327,6 +327,8 @@ Each queue has a limit of 30 requests. When the limit of a queue is reached, req
 <Tabs>
 <TabItem label="Server limits">
   Each server is allowed a certain number of data store requests based on the request type and number of users. Use `Class.DataStoreService:GetRequestBudgetForRequestType()|GetRequestBudgetForRequestType()` to confirm the number of data store requests that the current place can make.
+  
+  For each request type, the limit is shared among all listed functions.
 
   <table>
   <thead>
@@ -343,7 +345,7 @@ Each queue has a limit of 30 requests. When the limit of a queue is reached, req
       <td>60 + numPlayers × 10</td>
     </tr>
     <tr>
-      <td><b>Set</b> (limit is shared among all listed functions)</td>
+      <td><b>Set</b></td>
       <td>`Class.GlobalDataStore:SetAsync()|SetAsync()`<br></br>`Class.GlobalDataStore:IncrementAsync()|IncrementAsync()`<br></br>`Class.GlobalDataStore:UpdateAsync()|UpdateAsync()`<br></br>`Class.GlobalDataStore:RemoveAsync()|RemoveAsync()`</td>
       <td>60 + numPlayers × 10</td>
     </tr>

content/en-us/cloud-services/data-stores/error-codes-and-limits.md

@@ -211,7 +211,7 @@ At the end of the transition, remaining players will be removed from the arena,
 
 When players move into the transition state, remove their weapons.
 
-1. In PlayerManager, find the local functions. Copy and paste the highlighted code for `removePlayerWeapon()` below. The code will remove an individual player's weapon if it's actively equipt or in the player's backpack.
+1. In PlayerManager, find the local functions. Copy and paste the highlighted code for `removePlayerWeapon()` below. The code will remove an individual player's weapon if it's actively equipped or in the player's backpack.
 
    ```lua
    local function removePlayerWeapon(whichPlayer)
@@ -227,7 +227,7 @@ When players move into the transition state, remove their weapons.
        end
 
        -- If the player has the weapon in their backpack
-       local backpackWeapon = whichPlayer.Backpack:FindFirstChild("Weapon") 
+       local backpackWeapon = whichPlayer.Backpack:FindFirstChild("Weapon")
 
        if backpackWeapon then
          backpackWeapon:Destroy()
@@ -288,7 +288,7 @@ Cleanup will be its own function in MatchManager. For now, cleanup will just use
      repeat
        task.wait(gameSettings.intermissionDuration)
      until #Players:GetPlayers() >= gameSettings.minimumPlayers
-     
+
      displayManager.updateStatus("Get ready!")
      task.wait(gameSettings.transitionTime)
 
@@ -371,25 +371,25 @@ First, start a function to send players back to the lobby.
 
    ```lua
    while true do
-   	displayManager.updateStatus("Waiting for Players")
+     displayManager.updateStatus("Waiting for Players")
 
-   	repeat
-   		task.wait(gameSettings.intermissionDuration)
-   	until #Players:GetPlayers() >= gameSettings.minimumPlayers
+     repeat
+       task.wait(gameSettings.intermissionDuration)
+     until #Players:GetPlayers() >= gameSettings.minimumPlayers
 
-		displayManager.updateStatus("Get ready!")
-		task.wait(gameSettings.transitionTime)
+     displayManager.updateStatus("Get ready!")
+     task.wait(gameSettings.transitionTime)
 
-		matchManager.prepareGame()
-		local endState = matchEnd.Event:Wait()
+     matchManager.prepareGame()
+     local endState = matchEnd.Event:Wait()
 
-		local endStatus = matchManager.getEndStatus(endState)
-		displayManager.updateStatus(endStatus)
+     local endStatus = matchManager.getEndStatus(endState)
+     displayManager.updateStatus(endStatus)
 
-		matchManager.cleanupMatch()
-		task.wait(gameSettings.transitionTime)
+     matchManager.cleanupMatch()
+     task.wait(gameSettings.transitionTime)
 
-		matchManager.resetMatch()
+     matchManager.resetMatch()
    end
    ```
 
@@ -614,7 +614,7 @@ local function removePlayerWeapon(whichPlayer)
 		end
 
 		-- If the player has the weapon in their backpack
-		local backpackWeapon = whichPlayer.Backpack:FindFirstChild("Weapon") 
+		local backpackWeapon = whichPlayer.Backpack:FindFirstChild("Weapon")
 
 		if backpackWeapon then
 			backpackWeapon:Destroy()

content/en-us/education/battle-royale-series/cleanup-and-reset.md

@@ -7,7 +7,7 @@ Designing for performance means following a handful of best practices **as you b
 
 ## Low-end devices
 
-Lower-end devices, particularly mobile devices, have severe memory limitations and are succeptible to crashes due to out of memory (OOM) errors:
+Lower-end devices, particularly mobile devices, have severe memory limitations and are susceptible to crashes due to out of memory (OOM) errors:
 
 - If you want to support lower-end devices, choose at least one "baseline" device, test your experience on it throughout the development process, and pay close attention to frame rate and memory usage. As you find problem areas in your experience, use those areas to identify the limits of your device.
 

content/en-us/performance-optimization/design.md

@@ -5,133 +5,159 @@ description: Mechanical constraints behave as conceptual mechanical connections
 
 The physics engine includes the following `Class.Constraint|Constraints` that behave as conceptual mechanical connections, including hinges, springs, ropes, and more. In addition, various [mover constraints](../physics/mover-constraints.md) are available to exert directional or rotational force upon [assemblies](../physics/assemblies.md).
 
-<GridContainer numColumns="2">
+<Grid container spacing={4}>
 
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/ball-socket.md" size="large" color="primaryBrand" variant="outlined" fullWidth>Ball Socket</Button>
+<Button href="../physics/constraints/ball-socket.md" size="large" variant="contained" fullWidth>Ball Socket</Button>
 <p></p>
 <CardMedia component="video" controls src="../assets/physics/constraints/BallInSocket-Demo.mp4" />
 <p></p>
 <figcaption>[BallSocketConstraint](../physics/constraints/ball-socket.md) forces its two attachments into the same position and allows them to freely rotate about all three axes, with optional limits to restrict both tilt and twist</figcaption>
 </CardContent>
 </Card>
+</Grid>
 
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/hinge.md" size="large" color="primaryBrand" variant="outlined" fullWidth>Hinge</Button>
+<Button href="../physics/constraints/hinge.md" size="large" variant="contained" fullWidth>Hinge</Button>
 <p></p>
 <CardMedia component="video" controls src="../assets/physics/constraints/Hinge-Demo.mp4" />
 <p></p>
 <figcaption>[HingeConstraint](../physics/constraints/hinge.md) allows its two attachments to rotate about one axis, with optional assigned power for motor or servo behavior</figcaption>
 </CardContent>
 </Card>
+</Grid>
 
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/prismatic.md" size="large" color="primaryBrand" variant="outlined" fullWidth>Prismatic</Button>
+<Button href="../physics/constraints/prismatic.md" size="large" variant="contained" fullWidth>Prismatic</Button>
 <p></p>
 <CardMedia component="video" controls src="../assets/physics/constraints/Prismatic-Demo.mp4" />
 <p></p>
 <figcaption>[PrismaticConstraint](../physics/constraints/prismatic.md) allows two attachments to slide along one axis but not rotate, with optional assigned power for mechanisms like sliding doors and elevator platforms</figcaption>
 </CardContent>
 </Card>
+</Grid>
 
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/cylindrical.md" size="large" color="primaryBrand" variant="outlined" fullWidth>Cylindrical</Button>
+<Button href="../physics/constraints/cylindrical.md" size="large" variant="contained" fullWidth>Cylindrical</Button>
 <p></p>
 <CardMedia component="video" controls src="../assets/physics/constraints/Cylindrical-Demo.mp4" />
 <p></p>
 <figcaption>[CylindricalConstraint](../physics/constraints/cylindrical.md) allows its attachments to slide along one axis and rotate about another axis, with optional assigned angular and/or linear power</figcaption>
 </CardContent>
 </Card>
+</Grid>
 
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/spring.md" size="large" color="primaryBrand" variant="outlined" fullWidth>Spring</Button>
+<Button href="../physics/constraints/spring.md" size="large" variant="contained" fullWidth>Spring</Button>
 <p></p>
 <CardMedia component="video" controls src="../assets/physics/constraints/Spring-Demo.mp4" />
 <p></p>
 <figcaption>[SpringConstraint](../physics/constraints/spring.md) applies a force on its attachments based on spring and damper behavior, with an optional minimum/maximum length</figcaption>
 </CardContent>
 </Card>
-  
+</Grid>
+
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/torsion-spring.md" size="large" color="primaryBrand" variant="outlined" fullWidth>Torsion Spring</Button>
+<Button href="../physics/constraints/torsion-spring.md" size="large" variant="contained" fullWidth>Torsion Spring</Button>
 <p></p>
 <CardMedia component="video" controls src="../assets/physics/constraints/TorsionSpring-Demo.mp4" />
 <p></p>
 <figcaption>[TorsionSpringConstraint](../physics/constraints/torsion-spring.md) applies torque based on a relative angle and relative angular velocity, in an attempt to bring two axes from two parts together</figcaption>
 </CardContent>
 </Card>
-  
+</Grid>
+
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/universal.md" size="large" color="primaryBrand" variant="outlined" fullWidth>Universal</Button>
+<Button href="../physics/constraints/universal.md" size="large" variant="contained" fullWidth>Universal</Button>
 <p></p>
 <CardMedia component="video" controls src="../assets/physics/constraints/Universal-Demo.mp4" />
 <p></p>
 <figcaption>[UniversalConstraint](../physics/constraints/universal.md) ensures two axes on two assemblies remain perpendicular, useful for applications such as vehicle power transmission to rear drive shafts, robotics, and more</figcaption>
 </CardContent>
 </Card>
+</Grid>
 
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/rope.md" size="large" color="primaryBrand" variant="outlined" fullWidth>Rope</Button>
+<Button href="../physics/constraints/rope.md" size="large" variant="contained" fullWidth>Rope</Button>
 <p></p>
 <CardMedia component="video" controls src="../assets/physics/constraints/Rope-Demo.mp4" />
 <p></p>
 <figcaption>[RopeConstraint](../physics/constraints/rope.md) prevents two attachments from separating further than a defined length, with optional behavior as an extending or contracting winch</figcaption>
 </CardContent>
 </Card>
+</Grid>
 
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/rod.md" size="large" color="primaryBrand" variant="outlined" fullWidth>Rod</Button>
+<Button href="../physics/constraints/rod.md" size="large" variant="contained" fullWidth>Rod</Button>
 <p></p>
 <CardMedia component="video" controls src="../assets/physics/constraints/Rod-Demo.mp4" />
 <p></p>
 <figcaption>[RodConstraint](../physics/constraints/rod.md) keeps two attachments separated by a defined length, with optional limits on rotational tilt</figcaption>
 </CardContent>
 </Card>
+</Grid>
 
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/plane.md" size="large" color="primaryBrand" variant="outlined" fullWidth>Plane</Button>
+<Button href="../physics/constraints/plane.md" size="large" variant="contained" fullWidth>Plane</Button>
 <p></p>
 <CardMedia component="video" controls src="../assets/physics/constraints/Plane-Demo.mp4" />
 <p></p>
 <figcaption>[PlaneConstraint](../physics/constraints/plane.md) moves two attachments into a position/orientation along a plane, and both attachments remain free to translate and rotate unless otherwise constrained</figcaption>
 </CardContent>
 </Card>
+</Grid>
 
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/weld.md" size="large" color="primaryBrand" variant="outlined" fullWidth>Weld</Button>
+<Button href="../physics/constraints/weld.md" size="large" variant="contained" fullWidth>Weld</Button>
 <p></p>
 <figcaption>[WeldConstraint](../physics/constraints/weld.md) connects two `Class.BasePart|BaseParts` and ensures they stay in the same relative position and orientation to each other, even if they are not touching</figcaption>
 </CardContent>
 </Card>
+</Grid>
 
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/rigid.md" size="large" color="primaryBrand" variant="outlined" fullWidth>Rigid</Button>
+<Button href="../physics/constraints/rigid.md" size="large" variant="contained" fullWidth>Rigid</Button>
 <p></p>
 <figcaption>[RigidConstraint](../physics/constraints/rigid.md) connects two `Class.Attachment|Attachments` or `Class.Bone|Bones` and ensures they stay in the same relative position/orientation to each other, even if they are not touching</figcaption>
 </CardContent>
 </Card>
+</Grid>
 
+<Grid item XSmall={12} Small={6} Medium={6} Large={6}>
 <Card variant="outlined" style={{height: '100%'}}>
 <CardContent>
-<Button href="../physics/constraints/no-collision.md" size="large" color="primaryBrand" variant="outlined" fullWidth>No Collision</Button>
+<Button href="../physics/constraints/no-collision.md" size="large" variant="contained" fullWidth>No Collision</Button>
 <p></p>
 <figcaption>[NoCollisionConstraint](../physics/constraints/no-collision.md) prevents collisions between two specific parts, but those parts may still register collisions with the rest of the world</figcaption>
 </CardContent>
 </Card>
+</Grid>
 
-</GridContainer>
+</Grid>
 
 ## Constraint visualization