Characters & NPCs
Names, titles and relationships
Keep what makes your game special, in every language. Translation, LQA, and voice-over that connect with players.
Build a termbase for characters, items, skills, and systems, with definitions, context, and relevant NPC details. Compare it with localization files, track changes, and review all affected text.
Discuss your translation project
Review localization files, character profiles and gameplay references. Human review confirms candidate terms, including important names that appear only rarely.
Names, titles and relationships
Cities, groups and worldbuilding
Names and practical uses
Effects, states and mechanics
Features and interaction points
Resources, rewards and rules
Classify characters, items, skills and other concepts.
Explain meaning, use and distinctions from similar concepts.
Link source lines, string keys, screenshots and profiles.
Chinese and English generally do not mark grammatical gender on nouns. Confirm the character’s gender and context before choosing gendered forms in other languages.

The name displayed above an NPC who is worried about a harbor closure.
Assuming the character is confirmed as male.
Assuming the character is confirmed as female.
Ask the product team; do not infer gender from names or appearance.
Character gender and grammatical gender are distinct fields.
Use text variants or an approved neutral expression.
Review pronouns and agreement in dialogue and quests too.
Select a step or play the walkthrough. Each stage records what was decided, why, and how it was checked.
Collect and classify candidates from text and reference material. Separate identical names that refer to different concepts.
Add definitions, NPC gender and usage context. Send unresolved questions to the product team.
Language reviewers confirm translations, grammatical forms, permitted variants and forbidden terms.
Check affected text when new localization files arrive or terms change. Review the agreed content before delivery.
Confirm the change, update the termbase, localization files and relevant translation memory, then verify and record the effective version.
Compare the termbase with the localization files to find missing terms, outdated wording, and mismatches. Review each difference before making changes.
Maintenance example
Item name · Description · Quest objective
Confirm why the Chinese name changed. If the meaning is unchanged, a target translation may remain valid; assess and record the decision.
Inventory · Shop · Item received message
Assuming the approved English term has changed, locate the old wording, review context and update relevant translation memory.
NPC name · Dialogue · Quest description
Assuming the character is confirmed as female, review the name, pronouns and adjective agreement together.
Multiple names for the same concept
Missing new terms or lingering old forms
New terms, definitions and languages
Deprecated or confusing terminology
Gender, number, case and forms of address
Approved short names, aliases and inflections
Tools flag possible issues; reviewers check them in context. Approved aliases, short names, and inflections help prevent valid wording from being replaced unnecessarily.
Files, records and acceptance criteria are agreed for each project.
Share your termbase, localization files, and character profiles. We’ll agree on which terms to collect, when to check them, and how to maintain them.
Discuss your translation projectShare the languages, services, and release dates you have in mind. Our team will follow up by email.