Anyone who has watched a live-service title age across seasons knows how quickly a single inconsistent term can surface. A faction name that shifts between patches, an ability that appears under two slightly different labels in the UI and the patch notes, or a character title that drifts across voice-over scripts and marketing copy—these are not minor polish issues. They chip away at the sense that the world is coherent. Players notice. Forums fill with screenshots. Trust erodes faster than most studios expect.
The root problem is rarely a lack of skilled linguists. It is the reality of how games are made and maintained. Multiple writers, external localization vendors, internal community teams, marketing freelancers, and seasonal content pipelines all touch the same core vocabulary. Without a shared reference, each group makes reasonable local decisions that eventually collide. What begins as parallel work turns into terminology fights that require expensive consistency passes later—or worse, leave the inconsistencies live.
A properly built game worldview terminology glossary, or termbase, addresses this at the structural level. It is not a static word list. It is a living single source of truth that records approved translations for character names, item and skill designations, location and faction terminology, system labels, and any invented vocabulary that carries mechanical or narrative weight. Each entry typically carries a short definition, part-of-speech note, usage constraints, and sometimes length limits or cultural notes. When the glossary is enforced through CAT tools and accessible to every contributor, the same term stays the same term whether it appears in a tutorial tooltip, a seasonal event description, or a community manager’s social post three years after launch.
Industry practice has long treated early glossary work as foundational rather than optional. Richard Honeywood, reflecting on Blizzard’s processes, described glossary and style-guide creation as one of the first deliberate stages after familiarization. More recent observations from live-ops studios show the same pattern: teams that extract candidate terms from the full string set before volume translation begins, then keep the resource updated with every content drop, spend far less time on rework. One widely cited industry observation notes that more than 30 percent of failed or problematic translations in key terms stem from inconsistency rather than outright error. Retroactive hunting for those divergences is almost always more expensive than preventing them.
The commercial stakes are measurable. Analysis of Steam sales data across thousands of titles has linked translation into a market’s primary language with roughly 12 percent higher revenue in that market, and broader localization efforts have been associated with sales lifts in the mid-teens in multiple studies. Those gains depend on the localized version feeling intentional. Players who encounter fractured naming conventions are less likely to stay engaged through the next season or recommend the title. For games designed around multi-year live operations, the glossary becomes part of the retention infrastructure.
Maintenance is the part most teams underestimate. New seasons introduce new mechanics and lore. Old terms sometimes need refinement for clarity or cultural fit. Someone has to own the update cycle, push changes to every active linguist and tool, and ensure version control so that a correction made for one language does not silently revert elsewhere. Centralized termbases inside modern translation management systems make this manageable; spreadsheet hand-offs do not. Studios that treat the glossary as a living quality-control asset rather than a one-time deliverable report fewer player-facing inconsistencies and lower long-term localization costs.
Global teams face an additional layer. A term that works cleanly in one language may require careful handling in another for gender agreement, compound-word length, or cultural resonance. The glossary records those decisions once so that subsequent contributors do not reinvent them. The same discipline applies whether the game is shipping into European, East Asian, Latin American, or Middle Eastern markets. Consistency across languages reinforces the sense of a single coherent world rather than a set of loosely related translations.
Building the resource early, enforcing it rigorously, and keeping it current is not glamorous work. It is, however, one of the highest-leverage investments a studio can make for any title expected to run for years. The alternative—letting terminology drift across teams and updates—quietly taxes immersion, support volume, and player goodwill.
Artlangs Translation has spent more than two decades refining exactly these kinds of sustained localization systems. With coverage across 230-plus languages, a network of more than 20,000 professional linguists, and a track record of complex game, short-drama, video, and audiobook projects, the company maintains the terminology discipline and process infrastructure that long-running titles require. Its work spans text localization, subtitle and voice adaptation, and the data practices that keep multilingual assets coherent over time.
