Ask an AI about this

Building turns your translated text, fonts, and voices into a single installable patch, and puts it straight into your game folder so you can play it.

The Build page

Building turns your translated text, fonts, and voices into a single installable patch, and puts it straight into your game folder so you can play it.

Building is the moment your project stops being a work-in-progress spread across pages and becomes a single thing: a patch that any player can install with two clicks. The Build page does three jobs, in order. It shows you where the work stands, it packages everything into the patch and installs it straight into your game folder, and it keeps the history of every build you've made. You'll come back here every time you improve your translation.

Build, release and install
The whole loop on S.T.A.L.K.E.R. 2: John builds his Japanese translation (only an example), tests it in his own game and releases it to everyone. Then Emily, another player on a Pro plan, finds it on Home and installs it in a few clicks. The build, the upload and the download are sped up, and the corner says by how much.

The build loop

The Build page opens on the game's art and four steps: Translate, Check, Build and Release. The one lit up is what to do next, and a red one says what is in the way. Under it sit two lanes side by side. The green Build lane makes the patch on this PC; the blue Release lane sends a finished build to Tranzio. They are separate on purpose: building never shares anything, and releasing is the only step other players see.

Build & release · Japanese

Stray Lanterns

Last build #0008 just now · released as v0.2.0 to everyone

  1. 1 Translate

    92% text879 strings still in English
  2. 2 Check

    1 warningNothing blocks a build
  3. 3 Build

    #0008 builtInstalled on this PC to test
  4. 4 Release

    Ready to releaseShare it as v0.3.0 so others can install
The four steps at the top of the Build page. First a build is waiting to be released, then the same translation before anything was translated, then with the text done and a build ready to make.
  1. Read the pre-build checks

    The Build lane shows three coverage figures (text, audio, fonts) and a list of anything worth knowing before you press the button: strings still untranslated in each target language, voice clips not linked to any line, recorded lines the build cannot deliver (a clip inside a sound bank, a Bink or RAD Audio wave, a file in an IoStore container), text files it cannot write back yet, a missing target language. Only one of those actually stops a build, which is having no target language at all. Everything else is advice, and each row says how many and why.

    Text

    100%

    12,483 / 12,483 strings

    Audio

    22%

    1,412 / 6,549 clips dubbed

    Fonts

    100%

    3 / 3 fonts replaced

    Nothing flagged. You’re ready to build.
    The coverage meters and the checks under them, as the last of the text gets translated. An area with nothing to cover reads n/a rather than 0%, so a game with no voice files never looks unfinished.

    An untranslated string is a warning, not an error, because the build has a sensible answer for it: it ships the original text. That's what makes releasing a half-finished translation possible, and it's why Beta releases exist.

  2. Build the patch

    Press Build #0007 (the button carries the next build's number) and the pipeline runs, stage by stage, with live progress and a streaming log beside it. On a big game with a dub this can take a few minutes. You can switch to another page and it keeps running.

  3. Play it

    The patch installs itself into the game folder the moment the build finishes, so there's nothing to copy anywhere. The page says Installed in your game and lays out what comes next; Play on Steam (or Epic) starts the game when Tranzio found it in your launcher. Play the important parts: the opening, a menu-heavy screen, a long dialogue. This is the step that catches what no automatic check can, like a line that's technically correct but sounds wrong coming from that character. To take the patch back out, use Remove patch on the game's overview.

  4. Release it

    When it plays right, press Release. It is the blue card after a build, the button in the Release lane, and the one on any finished row in the history. The window it opens asks who gets it and names the version; see Publishing.

What happens inside a build

The pipeline is short and the stage names say what they're doing. Stages that have no work simply don't appear: a text-only translation has no audio stage, and a game whose fonts you never touched has no font stage.

