Keeping a character's voice consistent across thousands of lines
A character introduced in the opening hours with a sharp, clipped way of speaking gradually softens into generic dialogue by the time DLC content ships two years later — not because anyone decided the character changed, but because the line-by-line decisions that made their voice distinctive were never written down anywhere a second translator could find them.
Voice drift is rarely one dramatic mistake. It is the accumulation of many small, individually defensible choices made by different people, at different times, without a shared reference for what this character actually sounds like.
What makes a voice a voice
A character's voice is not one thing — it is a bundle of smaller, checkable habits: their speech register (formal, blunt, flowery), catchphrases or verbal tics they return to, sentence length and rhythm, and the vocabulary they favor or avoid. A hot-tempered soldier and a soft-spoken scholar shouldn't just say different things — they should sound different even reading a transcript with the names removed.
The trap is treating voice as something a translator intuits fresh from each line. Intuition is inconsistent by nature: two competent translators reading the same character bio will make different but equally reasonable voice choices, and the same translator will drift over months without noticing.
Voice sheets: a reference per character
A voice sheet is a short, per-character document that any translator can check before writing a line for that character. It typically covers who the character is and their relationship to the player, how they speak (register, tics, things they would and would not say), and a handful of sample lines that demonstrate the voice in practice.
The sample lines matter more than the description. It is easier to match a tone from three concrete example lines than to reverse-engineer it from adjectives like sarcastic or gruff, which mean something different to every reader.
Consistency across DLC and seasonal content
Voice drift compounds with time gaps. A character who last spoke in the base game a year ago, then reappears in a seasonal event written by someone who joined the project since, is the single most common place a voice sheet earns its keep — there is no recent dialogue to reread for tone, only the document.
The same applies when a character is picked up by a different translator mid-project, whether due to team changes or simple workload distribution. Without a shared reference, the character effectively gets two different personalities depending on who is writing that week.
What is mechanically checkable
Some parts of voice consistency reduce to pattern matching and don't need a human read for every line:
- Name and title spelling — the same character rendered the same way everywhere
- Catchphrases used verbatim, not paraphrased differently each time
- Banned or reserved phrases — words another character owns, or a register this character never uses
- Whether a character's grammatical register (formal/casual) is consistent line to line
What still needs a human reader
Whether a line actually sounds like the character is a judgment call no checklist replaces. A line can pass every mechanical check — correct name spelling, no banned words, consistent register — and still read as flat or generic, missing the rhythm or attitude that made the character recognizable in the first place.
The practical split is to let mechanical checks catch the clear-cut violations early and cheaply, so the human reviewer's time goes to the harder question: reading a batch of lines back to back and asking whether this still sounds like them, ideally against the voice sheet's sample lines as an anchor rather than against memory alone.