@tencent-rtc/mcp 1.3.9 → 1.4.1

package/resource/doc/livekit/{live → core-sdk/live}/android/live-audio-effect.md

@@ -1,8 +1,5 @@
 This document provides guidance on integrating audio effect controls into your live streaming application using the `AudioEffectStore` and `DeviceStore` modules from the **AtomicXCore** framework. These modules enable features such as microphone volume control, ear monitoring, and a variety of voice changing and reverb effects.
 
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/db216561c6bc11f0a7775254005ef0f7.png)
-
-
 ## Core Features
 
 By combining `AudioEffectStore` and DeviceStore, you can implement the following core features:
@@ -14,74 +11,22 @@ By combining `AudioEffectStore` and DeviceStore, you can implement the following
 
 - **Reverb Effects**: Simulate different acoustic environments, such as KTV, metallic, deep, bright, and others.
 
-
 ## 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 Responsibility & Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`AudioChangerType`</td>
-
-<td rowspan="1" colSpan="1" >`enum`</td>
-
-<td rowspan="1" colSpan="1" >Enumerates available voice effects, such as "child", "man", etc.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`AudioReverbType`</td>
-
-<td rowspan="1" colSpan="1" >`enum`</td>
-
-<td rowspan="1" colSpan="1" >Enumerates available reverb effects, such as "ktv", "hall", etc.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`AudioEffectState`</td>
-
-<td rowspan="1" colSpan="1" >`data`</td>
-
-<td rowspan="1" colSpan="1" >Represents the current state of the audio effect module, typically used for UI rendering. Includes voice effect state, reverb state, ear monitoring enabled state, and ear monitor volume.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`AudioEffectStore`</td>
-
-<td rowspan="1" colSpan="1" >`abstract`</td>
-
-<td rowspan="1" colSpan="1" >Singleton data management class for audio effects. Use it to invoke audio effect APIs. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`DeviceState`</td>
-
-<td rowspan="1" colSpan="1" >`data`</td>
-
-<td rowspan="1" colSpan="1" >Represents the current state of the device module, typically used for UI rendering. Core properties include camera and microphone status.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`DeviceStore`</td>
-
-<td rowspan="1" colSpan="1" >`abstract`</td>
-
-<td rowspan="1" colSpan="1" >Singleton data management class for device operations. Use it to control the camera and microphone. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates.</td>
-</tr>
-</table>
-
+| **Core Concept** | **Type** | **Core Responsibility & Description** |
+| --- | --- | --- |
+| `AudioChangerType` | `enum` | Enumerates available voice effects, such as "child", "man", etc. |
+| `AudioReverbType` | `enum` | Enumerates available reverb effects, such as "ktv", "hall", etc. |
+| `AudioEffectState` | `data` | Represents the current state of the audio effect module, typically used for UI rendering. Includes voice effect state, reverb state, ear monitoring enabled state, and ear monitor volume. |
+| `AudioEffectStore` | `abstract` | Singleton data management class for audio effects. Use it to invoke audio effect APIs. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates. |
+| `DeviceState` | `data` | Represents the current state of the device module, typically used for UI rendering. Core properties include camera and microphone status. |
+| `DeviceStore` | `abstract` | Singleton data management class for device operations. Use it to control the camera and microphone. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates. |
 
 ## Implementation
 
 ### Step 1: Component Integration