Encoding audio1,412 clips
01:12
Downloading fonts2 fonts
00:04
3
Building the Japanese patchpacking…
4
Installing patchpending
The pipeline mid-run. A finished stage keeps its time, the running one shows how far along it is, and everything below is still to come.
StageWhat it does
Encoding audioTurns every dub you recorded into the audio format this game actually loads. A clip that can't be encoded is dropped with a warning rather than failing the build, because the text is still worth shipping.
Downloading fontsFetches the font files you chose as replacements, once, before any packing starts.
Building the … patchOne stage per target language. Packs that language's text, fonts, and audio into a patch file the game can load.
Installing patchPuts the finished patch into your game folder so you can launch and test straight away.

Reading the log

Beside the pipeline runs the log: one line per thing that happened, stamped with how long into the build it was. Green lines are things that worked, amber ones are things that were skipped, and red ones are why a build stopped. The slow stages write a bar that fills in place rather than a new line per tick, so packing sixteen thousand clips still leaves the rest of the log readable. When something goes wrong, this is the first place to look, and every build keeps its log so you can open it again later from the history.

The header counts how long the build has been running. It adds a time remaining only once the stages that have finished actually give it one, and drops it again if the build stops moving: a countdown that keeps promising one more second while nothing happens tells you less than a clock that simply keeps counting.

build.logdone
00:00infobuild #0007 started · targets=ja
00:02infooverriding 2 fonts
00:06ok2/2 fonts ready
00:14warnaudio VO_Ch04_Keeper_08.wem: no encoder for this format
01:18ok1,412 audio clip(s) encoded
01:19infopacking the Japanese patch
01:57okJapanese · 日本語 → hollowtide_2026-04-02_ja.pak · 1,248 files · 2 fonts
01:58ok3 loose audio file(s) staged for install and publish
02:01okinstalled 1 pak(s) and 3 audio override(s) into the game folder
02:01done1,248 files packed across 1 language(s)
A build log streaming. The amber line here is a dub that couldn't be encoded, which is a setup problem (a missing encoder) rather than a broken project, so the build carried on without it.

The most common failure by far is the game being open while you build. A running game holds its files, the patch can't be written, and the log says so in as many words. Close the game and press Build again.

Reading the build history

Every build you made is a row, newest first. It starts with whether the build finished, then its number. In the game marks the build whose patch is installed right now. A released build shows its version and who got it: Everyone means anyone who owns the game can install it, Just me means it is saved to your account where only you see it. Stable is the version everyone gets by default; Beta goes only to people who opt in to try new work early. Then which languages it was for, how long it took, and when.

A finished build that never left this computer has a Release button. The icons beside it (their names show when you point at them): Open folder shows the build's files on your computer. Log opens everything the build did, which you only need when it failed. Build again runs a new build with the same settings, for after a fix or a game update. Delete removes the build and its files, and its cloud copy if it had one; it asks first, and your translation itself is never touched.

Builds and versions

Every build gets a build number like #0007, and the page keeps the full history: what it targeted, how long it took, when it ran, and whether it ever left your machine. Build numbers are yours alone. A version like v0.2.0 is a different thing: it's the name a release carries once you release that build, and it's what players see. Most builds never become a release.

Build history· 4 builds

  • Finished
    #0008In the game
    Languages
    Japanese
    Took
    1m 58s
    When
    6 min ago
  • Finished
    #0007v0.2.0 · EveryoneBeta
    Languages
    Japanese
    Took
    2m 01s
    When
    yesterday
  • Finished
    #0006v0.1.4 · Just meBeta
    Languages
    Japanese
    Took
    2m 01s
    When
    yesterday
  • Failed
    #0005
    Languages
    Japanese
    Took
    12s
    When
    yesterday
The build history. The chip beside a build number says which version it went out as and who got it: everyone, or just you. A build with no chip has never left this machine, and the newest one here is the one in the game.

When you improve your translation later, build again and publish a new release; everyone who installed your adaptation sees an update available tag and your changelog. That update loop is described from the player's side in Keeping translations up to date.

A build packages your work only: translated text, fonts, and audio. It never includes the game's original files, which is why your patch stays small, legal, and only installable by people who own the game.

Happy with how it plays? The last step is sharing it: Publishing & My adaptations.