Yulia Karostik, Head of Support & Localization at Vizor
Yulia manages partner relationships, including with vendors. Apart from seeking opportunities for budget optimization, she keeps an eye on the development of cutting-edge technologies and drives their implementation in Vizor’s processes.
Monthly saving on ZH-CN, ZH-TW, KO with MTPE, compared to professional human translation from scratch
Monthly saving on EN-NL with MTPE, compared to professional human localization
Founded in 2007, Vizor started off making simulation games for social networks, combining the expedition genre with farming mechanics.
Now Vizor is both a game developer and publisher of social and mobile games. Total DAU of their games exceeds 2 mln players. Their flagship game Klondike Adventures is responsible for half of this amount of daily active users.
Some games Vizor launched over 10 years ago are still being supported and regularly updated. Quite a term for the fast-changing gamedev world!
Vitalia Fokina, Localization Project Manager at Vizor
Vitalia is responsible for localization process management on the Vizor side, maintaining localization operations, and quality control.
She coordinates the work of Vizor’s in-house linguists, selects new instruments to enhance Vizor’s localization toolkit, and communicates with the Alconost team on a daily basis, answering questions from the editors and carefully curating every string.
Double-testing translation engines
The teams at Alconost and Vizor performed independent checks into the quality different engines produced when translating various languages. The transition to MTPE began only after both sides agreed on positive assessments.
"The engines aren't consistent, and their output can vary. The bilateral assessment gave us the most reliable result, and our efforts had a cumulative effect." — Dima Winicki, Alconost Localization Project Manager
Assessing engines in terms of respecting context
Alconost collected linguist feedback for each engine to establish a baseline quality level for each, and to see how appropriately the different engines were interpreting contextual hints. We also learned how to improve our prompts at this stage.
In the run-up to implementing MTPE for Vizor projects, Alconost took on the expense of quality assessment for the different machine translation engines.
"We thought it was an intriguing experiment. We can scale the results to other projects in the gamedev sector.
And we have a decade of history with Vizor, full of fruitful, enjoyable work. We wanted to make sure the client continued receiving high-quality translations, even after this fundamental change to the workflow." — Dima
This engine was used initially because it received the best feedback from native-speaking translators. However, later it was kept for the Korean language only.
After experimenting with prompts and leveraging ChatGPT’s newest version, DeepL was replaced by ChatGPT for all languages except Korean.
.png?width=1200&length=1200&name=Initial_Engine_Assesment_01_ES%20(1).png)
.png?width=1200&length=1200&name=Initial_Engine_Assesment_02_NL%20(2).png)
.png?width=1200&length=1200&name=Initial_Engine_Assesment_03_PT%20(2).png)
More frequent quality control at the start of MTPE implementation
For completely native localization, scheduled assessments are performed once per quarter. With MTPE projects, quality is assessed more often, once per month on average. These checks don't cost the client extra, despite their frequency and the involvement of native speakers.
"At the beginning, it was vital for us to be sure the MTPE workflow was set up correctly for each language pair. Once several consecutive checks show a stable level of quality, we can get back to a more standard schedule." — Dima
Prioritizing editing efforts
The Vizor team produced style guides for editors indicating which aspects of the machine translations were priorities for correction, and which could receive less attention.
"That way, editors can be more efficient with their time and effort." — Vitalia
Extra mile: same translators invited as editors
Alconost wanted to keep the same linguists on each project, but as editors, rather than translators. To that end, Alconost offered its translators individual sets of new terms.
And although post-editing is challenging — for some linguists, there are ethical issues, and for others, there are financial considerations — the basic pool of contributors to Vizor projects didn't change with the switch to MTPE.
These are basically dedicated linguists who feel attached to the gamedev world and have worked on these projects for years.
"AI can't yet cope with Japanese very well. With German, the value of the locale is a factor. And linguists are very much involved in the project for both those languages. Their comments are helping us with other locales, too." — Yulia
Yulia Karostik
Head of Support & Localization at Vizor
"We receive vital input from our dedicated linguists. They might point out some vagueness in the original phrasing. Or help us localize humor appropriately. We want to safeguard our relationship with people like that." — Vitalia
Vitalia Fokina
Localization Project Manager at Vizor
Achieve the desired cost savings
In some language pairs, the savings exceeded the target goal of 30% to reach 35% or even 50%. That permits Vizor to keep native-speaker localization in place for selected projects and locales while meeting the overall goal.
Keep quality at the high level set by native-speaker localization
This goes beyond minimizing complaints from players.
Put AI's translation potential to better use when testing important business development scenarios
In some language pairs, the savings exceeded the target goal of 30% to reach 35% or even 50%. That permits Vizor to keep native-speaker localization in place for selected projects and locales while meeting the overall goal.
Safe start
At the testing stage, when the potential for releasing the game globally is being assessed, a small amount of paid traffic is brought into the game. Many factors influence the testing results, and there's no point taking the risk that flaws in the localization will distort the metrics even more. Also, there's not enough text in the game, at this stage, for savings on localization to really be noticeable, especially compared to overall development costs.
Reliable foundation
When the decision is made to go ahead with the release, a huge influx of content will need translation, and later, that will become the foundation for a translation memory and glossary. If that basic content gets translated inconsistently, the project will basically be maimed from birth. There will be negative ripple effects on translation quality in subsequent updates.
Formal requirements & creative spirit
At the start of the project, the entire UI will need to be localized, in a way that fits within strict character limits. Presently, that's a weakness of machine translation. Characters' names and unique words or neologisms will also need some creative adaptation. Native-speaking linguists are still the top performers for those aspects of the job.
"I agree that MTPE is not a silver bullet. A legacy of native-speaker localization is the perfect foundation for MTPE.
But I don't think it's always a terrible idea to try out MTPE without that background of native localization. Especially if your budget is extremely limited. The details are important here: particular aspects of the content, what the engines can do, your own individual requirements or quality expectations...
It's possible that with the right combination of factors, the result would be acceptable, but I wouldn't guarantee it. Every specific project needs to be assessed individually."
Dima Winicki,
Alconost Localization Project Manager
The deceptive charm of poetry
Players don't love poetry as much as you might think! We've never seen a case where we've done an update in verse and users write to say "Thank God there's poetry!" Creating beautiful lines of verse for a game is fun, sure, but from what we've observed, it's not very rational. Save time and money on translations: use ordinary, creative prose rather than rhyming lines.
Mind the scope
It's a simple fact, but true: the less text your game has, the lower the translation cost. Especially when you need 12 languages! Any 100 words coming in can turn into 1200 words, in 12 languages, going out. And all of that costs money. Even if you're using MTPE, the cost is there. The less wordy the original, the less you'll spend longterm on translation.
MTPE means managers’ workload increases
When you implement MTPE, you reduce translators' participation in the project, but the volume of work grows significantly for the project manager. To obtain a machine translation with acceptable quality, you need to give the machine the right assignment, provide context, monitor its interpretations for accuracy, and collect the raw translations to hand over to native-speaking editors. Never underestimate the volume of work. The machine can make mistakes, and its results aren't always consistent. Creating raw translations isn't as easy as pushing a button. The job takes time, attention, and care.
Don't forget what your business actually is
Many studios can’t resist the temptation to handle localization in-house for the sake of cutting costs. It's especially alluring now, when AI tools can do some of the work. But as trite as this may sound, game development and localization are different businesses, and a gamedev company that focuses on game development will do better in the long run.
Avoid going to extremes
Track your reduced localization costs according to the final totals, not for individual languages. If you achieve the savings you need overall by switching to MTPE for particular languages and particular projects, you should feel good about sticking with native-speaker localization for the locales that are the most important to you. If your goal is to reduce costs, you should pursue that goal, and not leap to replacing all native-speaker localization with MTPE.
Keep it simple
Game developers love cultural references to music or other works of art. Localizing allusions like that is no easy task. Translators can do it, but when players miss the references, it makes us sad, because so much work went into localizing them. Try to use only truly classic Easter eggs that are relevant and understandable to your target audience in every country. Then all the work that goes into localizing them will feel justified.
From a lone wolf to a team player
Researching translation engines demands time and effort, and they evolve quickly. Your initial findings can become outdated as time goes by. When you look into an engine's potential on your own, you don't have anyone with whom you can compare experiences and observations. A localization partner who can do the research along with you will expand your capabilities and lend you support. You'll gain confidence, identify new areas where AI can be applied, and feel more willing to experiment.
