In a game, a single term travels across more surfaces than almost any other kind of content. A weapon’s name appears in the inventory UI, in tutorial text, in a quest description, in a voiced line, in the store listing, in a patch note, and in a marketing trailer. If it is translated one way in the UI and another way in the dialogue, players notice immediately — and in a live game, that inconsistency compounds with every update.

This is why terminology consistency is the hardest part of game localization, and why it cannot be held by individual translators. No one person touches every asset, and no one remembers, six patches later, exactly how a faction name was rendered at launch. Consistency has to live in the workflow, not in memory.

Where game terminology breaks

• Across asset types. UI strings, dialogue, subtitles, store copy, and marketing are often handled by different people or vendors. Without a shared reference, each renders the same term slightly differently.
• Across updates. A term introduced at launch gets translated again from scratch in a later patch, by someone who never saw the original — so it drifts.
• Across languages. A character or item name needs a deliberate, documented decision per language (transliterate, translate, or keep the original), not an ad-hoc choice each time it appears.
• Across contributors. Live games rotate translators. Every handoff is a chance for terminology to reset unless it is written down and enforced.

What holds it together

A maintained termbase (glossary). Character names, item and skill terms, faction and location names, and world-specific vocabulary are locked in a reference that every contributor works against — with the per-language decision recorded, not re-derived.

A style guide for voice and register. Consistency is not only which word, but how a character sounds. A written guide keeps tone stable across contributors and updates.

An update workflow with memory. Every patch runs against the termbase, and every correction feeds back into it, so a fix made once holds across the next ten updates instead of being re-litigated each time.

One accountable partner across assets. When UI, dialogue, store, and marketing all run through the same terminology control, the same term cannot be translated five ways by five teams. This is the practical value of consolidating game localization rather than splitting it across vendors by asset type.

The test to apply

If you are evaluating a game localization partner, ask one question: “How do you keep a skill name introduced at launch identical in a patch shipped a year later, across UI, voice, and marketing?” A partner with real terminology control has a concrete answer involving a maintained termbase and an update workflow. A partner without one will talk about hiring good translators — which is necessary, but not what keeps terminology consistent across a live title.

Consistency across every asset and every update is exactly what game and manga localization has to deliver. It is the same terminology discipline that keeps any multilingual content aligned as it changes — games just make the cost of getting it wrong immediate and visible.