update Open Source Docs from Roblox internal teams

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

content/en-us/characters/pathfinding.md

@@ -21,6 +21,22 @@ With **Pathfinding modifiers** enabled, text labels indicate specific materials
 
 <img src="../assets/avatar/pathfinding/Navigation-Labels.jpg" width="800" alt="Navigation labels showing on navigation mesh" />
 
+## Known Limitations
+
+Pathfinding features specific limitations to ensure efficient processing and optimal performance.
+
+### Vertical Placement Limit
+
+Pathfinding calculations consider only parts within certain vertical boundaries:
+
+- Lower Boundary &mdash; Parts with a bottom **Y** coordinate less than -65,536 studs are ignored.
+- Upper Boundary &mdash; Parts with a top **Y** coordinate exceeding 65,536 studs are ignored.
+- Vertical Span &mdash; The vertical distance from the lowest part's bottom **Y** coordinate to the highest part's top **Y** coordinate must not exceed 65,536 studs; otherwise, the pathfinding system will ignore those parts during the pathfinding computation.
+
+### Search Distance Limitation
+
+The direct line-of-sight distance for pathfinding from the start to the finish point must not exceed 3,000 studs. Exceeding this distance will result in a `Enum.PathStatus|NoPath` status.
+
 ## Creating Paths
 
 Pathfinding is initiated through `Class.PathfindingService` and its `Class.PathfindingService:CreatePath()|CreatePath()` function.

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

@@ -423,11 +423,11 @@ same `MeshId` are handled in a single draw call when:
     <td>Light grid and shadow updates</td>
   </tr>
   <tr>
-    <td>Update LightGrid</td>
+    <td>LightGridCPU</td>
     <td>Voxel light grid updates</td>
   </tr>
   <tr>
-    <td>Shadows</td>
+    <td>ShadowMapSystem</td>
     <td>Shadow mapping</td>
   </tr>
   <tr>

content/en-us/production/analytics/custom-events.md

@@ -15,6 +15,10 @@ Once your experience begins tracking custom events, you'll unlock the Custom pag
 
 To unlock the Custom Events dashboard, you must first track custom events in your experience. Start by identifying which metrics are the most important for monitoring and improving your experience. Events are aggregated daily so it may take up to 24 hours for charts to populate on the page.
 
+<Alert severity ='warning'>
+Events can only be sent from the server and in published experiences. Events can't be sent from the client or Studio.
+</Alert>
+
 ### Counters
 
 Counters are one-time events captured without a value. You can use counters for tracking the number of times a specific event has occurred. Use counters for single actions such as clicking a button, starting a quest, or using a tool.
@@ -71,6 +75,10 @@ You can breakdown by custom fields by using the breakdown selector.
 
 <img src="../../assets/analytics/event-types/Custom-Event-Breakdown.png" width = "40%" alt="A dropdown indicating the three custom fields you can compare across, along with standard breakdowns like age, gender, operating system and more."/>
 
+You should use custom fields whenever possible instead of event names, since there is a much tighter cardinality limit on event names than custom fields. Using custom fields also allows you to see visualizations of events across field values.
+
+For example, instead of `PlantCabbage`, `PlantTurnip`, `PlantPepper` as three separate events, you could have a single event with the name `PlantSeed` and custom field values `Plant - Cabbage`, `Plant - Turnip`, and `Plant - Pepper`. This way you can visualize both the total number of seeds planted as well as compare each plant in the same visualization. This also reduces your event name cardinality.
+
 For more information, see [custom fields](./custom-fields.md).
 
 ## Using Custom Events to Grow Your Experience

content/en-us/production/analytics/custom-fields.md

@@ -9,7 +9,7 @@ You can use up to 3 **custom fields** to filter your [Economy](./economy-events.
 - Player class — Warrior, Mage, Archer
 - Weapon type — SMG, Pistol, Rocket Launcher
 
-The `customFields` parameter is a dictionary argument that allows sending up to three custom values using the provided `Enum.AnalyticsCustomFieldKeys` as keys. You can have up to 8,000 unique combinations of values across the three custom fields.
+The customFields parameter is a dictionary argument that allows sending up to three custom values using the provided `Enum.AnalyticsCustomFieldKeys` as keys by accessing them as `Enum.AnalyticsCustomFieldKeys.CustomField{01, 02, 03}.Name`. Anything other than `CustomField01.Name`, `CustomField02.Name`, and `CustomField03.Name` is ignored. You can have up to 8,000 unique combinations of values across the three custom fields.
 
 Using a fantasy-related experience as an example, you can track an economy event regarding equipment type, player class, and level with the following:
 

content/en-us/production/analytics/economy-events.md

@@ -15,6 +15,10 @@ Once your experience begins tracking Economy events, you'll unlock the Economy p
 
 To unlock the Economy dashboard, you need to track some economy events in your experience. Start by identifying where users **source** (i.e. gain) and **sink** (i.e. spend) resources in your experience. These are represented in code by `Enum.AnalyticsEconomyFlowType`, which can be either `Source` or `Sink`.
 
+<Alert severity ='warning'>
+Events can only be sent from the server and in published experiences. Events can't be sent from the client or Studio.
+</Alert>
+
 ### Transaction Types
 
 Each source and sink event requires a transaction type, encoded with `Enum.AnalyticsEconomyTransactionType`. By default, the options are:

content/en-us/production/analytics/funnel-events.md

@@ -15,6 +15,10 @@ Once your experience begins tracking Funnel events, you'll unlock the Funnel pag
 
 To track funnel events, first identify the most important funnels in your experience and segment them into steps. Your onboarding flow is a great place to start, as this is where you may be losing most of your users.
 
+<Alert severity ='warning'>
+Events can only be sent from the server and in published experiences. Events can't be sent from the client or Studio.
+</Alert>
+
 ### Tracking One-Time Funnels
 
 A one-time funnel monitors conversion events that only occur once per user.

content/en-us/studio/microprofiler/tag-table.md

@@ -221,28 +221,31 @@ The following is a list of common tags in the MicroProfiler, grouped by category
   </tr>
   <tr>
     <td>Perform/Scene/computeLightingPerform/LightGridCPU</td>
-    <td>Updates the voxel lighting. Lights are only rendered in Voxel Lighting mode, but occupancy and sky light are computed in all lighting modes.</td>
-    <td>If updating chunk occupancy takes too long, consider using lower resolution geometry, or reducing the number of parts. If the other sub-markers take too long, consider reducing the number of lights. Consider using non-shadow casting geometry for objects that move and invalidate the occupancy.</td>
+    <td>Updates the voxel lighting, which is used in `Enum.Technology|Voxel` and `Enum.Technology|ShadowMap` modes and at quality levels below 4 in `Enum.Technology|Future` mode.</td>
+    <td>If updating chunk occupancy takes too long, consider using lower resolution geometry, reducing the number of parts, or anchoring parts. If the other sub-markers take too long, consider reducing the number of lights and using non-shadow casting geometry for objects that move and invalidate the occupancy.</td>
   </tr>
-{/*
   <tr>
     <td>Perform/Scene/computeLightingPerform/ShadowMapSystem</td>
-    <td>-- TODO</td>
-    <td>-- TODO</td>
+    <td>Updates shadow maps. Not performed at quality levels below 4 or when `Class.Lighting.Technology` is set to `Enum.Technology|Voxel`.</td>
+    <td>If lighting is set to `Enum.Technology|Future`, lower it to `Enum.Technology|ShadowMap` or reduce the number of lights. You can also use `Class.Light.Shadows` and `Class.BasePart.CastShadows` to disable shadow casting on less important instances. See [Improving Performance](../../performance-optimization/improving.md#mitigation-4).</td>
   </tr>
-*/}
   <tr>
   </tr>
   <tr>
     <td>Perform/Scene/Glow, ColorCorrection, MSAA, SSAO, and SSAOApply</td>
     <td>Post-processing rendering.</td>
-    <td>Reduce the number of post-processing effects, usually this is not significant.</td>
+    <td>Reduce the number of post-processing effects. Usually this is not significant.</td>
   </tr>
   <tr>
     <td>Perform/Scene/UI</td>
     <td>UI rendering. In Id_Screen, there is a label with the number of batches, materials and triangles used.</td>
     <td>Reduce the number of visible UI elements. Using `CanvasGroups` may help at the expense of increased memory use.</td>
   </tr>
+  <tr>
+    <td>Perform/Scene/UpdateView/updateParticles, updateParticleBoundings</td>
+    <td>Update particle position and bounds.</td>
+    <td>Reduce the number of `Class.ParticleEmitter|ParticleEmitters`, emission rates, lifetimes, etc. Limit the movement of emitters.</td>
+  </tr>
   <tr>
     <td>Id_Opaque</td>
     <td>Parts in the scene with a transparency value of 0.</td>