Find missing translations and broken placeholders before players see them

After a new language is added or a text changes, some lines are missing, still empty, or lose the slot where a name or number should go, and the screen shows raw code words. This entry shows how to make the AI compare each language file with the main one and list every problem.

Why this works

One language is the source of truth, and every other one is a copy that can drift from it. Comparing the copy line by line against the source finds every gap and slot mismatch before a player has to stumble over it.

When not to use it

Skip it for a game with a handful of texts in one language, where a quick read is enough. It also cannot judge whether a translation is good; only a native speaker can tell that.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• A diagram of every state
• 39 lines of example code with 5 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Find missing translations and broken placeholders before players see them" (read_entry translation-file-missing-or-broken-texts) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP