Tolgee CLI Pull
Use Tolgee as the authoring platform and pull translation data into a predictable local format.
Unity Localization workflow layer
Tolgee workflow for Unity Localization
Sync Tolgee with Unity String Tables. Preview changes before writing assets. Generate compile-safe C# keys. Validate translations in CI.
TolBridge does not replace Unity Localization.
It adds a pull, preview, key-generation, and validation workflow on top of Unity's official Localization Package.
Add UI.Main DRILL_START_TITLE added to en, de
Update Gameplay.HUD RESOURCE_LOW_WARNING changed in de
Check Shared Data LOCAL_ONLY_DEBUG_LABEL reported before asset writes
LocalizationKeys.cs Compile-safe MVP feature
// <auto-generated />
namespace CrimsonDragon.TolBridge.Generated
{
public static class LocalizationKeys
{
public const string DrillStartTitle =
"DRILL_START_TITLE";
}
}Pull first, write after review
From Tolgee to Unity assets with a visible checkpoint
The first validation message is deliberately narrow: TolBridge follows the engine-native localization model and inserts a reviewable workflow step before changing project assets.
Dry-run Diff
Show added keys, changed translations, local-only entries, and mapping issues before writes.
Unity String Tables
Apply approved changes to Unity's official Localization Package assets.
LocalizationKeys.cs
Generate deterministic C# keys so renamed or deleted entries fail during compilation.
CI Validation
Run localization checks in Unity batchmode and fail the build on actionable problems.
What the MVP validates
Unity teams need fewer localization surprises
This page tests whether teams care about a safer String Table workflow before TolBridge becomes a finished product page.
Fragile free-string keys
Hand-written string IDs make deleted or renamed localization keys easy to miss until a scene or build path hits them.
Late missing-translation discoveries
Teams often find gaps during QA, release checks, or builds instead of seeing concise validation output earlier.
Awkward TMS/String Table sync
Translation management and Unity assets do not naturally line up around namespaces, locales, and table collections.
MVP feature promise
Focused tooling around Unity Localization
The first version should prove the workflow value without adding a runtime translation database or replacing Unity's package.
Dry-run sync
Preview Tolgee changes grouped by table, locale, and key before Unity assets are modified.
Compile-safe keys
Generate LocalizationKeys.cs from Shared Table Data so removed keys can break code at compile time.
CI validation
Check mappings, missing translations, unknown locales, and generated-key freshness in Unity batchmode.
Early tester validation
Help test the workflow before the package exists
The waitlist qualifies real Unity localization pain instead of collecting broad newsletter signups.
- Unity projects using, migrating to, or evaluating the official Localization Package.
- Teams that want Tolgee authoring while keeping Unity String Tables in the project.
- Developers who care about generated keys and build-time validation.
Early tester list
Share the workflow you are using now and what would make Unity localization feel safer.
FAQ and legal note
Independent workflow tooling
Is TolBridge a replacement for Unity's Localization Package?
No. The product direction keeps Unity String Tables as the runtime source of truth and adds workflow tooling around sync, generated keys, and validation.
Is TolBridge affiliated with Tolgee or Unity?
TolBridge is an independent tool and is not affiliated with, sponsored by, or endorsed by Tolgee or Unity Technologies. Unity is a trademark or registered trademark of Unity Technologies or its affiliates. Tolgee is a trademark of Tolgee s.r.o.
Why start with pull and validation instead of runtime translation fetching?
The validation thesis is that Unity teams first need a safe workflow around String Tables: pull from Tolgee, review a dry-run diff, write native assets, generate keys, and fail CI on localization problems.