-- **Video Live Streaming**: Please refer to [Quick Start](https://write.woa.com/document/194571606056804352) to integrate **AtomicXCore.**
-
-- **Voice Chat Room**: Please refer to [Quick Start](https://write.woa.com/document/194571595678187521) 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: Obtain Store Instances
 
@@ -99,8 +44,7 @@ val deviceStore = DeviceStore.shared()
 Ear monitoring allows users to hear their own microphone audio in real time. Manage ear monitoring using the following APIs.
 
 > **Note：**Ear monitoring typically requires headphones to function properly.
-> 
-
+>
 
 #### Implementation
 1. **Toggle Ear Monitoring**: Use a `Switch` control to enable or disable ear monitoring.
@@ -109,7 +53,6 @@ Ear monitoring allows users to hear their own microphone audio in real time. Man
 
 3. **Listen for State Updates**: Subscribe to ear monitor state changes to update the UI in real time.
 
-
 #### Code Example
 ``` java
 import io.trtc.tuikit.atomicxcore.api.device.AudioEffectStore
@@ -136,44 +79,14 @@ CoroutineScope(Dispatchers.Main).launch {
 ```
 
 #### setVoiceEarMonitorEnable Parameters
-<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" >`enable`</td>
-
-<td rowspan="1" colSpan="1" >`Boolean`</td>
-
-<td rowspan="1" colSpan="1" >Whether to enable ear monitoring.<br>- true: Enable<br>- false: Disable</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `enable` | `Boolean` | Whether to enable ear monitoring.<br>- true: Enable<br>- false: Disable |
 
 #### setVoiceEarMonitorVolume Parameters
-<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" >`volume`</td>
-
-<td rowspan="1" colSpan="1" >`Int`</td>
-
-<td rowspan="1" colSpan="1" >Ear monitor volume.<br>- Range: [0, 150]<br>- Default: 100</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `volume` | `Int` | Ear monitor volume.<br>- Range: [0, 150]<br>- Default: 100 |
 
 ### Step 4: Implement Microphone Volume Adjustment
 
@@ -184,7 +97,6 @@ To adjust the microphone (capture) volume, call `setCaptureVolume(volume) `on `D
 
 2. **Listen for State Updates**: Subscribe to capture volume state changes to update the UI in real time.
 
-
 #### Code Example
 ``` java
 import kotlinx.coroutines.CoroutineScope
@@ -205,24 +117,9 @@ CoroutineScope(Dispatchers.Main).launch {
 ```
 
 #### setCaptureVolume Parameters
-<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" >`volume`</td>
-
-<td rowspan="1" colSpan="1" >`Int`</td>
-
-<td rowspan="1" colSpan="1" >Microphone (capture) volume.<br>- Range: [0, 150]<br>- Default: 100</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `volume` | `Int` | Microphone (capture) volume.<br>- Range: [0, 150]<br>- Default: 100 |
 
 ### Step 5: Implement Voice Effects
 
@@ -241,24 +138,9 @@ audioEffectStore.setAudioChangerType(AudioChangerType.NONE)
 ```
 
 #### setAudioChangerType Parameters
-<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" >`type`</td>
-
-<td rowspan="1" colSpan="1" >`AudioChangerType`</td>
-
-<td rowspan="1" colSpan="1" >Voice effect enum value.</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `type` | `AudioChangerType` | Voice effect enum value. |
 
 ### Step 6: Implement Reverb Effects
 
@@ -275,33 +157,17 @@ audioEffectStore.setAudioReverbType(AudioReverbType.NONE)
 ```
 
 #### setAudioReverbType Parameters
-<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" >`type`</td>
-
-<td rowspan="1" colSpan="1" >`AudioReverbType`</td>
-
-<td rowspan="1" colSpan="1" >Reverb effect enum value.</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `type` | `AudioReverbType` | Reverb effect enum value. |
 
 ### Step 7: Reset Audio Effect Settings
 
 > **Note：**
-> 
+>
 
 > `AudioEffectStore` and `DeviceStore` are singletons, so audio effect and device settings are globally applied. To prevent settings from one live room affecting others, reset audio effect and device settings when the current live room ends.
-> 
-
+>
 
 Reset audio effect settings in the following scenarios:
 1. When the current live room ends.
@@ -311,7 +177,7 @@ Reset audio effect settings in the following scenarios:
    ``` java
    import io.trtc.tuikit.atomicxcore.api.device.AudioEffectStore
    import io.trtc.tuikit.atomicxcore.api.device.DeviceStore
-   
+
    // One-click reset for all voice and reverb effects
    AudioEffectStore.shared().reset()
    DeviceStore.shared().reset()
@@ -320,32 +186,10 @@ Reset audio effect settings in the following scenarios:
 ## API Documentation
 
 For detailed information on all public interfaces and properties of [AudioEffectStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-audio-effect-store/index.html), [DeviceStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-device-store/index.html), and their related classes, refer to the official API documentation for the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore) framework.
-<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" >AudioEffectStore</td>
-
-<td rowspan="1" colSpan="1" >Manage audio effects: configure and retrieve real-time audio effect status.</td>
-
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-audio-effect-store/index.html)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >DeviceStore</td>
-
-<td rowspan="1" colSpan="1" >Manage devices: control camera and microphone, and retrieve real-time device status.</td>
-
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-device-store/index.html)</td>
-</tr>
-</table>
-
+| **Store/Component** | **Feature Description** | **API Documentation** |
+| --- | --- | --- |
+| AudioEffectStore | Manage audio effects: configure and retrieve real-time audio effect status. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-audio-effect-store/index.html) |
+| DeviceStore | Manage devices: control camera and microphone, and retrieve real-time device status. | [API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.device/-device-store/index.html) |
 
 ## FAQs
 
