npm - @tencent-rtc/mcp - Versions diffs - 1.3.9 → 1.4.0 - Mend

@tencent-rtc/mcp 1.3.9 → 1.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (431) hide show

package/resource/doc/livekit/{live → core-sdk/live}/flutter/live-live-list.md RENAMED Viewed

@@ -1,8 +1,5 @@
 `LiveListStore` is the `AtomicXCore` core module for management of live room list, creation, joining and room status maintenance. With `LiveListStore`, you can build complete lifecycle management for your application.
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032457995/e2538748f6d111f09fbf525400370dda.png)
 ## Core Features
 - **Get live room list**: Obtain the current list of all public live rooms, supporting load by page.
@@ -14,60 +11,22 @@
 - **Custom business data**: Powerful custom metadata (`MetaData`) capacity allows you to store and synchronize any business-relevant information in the room, such as live status, music info, and custom role.
 ## Core Concepts
 Before starting integration, let's learn about several core concepts related to `LiveListStore` in the following table:
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Core Concepts**</td>
-<td rowspan="1" colSpan="1" >**Type**</td>
-<td rowspan="1" colSpan="1" >**Core Responsibilities and Description**</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >[LiveInfo](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveInfo-class.html)</td>
-<td rowspan="1" colSpan="1" >`class`</td>
-<td rowspan="1" colSpan="1" >Represents the information model of a live room. It contains live ID (`liveID`), name (`liveName`), room owner information (`liveOwner`) and custom metadata (`metaData`).</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >[LiveListState](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListState-class.html)</td>
-<td rowspan="1" colSpan="1" >`class`</td>
-<td rowspan="1" colSpan="1" >Represents the current status of the live list module. Its core attribute `liveList` is a `ValueListenable<List<LiveInfo>>` data type, storing the fetched live stream list. `currentLive` represents the live room information where the user currently resides.</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >[LiveListListener](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListListener-class.html)</td>
-<td rowspan="1" colSpan="1" >`class`</td>
-<td rowspan="1" colSpan="1" >Represents the global event listener for a live streaming room. It includes two callbacks, `onLiveEnded` (live streaming end) and `onKickedOutOfLive` (kicked out of live), used to process key room status updates.</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >[LiveListStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html)</td>
-<td rowspan="1" colSpan="1" >`class`</td>
-<td rowspan="1" colSpan="1" >This is the core management class for interaction with the live list and room lifecycle. It is a Global Singleton (`shared`), responsible for all live streaming room operations such as create, join, and information update.</td>
-</tr>
-</table>
+| **Core Concepts** | **Type** | **Core Responsibilities and Description** |
+| --- | --- | --- |
+| [LiveInfo](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveInfo-class.html) | `class` | Represents the information model of a live room. It contains live ID (`liveID`), name (`liveName`), room owner information (`liveOwner`) and custom metadata (`metaData`). |
+| [LiveListState](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListState-class.html) | `class` | Represents the current status of the live list module. Its core attribute `liveList` is a `ValueListenable<List<LiveInfo>>` data type, storing the fetched live stream list. `currentLive` represents the live room information where the user currently resides. |
+| [LiveListListener](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListListener-class.html) | `class` | Represents the global event listener for a live streaming room. It includes two callbacks, `onLiveEnded` (live streaming end) and `onKickedOutOfLive` (kicked out of live), used to process key room status updates. |
+| [LiveListStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html) | `class` | This is the core management class for interaction with the live list and room lifecycle. It is a Global Singleton (`shared`), responsible for all live streaming room operations such as create, join, and information update. |
 ## Implementation Steps
 ### Step 1: Integrating the Component
