AI Translation

Level Infinite AI Translation is a text translation service built on large language models and vertical-domain corpora. It supports multilingual translation and is specifically optimized for gaming and pan-entertainment scenarios in areas such as custom glossary, automatic language detection, context enhancement, and data analytics.

note

• For product capabilities, applicable scenarios, and system architecture, see AI Translation Service
• For integration methods (SDK / API), see AI Translation Service Integration

You can use AI Translation in the Player Network Console to manage your project's translation content and view the Dashboard.

Translation Content Management

View the terminology library, slang library, translation memory, and manage translation scenarios through Translation Content Management.

Initialization

The AI Translation Feature can be officially used only after initialization.

1. When entering Translation Content Management for the first time, click Free Trial Now to initialize.

2. After initialization, the default translation scenario will be automatically generated, and an initialization success message will be displayed on the page.

Translation Scenario

When the client calls the translation service, this parameter is used to obtain the corresponding translation resources. Multiple translation scenarios are supported, making it easy to operate across different project scenes and versions.

1. Login to the Player Network Console and click Translation Content Management under AI Translation in the left column.

2. Under Translation Content Management, click Translation Scenario.

3. After initialization, the system will automatically create the Default Translation Scenario, allowing one-click copy of the game_code for project side invocation.

4. If you need more scenarios, click Add Translation Scenario in the popup to configure translation scenarios.

5. After filling in the Scenario Name, it is recommended to add a Scenario Description for easy team identification.
   

6. Click Confirm to save the translation scenario.
   

7. [Optional] If there are multiple translation scenarios, you can search by Scenario Name to quickly locate translation scenarios.

Terminology Library

Overview

The terminology library is usually the official terminology base (Terminology Base).It manages core terms such as character names, skill names, and system names officially defined for the project. Once matched, the outputs will strictly follow the configured translations to ensure global consistency, clarity, and precision.

Example: 中路=middle lane, 大招=ultimate, jungle=打野, Lubu=吕布

Operation Guide

Import

1. Login to the Player Network Console and click Translation Content Management under AI Translation in the left column.

2. Under Translation Content Management, click Terminology Library.

3. Click Import.

note

If this is your first time, please Download Terminology Template & Format Specifications to configure the content.

4. [Optional] The template can be configured based on requirements; unused language fields can be left blank.

5. Select the desired import method. Currently, Local File Import and Import from Production/Test Environment are supported.

Local File Import

1. Select Local File Import, click Upload Terminology File to choose and upload a file.

2. Click Confirm to start parsing the document.

note

If previous translation content exists, this import will overwrite the current active terminology library content.

3. After the file is parsed, click Confirm Import. After a secondary confirmation, the list page will display the imported content.

note

Please carefully review the imported data. Only [Valid Data] and [Recommended Entries] are supported for import; failed entries will not be imported.

Import from Production/Test Environment

1. If there is already configured terminology library content in the production/test environment, you can import from there.

2. Click Confirm to start parsing the document.

note

If previous translation content exists, this import will overwrite the current active terminology library content.

3. After the file is parsed, click Confirm Import. After a secondary confirmation, the list page will display the imported content.

4. [Optional] If the content is extensive, parsing in the background is supported and does not affect other operations on the front end.

5. [Optional] Single entry editing is supported.

Add

If you only need to add a single translation entry, you can manually configure it to avoid batch export and editing operations.

1. Under Terminology Library, click Add.

2. Fill in the required multilingual entries as needed and click Save.
   

Debug

Operations staff can quickly check whether translation content configuration meets expectations.

1. Under Terminology Library, click Debug.

2. Enter the entry to check. Supports automatic detection or specifying a language as the input source.

3. [Optional] If you think the translation is correct, you can click Copy to copy in one click, making document maintenance easier.

More Operations

More

Under Terminology Library, click More. Supports single/batch data deletion, clearing all current configuration entries, and exporting existing content.

Delete

1. Select the entries to delete in the Terminology Library List.

2. Click Delete under More.

3. Verify the number of entries to delete, click Confirm Delete to immediately delete the selected entries.

Clear

The clear operation will delete all current terminology library content. Please proceed with caution.

1. Click Clear under More.

2. In the popup, click Confirm Clear to immediately clear all current terminology library content.
   

