Ask an AI about this
Share your finished patch with the world, choose who can see it, and manage everything you've made from one shelf.
Publishing & My adaptations
Share your finished patch with the world, choose who can see it, and manage everything you've made from one shelf.
Publishing is the small step with the big consequence: your adaptation goes from a project on your computer to a listing in the catalog that any player in the world can install. It's also entirely under your control. You choose when, you choose who can see it, and you can keep improving it forever afterward through updates.
Uploading and publishing
Both start the same way: finish a build, then press Upload to Tranzio (from the build's success card, or from any successful row in the build history). One dialog opens, and it offers two different endings.
| Action | What happens |
|---|---|
| Upload | Stores the release on your account. Only you can see it, and you can install it on your own machines. This is the safe way to move a translation between your desktop and your laptop, or to keep a backup off the machine it was made on. |
| Upload & publish | Does the same, then lists it on Tranzio so other people can find and install it. A game only appears in the catalog at all once one of its adaptations has a published release. |
Either way, three things travel: your translation database, the patch file the game loads, and any dubbed audio that lives outside the patch. Nothing else leaves your machine.
- adaptation.tranzioyour translated text4.1 MB
- hollowtide_ka.pakthe patch the game loads18.6 MB
- 3 audio filesdubs that sit outside the pak6.2 MB
Published v0.2.0
The game's own files are never uploaded, and neither are the publisher's original strings or anything about where the game sits on your disk. What ships is a scrubbed copy of your adaptation, built for the purpose.
The version and the channel
Every release carries a version number, and the dialog picks one for you from how far the translation moved since your last release. It never asks you to think in patch, minor, and major: you say what the release is, and it shows you the number that makes.
Version
now v0.1.0Release as
Beside the version sits the channel, and it's a promise to players rather than a technical setting:
| Channel | What you're saying |
|---|---|
| Beta | For testers. Untranslated lines and rough edges are expected. This is the right choice for a first release, and the app never picks stable on your behalf. |
| Stable | Finished enough to play through. Players get this one by default, and publishing a stable release is what moves your adaptation to Published on the Adaptations page. |
A sensible path for a first release: publish as Beta, share it with a few players of your language, fold in what they find, then publish again as Stable. Published adaptations appear in the catalog under Community; when a Tranzio reviewer checks one for quality it earns the green Verified badge, which is the single biggest boost to how many players trust and install it.
Who can see it
Publishing lists a translation, and the Audience setting decides who that listing is for. It lives in an adaptation's settings and applies to the catalog and anywhere else translations are shown.
The people in a narrowed audience are not passive: followers and invited people both get a notification and an email every time you publish a release. That makes an invited audience a genuinely good way to run a closed test round rather than just a way to hide something.
The Adaptations page
Adaptations in the sidebar is your shelf: everything you author sits on top, everything you've installed from others sits below. Each of your own shows a lifecycle chip so the state of every project is visible at a glance:
| Action | What it does |
|---|---|
| View | Opens the adaptation's page, the same one players see, so you can read your own listing the way they read it. |
| Rename | Changes the adaptation's display name in the picker and catalog. The new name rides along on your next upload. |
| Delete | Removes it. If it was published, players keep what they installed but stop receiving updates. |
| Status | Meaning |
|---|---|
| Published | A stable release is live in the catalog. |
| In review | Submitted for the Verified quality pass and awaiting a reviewer. |
| Draft | Not published yet, or published only as a beta so far. |
Deleting a published release is permanent. If it was the newest one, players fall back to your previous release; if it was the only one, they stop receiving updates entirely. If you just want to change something, rename or publish a new version instead; if you're stepping away, leaving it published costs nothing and keeps helping players.
After publishing, reviews start arriving, and they're worth reading: Ratings & reviews explains how players rate your work and how to turn harsh reviews into a better next version.