Incorrect Chinese source
伤害总量奖励Total DMG Rewards
What players may expect: repeated attempts add to their damage total.
Bring your game to the world.
Keep what makes your game special, in every language. Translation, LQA, and voice-over that connect with players.
Understand the mechanics. Write rules players can follow.
Source text can contain errors. We confirm who can act, under which conditions, and with what results before writing clear instructions for players.
Discuss your translation project
Whether it is a single button or a full set of rules, we first confirm how the game works, then explain it clearly.
The Chinese source is wrong: highest damage, not total damage.
The Chinese label “伤害总量奖励” states the wrong reward basis. The game records the highest damage from a single attempt; damage from multiple attempts is not added together.
Actual game mechanic
Only the highest single-attempt damage countsWhat actually happens: only the highest damage from a single attempt counts.
Correct the Chinese first
单次挑战最高伤害奖励Meaning: rewards are based on the highest damage in a single attempt.
An accurate translation of an incorrect source still gives players the wrong rule.
Verify the mechanic → Correct Chinese → Update all languages → Validate in gameSee how we verify the rules
Human judgment
Compare the rule description with actual behavior, identify the conflict with “total”, and confirm it with the design team. Correct the Chinese source first, then update English and the other languages.
In-game validation
Inspect challenge records and reward calculation to confirm they use the highest single-attempt damage, not cumulative damage. Check whether the revised explanation makes this clear to players.
Beyond translation: restructure the rules.
In the strategy-game example, attacker and prisoner rules, rescue and protection were mixed into long paragraphs. Establish each role’s mechanics, then organize the information around player questions.
- Which role am I?
- Which conditions apply?
- What can I do?
- What happens next?
From verified mechanics to clear instructions.
Select a step to explore how each decision is made.
Identify questions
Flag ambiguous words, omitted relationships and source statements that may conflict with gameplay.
Consult references
Review design documents, UI context, character profiles and regional configurations.
Verify mechanics
Confirm who can act, what triggers each condition, how values are calculated, and what happens next.
Structure the explanation
Organize information by role, condition, action and outcome so players know what to do next.
Validate in game
Within the agreed scope, test actions, feedback and scoring, then verify the revised text.
One English word can describe different functions.
A name, an action, a server status, and a promotional label can call for different translations. Choose a context to see how the wording changes.
Mount listMount
Montaria
An object name requires a noun. Portuguese example: Montaria.
Mount actionMount
Montar
A button for getting on a mount needs a verb. In Portuguese, that is Montar.
Full serverHot
Completo
First confirm that the state means full. Final wording depends on the server state and interface context.
Popular itemHot
Popular
This means popular, not at capacity. Choose the wording that matches the actual marketing meaning.
See how we verify the rules
Human judgment
Check where the string appears and what it refers to. The same English word may need different translations in different contexts.
In-game validation
Inspect lists, buttons and state indicators to verify referents, available actions and state changes.
Is it a level, or an instruction?
“Upgrade Level” leaves the relationship implicit. In this example it is a level field, so its meaning must be clarified first.
Upgrade Level
Without the interface, it could be read as either a noun phrase or an instruction to upgrade.
Level of advancement
This example is an attribute field. Confirm whether it means the current advancement stage or the required level before finalizing the translation.
See how we verify the rules
Human judgment
Check the field label and its value to confirm that it describes a level rather than an action.
In-game validation
Inspect the adjacent value and explanation, then compare the display before and after advancement.
What does “Promote” let the player do?
If the goal is to recruit teammates, use recruitment wording. If the button posts the party to a chat channel, explain the posting action. “Promote” can also suggest rank advancement or advertising.
1:1 — which currency, and which conversion?
The source does not specify a currency. Translators need to check the game’s pricing configuration rather than assume RMB or use a current exchange rate.
1 : 1
Any amount topped up will be converted to Points by 1:1Payment currency
The player’s local payment currency
Amount paid
Confirmed local amount
Points received
Points set by the regional rule
For every [local currency amount] paid, receive [number of points].
See how we verify the rules
Human judgment
Confirm currency, regional prices, the points formula and rounding, then explain the rule for the target market.
In-game validation
In a test environment, compare the amount shown at payment, the displayed points and the points credited.
Similar buttons can perform different actions.
Choose a function to see a possible label and the behavior it describes. Final wording depends on how the game actually works.
Open to AllJoin directly
Eligible players can join the team directly.
Approval RequiredSubmit request → Await approval
A request to join needs approval; an invitation is sent by someone already in the team. Some games use Invite Only for requests, so check the behavior before choosing a label.
Auto InviteSend invitations
Use this label only when invitations are sent. Automatic matchmaking needs wording that describes that behavior.
Auto PlacePlace in the target slot
Confirm the object, destination and result. Do not label every distinct function Auto Fill.
See how we verify the rules
Human judgment
Use familiar gaming language to describe what the control does. Auto Fill is appropriate only when it accurately describes the function.
In-game validation
Trigger joining, approval, invitations and placement to confirm that labels match the results players see.
Deliverables
Files, records and acceptance criteria are agreed for each project.
- Questions and decisions about gameplay mechanics
- Revised gameplay instructions
- Agreed in-game validation records
Tell us about your localization project.
We translate terminology, UI, gameplay rules, and dialogue, with expert review and in-game checks to make sure the language works for players.
Discuss your translation projectExplore in-game LQA