3. [Optional] When the content is extensive, clearing in the background is supported and does not affect front-end operations.

Export

Export existing terminology library content as an Excel file, which can be used for subsequent translation content management.

1. Click Export under More.

2. [Optional] When the content is extensive, exporting in the background is supported and does not affect front-end operations.
   

3. The popup will display data packaging progress. Once completed, the browser will automatically download it.
   

Slang Library

Overview and Examples

The slang library is usually the player jargon / commonly used term collection (Slang).It manages jargon, spoken language, and common communication expressions already established among players, making translation results more natural and sound like "players talking".

Example: Blue = Blue Buff, Blue Daddy = Blue Buff, carry = boost, AFK = AFK, like for like = mutual likes

Replacement Best Practices

When adding or editing a slang entry, select the appropriate replacement method based on the language stage of the content to be replaced. The core difference between the four replacement methods lies in at which stage of the translation process the replacement occurs. The comparison is as follows:

Replacement Method	Replacement Timing	Applicable Scenario	Typical Case
Replace then Translate	Before sending to the model for translation	The source language contains jargon, terms, or abbreviations that are difficult for the model to understand	Blue Daddy → Blue Buff
Translate then Replace	After translation by the model	Redundant words, wrong words, or sensitive words appear in the target language (such as HTML escape characters or incorrectly added tags)	Sensitive words in model output → Standard wording
Direct Replace	No translation; replace upon match	Emergency fix for bad cases that cannot be handled by the first two methods; the effect is equivalent to "Translation Memory"	Hold on, we can win this! (whole sentence locked)
Keep Original	No translation; locked in place	Lock emoticons, hashtags, line breaks, HTML escape characters, etc.	/n, #hashtag kept as-is

Detailed descriptions and typical cases for each method are provided below. In the case entries, "Any language (auto-detect)" means the system automatically detects the input language, while "Any language" means the configuration applies to all output languages.

Replace then Translate

Replace the user's input content with the currently configured content first, then call the large language model for translation. Commonly used to replace words that are difficult for the model to understand (jargon, terms, abbreviations, etc.). Because the replacement happens before translation and the replaced content will continue to be translated, a single configuration applies to all languages — just fill in the Target Entry with a standard expression that the model can understand.

Original Entry	Target Entry	Player Input Example	Chinese Output	English Output	Japanese Output
Any language (auto-detect)｜Blue Daddy	Any language｜Blue Buff	Jungle goes to farm Blue Daddy	打野去打蓝buff	Jungler, go take the Blue Buff.	ジャングラーはブルーバフを取りに行って。
Any language (auto-detect)｜Maoyao	Any language｜Marco Polo + Yao	Marco in bot lane is very strong	下路马可波罗+瑶很厉害	The Marco Polo + Yao bot lane is really strong.	下レーンのマルコポーロ＋瑶がめっちゃ強い。
Any language (auto-detect)｜K-steal	Any language｜steal kills	Teammates only steal K	队友只会抢人头	My teammates only know how to steal kills.	味方はキルを横取りするばかり。

Translate then Replace

First call the large language model to translate the user's input content; if the result contains the entry, perform the replacement. The replacement only affects the translation output; the player's input is unaffected. The Original Entry is configured per output language, and language-independent symbols or tags can use Any language. Leaving the Target Entry empty means deleting that entry from the translation output.

Original Entry	Target Entry	Player Input Example	Chinese Output	English Output	Japanese Output
Any language｜<text>	Any language｜(empty, i.e. delete)	Help me look at this match<text>my teammates are throwing</text>	帮我看看这局队友太坑。	Help me look at this match—my teammates are throwing.	この試合、味方がひどすぎるので見て。
Any language｜test	Any language｜(empty, i.e. delete)	test	测试	(empty)	テスト
English｜crispy skin	English｜squishy	Their whole team is squishy	对面全是脆皮	Their whole team is squishy.	相手チームは全員脆い。
Any language｜&#39;	Any language｜'	You've done what you did to us	你们做过的事，我们都会还回来。	You've done what you did to us.	あなたが私たちにしてきたことをやり返しただけだ。

Direct Replace