@@ -360,7 +204,6 @@ This is a common point of confusion:
 
 - **Ear Monitor Volume**: Set via `AudioEffectStore.setVoiceEarMonitorVolume()`.  It only determines the volume level you hear in your in-ear monitor and does not affect the audience.
 
-
 ### Why does a newly created live room already have audio effects, or why is the volume too high or too low?
 
 Because `AudioEffectStore` and `DeviceStore` are singletons, audio effect and device settings are globally applied. If you previously set audio effects and did not reset them, those settings persist. Call the `reset()` method at the appropriate time to clear them.
@@ -374,7 +217,6 @@ Check the following:
 
 3. **Is the microphone enabled?** Confirm that the microphone is enabled in DeviceStore (i.e., openLocalMicrophone has been called).
 
-
 ### Can voice effects and reverb be enabled at the same time?
 
-Yes. `AudioChangerType` and `AudioReverbType` can be enabled simultaneously. For example, you can set both `AudioChangerType.LITTLE_GIRL`and `AudioReverbType.KTV` at the same time.
+Yes. `AudioChangerType` and `AudioReverbType` can be enabled simultaneously. For example, you can set both `AudioChangerType.LITTLE_GIRL`and `AudioReverbType.KTV` at the same time.

package/resource/doc/livekit/{live → core-sdk/live}/android/live-barrage.md

@@ -1,8 +1,5 @@
 This document provides a comprehensive guide for iOS developers to quickly integrate a feature-rich, high-performance live chat overlay (barrage/danmaku) system into your live streaming application using the `BarrageStore` module from the **AtomicXCore** framework.
 
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/fcf29098c6bb11f0a4a55254001c06ec.png)
-
-
 ## Core Features
 
 `BarrageStore` delivers a complete barrage solution for your live streaming app. Core features include:
