Loading
A QA-phase gate that catches broken layouts, mixed-language UI and dictionary drift across every locale you ship — before the build leaves your CI.
Localized builds break in ways a QA pass in English will never catch. Translation Guard runs on your staging build — before the aggregator sees it — and fails the gate on anything a player would notice.
German twice as long, Turkish with a diacritic stack, Arabic flipped RTL. We render every build in every locale on the resolutions and aspect ratios you ship to — and flag any string that clips, wraps badly, collides with a sibling, or pushes a button off-screen.
The build says it's Chinese. Most of the UI is — but the Buy Bonus button still reads "BUY BONUS", the paytable footer is in English, and one tooltip is in Polish. PlayPatrol's vision model recognizes the dominant script and flags every string that doesn't belong. No dictionary needed.
Give us your translation dictionary — CSV, JSON, XLIFF, whatever your localizers hand you — and we verify that every string you can see on screen matches the source of truth. No more "the button says something, but is it what Legal signed off?"
Translation Guard belongs in your pre-release pipeline. Point it at a staging URL, a demo environment or a release candidate — it spins up the game in every locale, on every resolution you care about, and returns a pass/fail before the build ever reaches an aggregator or an operator skin.
Once a build has shipped, operator-side issues (geo-blocks, broken wrappers, failed launches) are caught by Operators Network Pulse. Translation Guard is strictly a production-phase test — the last gate between "build green" and "aggregator submission".
Translation Guard is a pre-release gate. You point it at a build URL, hand over a dictionary if you have one, and it runs on every commit — or on every release candidate, your call.
A staging URL, preview environment or release-candidate link. No SDK in the game, no operator wrapper — we load it the way QA would. Configure the locales and viewports once.
CSV, JSON, XLIFF, gettext, whatever your localizers work in. Without it, we still catch overflow and mixed-language issues. With it, we verify every rendered string against the source of truth.
Webhook or CLI trigger. Gate fails when a defect above a threshold lands. Defects come with a rendered screenshot, DOM reference, source key and the expected-vs-actual diff — localization fixes at the source.
Translation Guard layers onto any provider plan. First build scanned inside a week of wiring up the webhook.