Once an entry is matched, it is strictly replaced according to the configured content. Used for emergency fixes of stubborn bad cases that the first two methods cannot handle; the effect is equivalent to "Translation Memory." It requires a full-sentence exact match and must be configured separately per output language (using "+ Add Language" to configure line by line). Not commonly used.

Original Entry	Target Entry	Player Input Example	Chinese Output	English Output	Japanese Output
Any language (auto-detect)｜Hold on, we can win this!	Chinese｜Hold on, we can win this! English｜Hold on, we can win this! Japanese｜持ち堪えれば勝てる！	Hold on, we can win this!	稳住，我们能赢	Hold on, we can win this!	持ち堪えれば勝てる！
Any language (auto-detect)｜He doesn't know how to gank	English｜don't know gank Japanese｜ガンクの仕方を知らない Malay｜Orang pun tak tahu gank	He doesn't know how to gank	人又不会抓	don't know gank	ガンクの仕方を知らない。
Any language (auto-detect)｜don't know gank	Chinese｜人又不会抓	don't know gank	人又不会抓	don't know gank	ガンクの仕方を知らない。

Keep Original

Not translated in any language; the original text remains unchanged. Used to lock content such as emoticons, hashtags, line breaks, and HTML escape characters that would become invalid or corrupted after translation. This method does not require a Target Entry; a single configuration covers all languages.

Original Entry	Target Entry	Player Input Example	Chinese Output	English Output	Japanese Output
Any language (auto-detect)｜/n, #hashtag1, #hashtag2	None (this method does not require a Target Entry)	Do you want to play with us? /n #hashtag1 #hashtag2	你想和我们一起玩吗？ /n #hashtag1 #hashtag2	Do you want to play with us? /n #hashtag1 #hashtag2	一緒に遊ばない？ /n #hashtag1 #hashtag2
Any language (auto-detect)｜(⁠ﾉ⁠◕⁠ヮ⁠◕⁠)⁠ﾉ⁠*⁠.⁠✧	None (this method does not require a Target Entry)	(⁠ﾉ⁠◕⁠ヮ⁠◕⁠)⁠ﾉ⁠*⁠.⁠✧ wow	(⁠ﾉ⁠◕⁠ヮ⁠◕⁠)⁠ﾉ⁠*⁠.⁠✧ 哇	(⁠ﾉ⁠◕⁠ヮ⁠◕⁠)⁠ﾉ⁠*⁠.⁠✧ Wow	(⁠ﾉ⁠◕⁠ヮ⁠◕⁠)⁠ﾉ⁠*⁠.⁠✧ うわぁ

Operation Guide

Import

1. Login to the Player Network Console and click Translation Content Management under AI Translation in the left column.

2. Under Translation Content Management, click Slang Library.

3. Click Import.

4. Select the desired import method. Currently, Local File Import and Import from Production/Test Environment are supported.

Local File Import

1. Select Local File Import, click Upload Slang File to choose and upload a file.

2. Click Confirm to start parsing the document.

note

If previous translation content exists, this import will overwrite the current active slang library content.

3. [Optional] If the content is extensive, parsing in the background is supported and does not affect other operations on the front end.

   After the file is parsed, click Confirm Import. After a secondary confirmation, the list page will display the imported content.

note

Please carefully review the imported data. Only [Valid Data] and [Recommended Entries] are supported for import; failed entries will not be imported.

Import from Production/Test Environment

1. If there is already configured slang library content in the production/test environment, you can import from there.

2. Click Confirm to start parsing the document.

note

If previous translation content exists, this import will overwrite the current active slang library content.

3. [Optional] If the content is extensive, parsing in the background is supported and does not affect other operations on the front end.

4. After the file is parsed, the list page will display the imported content.

5. [Optional] Single entry editing is supported.

Add

If you only need to add a single translation entry, you can manually configure it to avoid batch export and editing operations.

1. Under Slang Library, click Add.

2. Enter Target Entry.
   

3. Select the replacement method as needed. The basic settings display Replace then Translate and Translate then Replace by default; click Advanced Settings to enable Direct Replace and Keep Original.

   Basic Settings (displayed by default):

   • Replace then Translate: Replace the user input content with the currently set content first, then use the large language model for translation.
   • Translate then Replace: Use the large language model to translate the user input content first; if the result contains the entry, then perform the replacement.

   Advanced Settings: Click Advanced Settings to enable the following two additional methods.

   • Direct Replace: Once the entry is matched, it will be strictly replaced according to the configured content.
   • Keep Original: The content will not be translated in any language and will remain unchanged.

