Élodie BourryGame localization

“Beautifully translated into French. Hats off to the translator.”Steam player · Cucina Stellata ↗

French first, then three more languages for the client.“You can thank Élodie for that.”Damien, CEO of Level Up ↗

No, I'm Not a Human: put forward for the first ATAA video game translation awardATAA Awards 2026

Credits include Dredge, The Alters, Planet of Lana II, Nioh 3, Harry Potter and The Orange BoxSee all 99+ titles ↗

20 years in games, from QA and localization to content and coordinationMy journey ↗

For developers · Before in-game LQA

Debug tools that cut your LQA bill

In-game testing is paid by the hour, and much of that time goes to reaching the text, not reading it: replaying a chapter for one line of dialogue, farming gold to open a shop, waiting for nightfall. A few debug tools take testers straight to the words. I spent years as an LQA tester, and this is the list I wish every build had shipped with.

Without debug tools

Replay 40 minutes of chapter 3 to check one fixed line, then describe where it is in a bug report.

With debug tools

Jump to the dialogue by its ID, check it, switch to English to compare, screenshot it as CH3_MIRA_014.png. Two minutes.

0/ of 18 tools in your build tools

Top pick saves the most hours for the least work.Tick what your build already has. The rest is your to-do list.

A little gift

Take the list with you: an Excel file to share with your dev team, with a status and notes column for every tool. Your ticks are already filled in. Free, no email needed.

Planning your LQA?

Send me the list of what your build can do. With these tools in place, I can scope in-game testing more precisely, and you pay for checking text, not for getting to it. You don't need all of them: the top picks alone make a real difference.

I've led LQA on The Orange Box, Battlefield: Bad Company and Mercenaries 2. See my testing credits →