LocGuard Pro — Godot 4 localization QA

Catch untranslated strings before your players do.

Godot ships localization bugs silently: tr() returns the raw key when a translation is missing, and the built-in POT generator misses strings in .tscn/.tres properties and OptionButton items. LocGuard finds what actually breaks — in the editor and in CI.

What you get

• 🧭 In-editor dock: click "Scan project", get every finding in a list, double-click to open the offending file
• ⚙️ The full CLI (Node 18+, zero dependencies) with --strict and --json — exits non-zero on errors so your build fails before untranslated text ships
• 🧱 CI presets: GitHub Actions, GitLab CI and a pre-commit hook, ready to copy

What it catches

• missing-key — used in code/scenes but absent from your CSV (includes the .tscn/.tres texts and OptionButton items Godot's POT generator misses)
• placeholder drift — %d vs %s, {0}, {name} mismatches between locales (runtime format bugs)
• bbcode-imbalance — unclosed [b]…[/b] in translated RichTextLabel strings
• empty-translation — a blank locale column: players silently get the untranslated source text
• orphan-key, newline-key trap, overflow budgets (CLI)

Verified against the real engine

Every rule is proven by an automated suite that runs Godot 4.7 headless on a project seeded with each defect and asserts it genuinely breaks at runtime. The in-editor dock is kept in parity with the CLI by an automated parity test. If a rule can't be demonstrated in the real engine, it doesn't ship.

Free CLI

The CLI core is free and MIT-licensed at github.com/leobaray/locguard. Pro adds the in-editor dock, CI presets, the commercial license and support — and funds development.

From the maker of Blobsmith. Questions or bugs → comments below; they get fixed.