4. Fill in the replacement content, supporting replacement according to General or Other Languages.

note

General: General language has been selected. You cannot add other languages.

Other Languages: After selecting other languages, you can add more languages for translation.

5. Click Save to complete the creation.
   

When editing an existing slang entry, the same popup window will open, and the same Basic Settings and Advanced Settings rules will apply.

Debug

Operations staff can quickly check whether translation content configuration meets expectations.

1. Under Slang Library, click Debug.

2. Enter the entry to check. Supports automatic detection or specifying a language as the input source.

3. Click the Translate button to start debugging.
   

4. [Optional] If you think the translation is correct, you can click Copy to copy in one click, making document maintenance easier.

More Operations

More

Under Slang Library, click More. Supports single/batch data deletion, clearing all current configuration entries, and exporting existing content.

Delete

1. Select the entries to delete in the Slang Library List.

2. Click Delete under More.

3. Verify the number of entries to delete, click Confirm Delete to immediately delete the selected entries.

Clear

The clear operation will delete all current slang library content. Please proceed with caution.

1. Click Clear under More.

2. In the popup, click Confirm Clear to immediately clear all current slang library content.
   

3. [Optional] When the content is extensive, clearing in the background is supported and does not affect front-end operations.

Export

Export existing slang library content as an Excel file, which can be used for subsequent translation content management.

1. Click Export under More.

2. [Optional] When the content is extensive, exporting in the background is supported and does not affect front-end operations.

3. The popup will display data packaging progress. Once completed, the browser will automatically download it.
   

Translation Memory

Overview

Full-sentence translation memory is usually a fixed sentence-pattern repository (Translation Memory).Used to save confirmed sentence translations. When the same text appears, it will automatically match and reuse, improving translation consistency and efficiency.

Example: Mad skills! = Well played!｜ Our reign will never end! = The reign never ends!｜猥琐发育，别浪=Play it safe, focus on farming.

Operation Guide

Import

1. Login to the Player Network Console and click Translation Content Management under AI Translation in the left column.

2. Under Translation Content Management, click Translation Memory.

3. Click Import.

note

If this is your first time using, please download the full sentence table template & formatting guidelines to configure the content.

4. [Optional] The template can be configured based on requirements; unused language fields can be left blank.

5. Select the desired import method. Currently, Local File Import and Import from Production/Test Environment are supported.

Local File Import

1. Select Local File Import, click Upload Memory File to choose and upload a file.

2. Click Confirm to start parsing the document.

note

If previous translation content exists, this import will overwrite the current active translation memory content.

3. After the file is parsed, click Confirm Import. After a secondary confirmation, the list page will display the imported content.

note

Please carefully review the imported data. Only [Valid Data] and [Recommended Entries] are supported for import; failed entries will not be imported.

4. [Optional] If the content is extensive, parsing in the background is supported and does not affect other operations on the front end.

5. [Optional] If it is not the first time importing a multilingual entry file, canceling import is supported. You can click Abandon This Import to return to the list page.

Import from Production/Test Environment

1. If there is already configured translation memory content in the production/test environment, you can import from there and click Confirm to start import.

2. Click Confirm to start parsing the content. Once parsed, the list page will display the imported content.

note

If previous translation content exists, this import will overwrite the current active translation memory content.

3. [Optional] If the content is extensive, parsing in the background is supported and does not affect other operations on the front end.

4. [Optional] Single entry editing is supported.

Add

If you only need to add a single translation entry, you can manually configure it to avoid batch export and editing operations.

1. Under Translation Memory, click Add.

2. Fill in the multilingual entries you need to configure, then click New.

Debug

Operations staff can quickly check whether translation content configuration meets expectations.

1. Under Translation Memory, click Debug.

2. Enter the entry to check. Supports automatic detection or specifying a language as the input source.

3. [Optional] If you think the translation is correct, you can click Copy to copy in one click, making document maintenance easier.

More Operations

More