-- **Live streaming**: Refer to [quick integration](https://write.woa.com/document/200455640177692672) with **AtomicXCore**, and complete the feature implementation for [Anchor starts live streaming](https://write.woa.com/document/200455640177692672) and [audience viewing](https://write.woa.com/document/200455640177692672).
-- **Voice chat room**: Refer to [quick integration](https://write.woa.com/document/200555778169073664) with **AtomicXCore**, and complete the feature implementation for [Anchor starts live streaming](https://write.woa.com/document/200555778169073664) and [audience listening](https://write.woa.com/document/200555778169073664).
+- **Live streaming**: Refer to quick integration with **AtomicXCore**, and complete the feature implementation for Anchor starts live streaming and audience viewing.
+- **Voice chat room**: Refer to quick integration with **AtomicXCore**, and complete the feature implementation for Anchor starts live streaming and audience listening.
 ### Step 2: Audience Entering the Live Room Implementation
@@ -327,80 +286,16 @@ class YourAudiencePage extends StatelessWidget {
 ```
 **LiveInfo Parameter Description**
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter Name**</td>
-<td rowspan="1" colSpan="1" >**Type**</td>
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >`liveID`</td>
-<td rowspan="1" colSpan="1" >`String`</td>
-<td rowspan="1" colSpan="1" >Unique identifier of the live streaming room</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >`liveName`</td>
-<td rowspan="1" colSpan="1" >`String`</td>
-<td rowspan="1" colSpan="1" >Title of the live streaming room</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >`coverURL`</td>
-<td rowspan="1" colSpan="1" >`String`</td>
-<td rowspan="1" colSpan="1" >Thumbnail URL of the live streaming room</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >`liveOwner`</td>
-<td rowspan="1" colSpan="1" >`LiveUserInfo`</td>
-<td rowspan="1" colSpan="1" >Room owner's personal info</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >`totalViewerCount`</td>
-<td rowspan="1" colSpan="1" >`int`</td>
-<td rowspan="1" colSpan="1" >Total viewers in the live streaming room</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >`categoryList`</td>
-<td rowspan="1" colSpan="1" >`List<int>`</td>
-<td rowspan="1" colSpan="1" >Category tag list of the live streaming room</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >`notice`</td>
-<td rowspan="1" colSpan="1" >`String`</td>
-<td rowspan="1" colSpan="1" >Announcement information in the live streaming room</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >`metaData`</td>
-<td rowspan="1" colSpan="1" >`Map<String, String>`</td>
-<td rowspan="1" colSpan="1" >Custom metadata for complex business scenarios</td>
-</tr>
-</table>
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `liveID` | `String` | Unique identifier of the live streaming room |
+| `liveName` | `String` | Title of the live streaming room |
+| `coverURL` | `String` | Thumbnail URL of the live streaming room |
+| `liveOwner` | `LiveUserInfo` | Room owner's personal info |
+| `totalViewerCount` | `int` | Total viewers in the live streaming room |
+| `categoryList` | `List<int>` | Category tag list of the live streaming room |
+| `notice` | `String` | Announcement information in the live streaming room |
+| `metaData` | `Map<String, String>` | Custom metadata for complex business scenarios |
 ## Advanced Features
@@ -408,9 +303,6 @@ class YourAudiencePage extends StatelessWidget {
 On the live square page of the App, the top section features category tags such as "Popular," "Music," and "Gaming." When users click different tags, the live stream list below dynamically filters to show only live streaming rooms of the corresponding category, thereby helping users quickly identify content of interest.
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032457995/e254a211f6d111f09af3525400a31896.png)
 #### Implementation Method
 The core is to use the `categoryList` property in the `LiveInfo` model. When the anchor starts live streaming and sets the category, the `LiveInfo` object returned by `fetchLiveList` will contain this classification information. After your App obtains the complete live list, just perform a simple filter on the client according to the user's selected category, then refresh the UI.
@@ -604,9 +496,6 @@ class _CategoryLiveListPageState extends State<CategoryLiveListPage> {
 In an ecommerce live stream, the Anchor is explaining a product. At this point, a product card pops up at the bottom of the live stream for ALL audience, displaying the product image, name and price in real time. When the Anchor switches to the next product, the card on the client side updates automatically and synchronously.
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032457995/e24959b0f6d111f0b34b525400ecee81.png)
 #### Implementation Method
 The Anchor sets the current product's structured information (recommend using **JSON** format) to a custom key (such as "`product_info`") through the `updateLiveMetaData` API setting. **AtomicXCore** will synchronize this update to ALL audience in real time. The client just needs to subscribe to `LiveListState.currentLive`, listen for changes in `metaData`, and once `product_info` is found updated, parse the JSON data and refresh the product card UI.
@@ -810,40 +699,11 @@ class _ProductCardWidgetState extends State<ProductCardWidget> {
 ## API documentation
 For detailed information about ALL public interfaces, properties and methods of [LiveListStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html) and its related classes, please refer to the official API documentation of the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Flutter/index.html) framework. The related Store used in this document is as follows:
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Store/Component**</td>
-<td rowspan="1" colSpan="1" >**Feature Description**</td>
-<td rowspan="1" colSpan="1" >**API Reference**</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >**LiveCoreWidget**</td>
-<td rowspan="1" colSpan="1" >The core view component for live video stream display and interaction: responsible for video stream rendering and view widget processing, supporting live streaming, audience mic connection, Anchor Connection (TUILiveKit), and other scenarios.</td>
-<td rowspan="1" colSpan="1" >[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreWidget-class.html)</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >**LiveCoreController**</td>
-<td rowspan="1" colSpan="1" >Controller for LiveCoreWidget: used to set up live streaming ID, control preview, and perform other operations.</td>
-<td rowspan="1" colSpan="1" >[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreController-class.html)</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >**LiveListStore**</td>
-<td rowspan="1" colSpan="1" >Full lifecycle management of live streaming room: create/join/leave/terminate room, query room list, modify live information (name, notice), listen to live streaming status (for example being kicked out, ended).</td>
-<td rowspan="1" colSpan="1" >[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html)</td>
-</tr>
-</table>
+| **Store/Component** | **Feature Description** | **API Reference** |
+| --- | --- | --- |
+| **LiveCoreWidget** | The core view component for live video stream display and interaction: responsible for video stream rendering and view widget processing, supporting live streaming, audience mic connection, Anchor Connection (TUILiveKit), and other scenarios. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreWidget-class.html) |
+| **LiveCoreController** | Controller for LiveCoreWidget: used to set up live streaming ID, control preview, and perform other operations. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreController-class.html) |
+| **LiveListStore** | Full lifecycle management of live streaming room: create/join/leave/terminate room, query room list, modify live information (name, notice), listen to live streaming status (for example being kicked out, ended). | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html) |
 ## FAQs
@@ -861,5 +721,3 @@ To ensure system stability and efficiency, the usage of `metaData` follows the f
   - The total size of ALL values in a single room is no more than **16KB**.
 - **Conflict resolution**: The update mechanism for `metaData` is "last write wins". If multiple administrators modify the same key in a short time frame, the last modification will take effect. It is advisable to avoid multiple users simultaneously adjusting the same key information in service design.

package/resource/doc/livekit/{live → core-sdk/live}/ios/live-audience-list.md RENAMED Viewed

@@ -1,8 +1,5 @@
 `LiveAudienceStore` is a module in `AtomicXCore` designed for managing audience information in live streaming rooms. With `LiveAudienceStore`, you can implement a comprehensive audience list and management system for your live streaming application.
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/9013fb14c6b611f087ad52540099c741.png)
 ## Core Features
 - **Real-Time Audience List**: Fetch and display the list of users currently in the room.
@@ -14,72 +11,34 @@
 - **Room Management**: The host or administrator can remove specific viewers from the live room.
 ## Core Concepts
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Core Concept**</td>
-<td rowspan="1" colSpan="1" >**Type**</td>
-<td rowspan="1" colSpan="1" >**Core Responsibilities & Description**</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >`LiveUserInfo`</td>
-<td rowspan="1" colSpan="1" >`class`</td>
-<td rowspan="1" colSpan="1" >- Data model representing a viewer.<br>- Contains basic profile information such as userID, userName, and avatarURL.</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >`LiveAudienceState`</td>
-<td rowspan="1" colSpan="1" >`struct`</td>
-<td rowspan="1" colSpan="1" >- State container for the audience module.<br>- Exposes `audienceList` (StateFlow) for the real-time user list and `audienceCount` for the total viewer count.</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >`LiveAudienceEvent`</td>
-<td rowspan="1" colSpan="1" >`enum`</td>
-<td rowspan="1" colSpan="1" >- Event listener for audience changes.<br>- Provides callbacks like `.onAudienceJoined` and` .onAudienceLeft` to handle incremental list updates.</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >`LiveAudienceStore`</td>
-<td rowspan="1" colSpan="1" >`class`</td>
-<td rowspan="1" colSpan="1" >- Primary interface for audience management.<br>- Used to fetch list snapshots, perform admin operations (e.g., kicking users), and subscribe to real-time events.</td>
-</tr>
-</table>
+| **Core Concept** | **Type** | **Core Responsibilities & Description** |
+| --- | --- | --- |
+| `LiveUserInfo` | `class` | - Data model representing a viewer.<br>- Contains basic profile information such as userID, userName, and avatarURL. |
+| `LiveAudienceState` | `struct` | - State container for the audience module.<br>- Exposes `audienceList` (StateFlow) for the real-time user list and `audienceCount` for the total viewer count. |
+| `LiveAudienceEvent` | `enum` | - Event listener for audience changes.<br>- Provides callbacks like `.onAudienceJoined` and` .onAudienceLeft` to handle incremental list updates. |
+| `LiveAudienceStore` | `class` | - Primary interface for audience management.<br>- Used to fetch list snapshots, perform admin operations (e.g., kicking users), and subscribe to real-time events. |
 ## Implementation
 ### Step 1: Component Integration
-- **Video Live Streaming**: Please refer to [Quick Start](https://write.woa.com/document/194571606121816064) to integrate AtomicXCore.
-- **Voice Chat Room**: Please refer to [Quick Start](https://write.woa.com/document/194571595685527552) to integrate AtomicXCore.
+- **Video Live Streaming**: Please refer to Quick Start to integrate AtomicXCore.
+- **Voice Chat Room**: Please refer to Quick Start to integrate AtomicXCore.
 ### Step 2: Initialize and Retrieve the Audience List
-Get a `LiveAudienceStore` instance linked to the `liveId` and fetch the initial audience snapshot.
+Get a `LiveAudienceStore` instance linked to the `liveId` and fetch the initial audience snapshot.
 ``` swift
 import Foundation
-import AtomicXCore
-import Combine
+import AtomicXCore
+import Combine
 class AudienceManager {
     private let liveId: String
     private let audienceStore: LiveAudienceStore
     private var cancellables = Set<AnyCancellable>()
     // Expose the [full] audience list publisher for UI layer subscription
     let audienceListPublisher = CurrentValueSubject<[LiveUserInfo], Never>([])
     // Expose the audience count publisher
@@ -89,11 +48,11 @@ class AudienceManager {
         self.liveId = liveId
         // 1. Get the LiveAudienceStore instance by liveId
         self.audienceStore = LiveAudienceStore.create(liveID: liveId)
         // 2. Subscribe to state and events
         subscribeToAudienceState()
         subscribeToAudienceEvents()
         // 3. Proactively fetch initial data for the first screen
         fetchInitialAudienceList()
     }
@@ -110,7 +69,7 @@ class AudienceManager {
             }
         }
     }
     // ... subsequent code
 }
 ```
@@ -140,9 +99,9 @@ extension AudienceManager {
             .receive(on: DispatchQueue.main)
             .sink { [weak self] event in
                 guard let self = self else { return }
                 var currentList = self.audienceListPublisher.value
                 switch event {
                 case .onAudienceJoined(let newAudience):
                     print("Audience \(newAudience.userName) joined the live room")
@@ -151,7 +110,7 @@ extension AudienceManager {
                         currentList.append(newAudience)
                         self.audienceListPublisher.send(currentList)
                     }
                 case .onAudienceLeft(let departedAudience):
                     print("Audience \(departedAudience.userName) left the live room")
                     // Incremental update: remove the departed audience member from the current list
@@ -225,32 +184,32 @@ When a new audience member enters the live room, a welcome message is automatica
    ``` swift
    import Foundation
-   import AtomicXCore
+   import AtomicXCore
    import Combine
    class LiveRoomManager {
        private let liveId: String
        private let audienceManager: AudienceManager
        private let barrageManager: BarrageManager // Assume you have implemented BarrageManager as described in the barrage documentation
        private var cancellables = Set<AnyCancellable>()
        init(liveId: String) {
            self.liveId = liveId
            // Initialize two core managers
            self.audienceManager = AudienceManager(liveId: liveId)
            self.barrageManager = BarrageManager(liveId: liveId)
            // Set up linkage
            setupWelcomeMessageFlow()
        }
        private func setupWelcomeMessageFlow() {
            // 1. Get the LiveAudienceStore instance
            let audienceStore = LiveAudienceStore.create(liveID: self.liveId)
            // 2. Get the BarrageStore instance (thanks to internal mechanisms, this will be the same instance)
            let barrageStore = BarrageStore.create(liveID: self.liveId)
            // 3. Subscribe to audience events
            audienceStore.liveAudienceEventPublisher
                .receive(on: DispatchQueue.main)
@@ -259,12 +218,12 @@ When a new audience member enters the live room, a welcome message is automatica
                    guard case .onAudienceJoined(let newAudience) = event else {
                        return
                    }
                    // 5. Create a local tip message
                    var welcomeTip = Barrage()
-                   welcomeTip.messageType = .text
+                   welcomeTip.messageType = .text
                    welcomeTip.textContent = "Welcome \(newAudience.userName) to the live room!"
                    // 6. Call BarrageStore's API to insert it into the barrage list
                    barrageStore.appendLocalTip(message: welcomeTip)
                }
@@ -276,40 +235,11 @@ When a new audience member enters the live room, a welcome message is automatica
 ## API Documentation
 For detailed information on all public interfaces, properties, and methods of [LiveAudienceStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore) and its related classes, refer to the official API documentation included with the [AtomicX Core](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore) framework. The relevant Stores used in this document are as follows:
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Store/Component**</td>
-<td rowspan="1" colSpan="1" >**Feature Description**</td>
-<td rowspan="1" colSpan="1" >**API Documentation**</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >LiveCoreView</td>
-<td rowspan="1" colSpan="1" >Core view component for live video stream display and interaction: responsible for video stream rendering and view widget handling, supporting scenarios such as host streaming, audience co-hosting, and host-to-host connection.</td>
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/livecoreview)</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >LiveAudienceStore</td>
-<td rowspan="1" colSpan="1" >Audience management: obtain real-time audience list (ID / name / avatar), count audience numbers, and listen for audience join/leave events.</td>
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore)</td>
-</tr>
-<tr>
-<td rowspan="1" colSpan="1" >BarrageStore</td>
-<td rowspan="1" colSpan="1" >Barrage feature: send text/custom barrage, maintain barrage list, and listen to barrage status in real time.</td>
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore)</td>
-</tr>
-</table>
+| **Store/Component** | **Feature Description** | **API Documentation** |
+| --- | --- | --- |
+| LiveCoreView | Core view component for live video stream display and interaction: responsible for video stream rendering and view widget handling, supporting scenarios such as host streaming, audience co-hosting, and host-to-host connection. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/livecoreview) |
+| LiveAudienceStore | Audience management: obtain real-time audience list (ID / name / avatar), count audience numbers, and listen for audience join/leave events. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore) |
+| BarrageStore | Barrage feature: send text/custom barrage, maintain barrage list, and listen to barrage status in real time. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore) |
 ## FAQs
@@ -321,19 +251,13 @@ The `audienceCount` is a high-precision estimate. Updates occur based on specifi
 - **Unexpected Disconnection (Delayed)**:If a user disconnects abnormally (e.g., app crash, network loss), the system uses a heartbeat mechanism to verify status. The user is marked offline only after 90 seconds of inactivity, triggering a delayed count update.
 - **Frequency Control & Rate Limiting**: Audience count updates are broadcast as room messages. The system enforces a limit of 40 messages per second per room.
    > **Note：**
-   >
+   >
    > During high-traffic spikes (e.g., chat floods or rapid gifting), if the message rate exceeds this threshold, the system prioritizes core messages (like chat/barrage). Consequently, audience count update messages may be dropped to maintain stability.
-   >
+   >
 - **What does this mean for developers?**
    Treat `audienceCount` as a metric for UI display purposes only. Do not rely on it for billing, critical statistics, or scenarios requiring 100% accuracy, as brief delays or data loss may occur during high-concurrency events.