@@ -14,50 +11,19 @@ This document provides a comprehensive guide for iOS developers to quickly integ
 
 - Inserting system tips into the local message list (for example, "Welcome XX to 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 Responsibility & Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[Barrage](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage/index.html)</td>
-
-<td rowspan="1" colSpan="1" >data class</td>
-
-<td rowspan="1" colSpan="1" >Represents a single barrage message. Contains sender info (sender), message content (textContent or data), and message type (messageType).</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[BarrageState](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage-state/index.html)</td>
-
-<td rowspan="1" colSpan="1" >data class</td>
-
-<td rowspan="1" colSpan="1" >Represents the current state of the barrage module. The main property, messageList, is a StateFlow containing all barrage messages for the current live room, ordered chronologically. This serves as the UI data source.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[BarrageStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage-store/index.html)</td>
-
-<td rowspan="1" colSpan="1" >abstract class</td>
-
-<td rowspan="1" colSpan="1" >The main manager for barrage features. Use it to send messages (sendTextMessage, sendCustomMessage) and subscribe to barrage message updates via its state property.</td>
-</tr>
-</table>
-
+| **Core Concept** | **Type** | **Core Responsibility & Description** |
+| --- | --- | --- |
+| [Barrage](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage/index.html) | data class | Represents a single barrage message. Contains sender info (sender), message content (textContent or data), and message type (messageType). |
+| [BarrageState](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage-state/index.html) | data class | Represents the current state of the barrage module. The main property, messageList, is a StateFlow containing all barrage messages for the current live room, ordered chronologically. This serves as the UI data source. |
+| [BarrageStore](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.barrage/-barrage-store/index.html) | abstract class | The main manager for barrage features. Use it to send messages (sendTextMessage, sendCustomMessage) and subscribe to barrage message updates via its state property. |
 
 ## Implementation
 
 ### Step 1: Component Integration
-- **Video Live Streaming**: Please refer to [Quick Start](https://write.woa.com/document/194571606056804352) to integrate AtomicXCore.
-
-- **Voice Chat Room**: Please refer to [Quick Start](https://write.woa.com/document/194571595678187521) 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 Listen to Barrages
 
@@ -73,11 +39,11 @@ class BarrageManager(
 ) {
     private val barrageStore: BarrageStore = BarrageStore.create(liveId)
     private val scope = CoroutineScope(Dispatchers.Main)
-    
+
     // Expose the [full] message list as a Flow for the UI layer to subscribe to
     private val _messagesFlow = MutableStateFlow<List<Barrage>>(emptyList())
     val messagesFlow: StateFlow<List<Barrage>> = _messagesFlow.asStateFlow()
-    
+
     init {
         // Start listening for barrage messages immediately after initialization
         subscribeToBarrageUpdates()
@@ -114,7 +80,7 @@ class BarrageManager(
         if (text.isEmpty()) {
             return
         }
-        
+
         // Call the core API to send the message
         barrageStore.sendTextMessage(
             text,
@@ -136,40 +102,11 @@ class BarrageManager(
 ```
 
 #### API Parameters
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`text`</td>
-
-<td rowspan="1" colSpan="1" >`String?`</td>
-
-<td rowspan="1" colSpan="1" >The text content to send.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`extensionInfo`</td>
-
-<td rowspan="1" colSpan="1" >`Map<String, String>?`</td>
-
-<td rowspan="1" colSpan="1" >Additional data for business customization.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`completion`</td>
-
-<td rowspan="1" colSpan="1" >`CompletionHandler?`</td>
-
-<td rowspan="1" colSpan="1" >Callback invoked after sending, indicating success or failure.</td>
-</tr>
-</table>
-
+| **Parameter** | **Type** | **Description** |
+| --- | --- | --- |
+| `text` | `String?` | The text content to send. |
+| `extensionInfo` | `Map<String, String>?` | Additional data for business customization. |
+| `completion` | `CompletionHandler?` | Callback invoked after sending, indicating success or failure. |
 
 ### Step 4: Send Custom Barrage
 
@@ -205,7 +142,7 @@ class BarrageManager(
                 override fun onSuccess() {
                     println("Gift message (custom barrage) sent successfully")
                 }
-                
+
                 override fun onFailure(code: Int, desc: String) {
                     println("Failed to send gift message: $desc")
                 }
@@ -216,40 +153,11 @@ class BarrageManager(
 ```
 
 #### API Parameters
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >businessId</td>
-
-<td rowspan="1" colSpan="1" >String</td>
-
-<td rowspan="1" colSpan="1" >Unique business identifier (e.g., "live_gift"). Used by receivers to distinguish custom messages.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >data</td>
-
-<td rowspan="1" colSpan="1" >String</td>
-
-<td rowspan="1" colSpan="1" >Business data, typically a JSON string.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >completion</td>
-
-<td rowspan="1" colSpan="1" >CompletionHandler?</td>
-
-<td rowspan="1" colSpan="1" >Callback after sending.</td>
-</tr>
-</table>
-
+| **Parameter** | **Type** | **Description** |
+| --- | --- | --- |
+| businessId | String | Unique business identifier (e.g., "live_gift"). Used by receivers to distinguish custom messages. |
+| data | String | Business data, typically a JSON string. |
+| completion | CompletionHandler? | Callback after sending. |
 
 ### Step 5: Insert Local Tip Messages
 
@@ -275,24 +183,9 @@ class BarrageManager(
 ```
 
 #### API Parameters
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >message</td>
-
-<td rowspan="1" colSpan="1" >Barrage</td>
-
-<td rowspan="1" colSpan="1" >The message object to insert locally. The SDK appends this to messageList in BarrageState.</td>
-</tr>
-</table>
-
+| **Parameter** | **Type** | **Description** |
+| --- | --- | --- |
+| message | Barrage | The message object to insert locally. The SDK appends this to messageList in BarrageState. |
 
 ### Step 6: Manage User Speaking Permissions (Mute and Unmute)
 
@@ -446,11 +339,11 @@ class BarrageUIManager(
     private fun refreshUIIfNeeded() {
         val fullList = this.latestMessageList ?: return
         val adapter = recyclerView.adapter ?: return
-        this.latestMessageList = null 
+        this.latestMessageList = null
 
         // Only take the latest N messages
         val cappedList = fullList.takeLast(capacity)
-        
+
         dataSource.clear()
         dataSource.addAll(cappedList)
         adapter.notifyDataSetChanged()
@@ -516,7 +409,7 @@ For detailed information on all public interfaces, properties, methods of [Barra
 
 ### In addition to basic text barrages, we also want to implement richer styles such as "colored barrages" and "gift barrages." How can we achieve this?
 
-You can implement these features using custom messages with `sendCustomMessage`. 
+You can implement these features using custom messages with `sendCustomMessage`.
 
 **Implementation Steps**
 1. **Define the Data Structure**: Collaborate with your client and server teams to define the JSON structure for custom messages. For example, a colored barrage can be defined as:
@@ -528,7 +421,6 @@ You can implement these features using custom messages with `sendCustomMessage`.
 
 3. **Receiver**: Upon receiving a barrage message, check whether its messageType is `BarrageType.CUSTOM` and whether the `businessID` matches. If so, parse the data string (usually as JSON), and render your custom UI style based on the parsed data (such as `color`, `text`).
 
-
 ### If I call BarrageStore.create(liveID = "some_id") in different classes or files, will this create multiple instances and cause confusion?
 
 No. The internal mechanism of **AtomicXCore** ensures that as long as you pass in the same `liveID`, you always get the same `BarrageStore` instance for that live room. You do not need to manage singletons manually.
@@ -544,7 +436,6 @@ No. The internal mechanism of **AtomicXCore** ensures that as long as you pass i
 
 4. **Network issues**: Ensure the device's network connection is normal. Message sending depends on network connectivity.
 
-
 ### How can new viewers see historical barrage messages sent before they joined the live room?
 
 `AtomicXCore` supports retrieving historical chat messages, but you need to enable this feature in the **server console**. Once configured, the SDK handles everything automatically—no additional client code is required.
@@ -554,12 +445,8 @@ No. The internal mechanism of **AtomicXCore** ensures that as long as you pass i
 
 2. On the Live Configuration page, select **View Past Messages**, and set Previous Messages Viewable to specify the number of messages (up to a maximum of 50) that new viewers can see.
 
-
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027202808/1215e910e09b11f095ab5254001c06ec.png)
-
-
 #### **Step 2: Automatic Retrieval on the Client Side**
 
 After completing the above configuration, **no changes are needed** in your client code.
 
-When a new user joins the live room, `AtomicXCore` automatically retrieves the configured number of historical chat messages in the background. These messages are delivered to the UI layer through the `BarrageState` subscription channel, just like real-time messages. Your application will receive and display these historical chat messages in the same way as live messages.
+When a new user joins the live room, `AtomicXCore` automatically retrieves the configured number of historical chat messages in the background. These messages are delivered to the UI layer through the `BarrageState` subscription channel, just like real-time messages. Your application will receive and display these historical chat messages in the same way as live messages.