Under Translation Memory, click More. Supports single/batch data deletion, clearing all current configuration entries, and exporting existing content.

Delete

1. Select the entries to delete in the Translation Memory List.

2. Click Delete under More.

3. Verify the number of entries to delete, click Confirm Delete to immediately delete the selected entries.

Clear

The clear operation will delete all current translation memory content. Please proceed with caution.

1. Click Clear under More.

2. In the popup, click Confirm Clear to immediately clear all current translation memory content.
   

3. [Optional] When the content is extensive, clearing in the background is supported and does not affect front-end operations.

Export

Export existing translation memory content as an Excel file, which can be used for subsequent translation content management.

1. Click Export under More.

2. [Optional] When the content is extensive, exporting in the background is supported and does not affect front-end operations.

3. The popup will display data packaging progress. Once completed, the browser will automatically download it.
   

Operation Log

View historical operation logs of the Translation Content Management module through Operation Log, including detailed records of import, edit, clear, delete, and other actions for easier auditing and tracing.

1. On the Translation Content Management page, click Operation Log.

Filter Conditions

The operation log list supports quickly locating target records using the following filter conditions:

• Operation Time: Supports filtering operation logs by time range.

• Translation Scenario: Supports filtering by translation scenario name.

• Environment: Supports filtering by Production Environment or Test Environment.

• Operator: Supports filtering by operator account.

• Database: Supports filtering by Terminology Library, Slang Library, or Translation Memory.

• Operation Content: Supports filtering by Import, Edit, Clear, Delete, etc.

  

Dashboard

View core indicator data of AI Translation Service through Dashboard, including request count, translated character count, response time, and other key statistics, as well as visual charts for service usage trends and response time.

1. Login to the Player Network Console and click Dashboard under AI Translation in the left column.

Filter criteria

At the top of the Dashboard, you can view data within a specified range using the following filter criteria:

• Translation Scenario: Select the translation scenario to view. You can choose all scenarios or a specified scenario.
• Data Period: Select the time granularity for data statistics. Options include: Real-time Data, This Week, This Month, Last Ten Days, and more.

After configuring the filter criteria, click the Query button to refresh the data; click the Reset button to restore the default filter criteria.

Metrics

The Dashboard displays the following core metric cards:

Metric Name	Description
Request Count	Total number of AI translation API requests during the current period
Translated Characters	Total number of characters processed by the AI translation API during the current period
99% Response Time	99% of requests have response times shorter than this value
95% Response Time	95% of requests have response times shorter than this value
Average Response Duration	Average response duration of all requests during the current period
Cumulative Translated Volume	Total number of translated characters since business integration
Cumulative Call Count	Total number of translation API calls since business integration

Service Usage Trend

Displays the trend of request count and translated characters over the selected period. For real-time data, yesterday’s corresponding time period is shown as a dashed line for comparison.

The Service Usage Trend chart shows changes in translation service usage over time, supporting the following data dimensions:

• Request Count: Shows the number of requests at each time point.
• Translated Characters: Shows the number of translated characters at each time point.
• Request Count (Yesterday): Shows the comparison with the number of requests at the same period yesterday.
• Translated Characters (Yesterday): Shows the comparison with the number of translated characters at the same period yesterday.

The chart supports the Export feature in the top right corner, allowing you to export chart data as a file.

Service Response Time

Displays the trend of 99%, 95% percentile and average response times during the selected period.

The Service Response Time chart shows the changes in translation service response time over time, supporting the following data dimensions:

• 99% Response Time: Shows the 99% response time at each time point.
• 95% Response Time: Shows the 95% response time at each time point.
• Average Response Time: Shows the average response time at each time point.

The chart supports the Export feature in the top right corner, allowing you to export chart data as a file.

Distribution of Translation Languages

The proportion of requests by source language / target language during the selected period, can be toggled between views.

The Distribution of Translation Languages chart shows the language usage proportion in the translation service, supporting switching to view distribution data for either source or target languages.

Click the Source Language or Target Language labels to switch and view the respective language distribution.

• Source Language: Shows the distribution of source languages in translation requests.

• Target Language: Shows the distribution of target languages in translation requests.

  

The chart supports the Export feature in the top right corner, allowing you to export chart data as a file.