AutoBuild is ROOTWIN’s main assembler for Ren’Py games and mods. It is a desktop app (Python, CustomTkinter) written with TheOneTranslator, not against an imaginary “ideal” project. Assemblers already know the pain: files in the wrong folder, assets that never got optimized, a rebuild after a late translation drop that silently drops a sprite.

The point is not a magic one-click studio. The point is a repeatable scenario: launch the tool, get a result you can explain to the next person on the team.

What it is for

After a mod is ported (R-Migrator) and localized (RenDoki), someone still has to produce a playable package. That last mile is where mistakes hide. AutoBuild is meant to:

prepare a Ren’Py project for a build;
process and optimize assets;
catch missing files and broken layout;
support rebuilds after translation updates without starting from folklore;
match how TheOneTranslator actually ships work, not how a blog post says it should work.

How it grew

ROOTWIN showed TheOneTranslator an early assembler on 10 May 2026. A partnership agreement followed on 15 May. Joint development of AutoBuild started on 4 June. On 17 June we shipped 1.1 BEST — fewer bugs, a clearer install order — and published the first full Teletype deployment guide so a new assembler would not need a voice call for every step.

Two rounds of testing with TheOneTranslator (early June, then mid-June through 4 July) is what turned a useful script into something we were willing to document. On 4 September 2026, AutoBuild v1.2 was released featuring major bug fixes, asset handling optimization, and improved pipeline reliability.

Status

Still in active development. The current focus is stability, a faster pipeline, and cleaner asset handling for people who assemble mods every week, not once a year.

User guide

The full AutoBuild user guide covers the interface, modules, build flow, and common mistakes — worth reading before the first run.