# Terrain World Compiler release — 2026-10-06

- [Ready-to-run Linux x86_64 build](terrain-world-compiler-1.1.0-linux-x86_64-ready-to-run-2026-10-06.tar.gz)
- [Complete source + examples](terrain-world-compiler-1.1.0-source-examples-2026-10-06.tar.gz)
- [SHA-256 checksums](SHA256SUMS.txt)
- [Validation record](VALIDATION.json)

Compiler version 1.1.0. The standalone build includes Python 3.12.3 and runtime libraries; no Python installation, pip setup or internet connection is needed. It targets Linux x86_64 with glibc 2.38 or newer, checked on Pop!_OS 24.04 LTS. It is also already extracted under ready-to-run/terrain-world-compiler-linux-x86_64/.

Extract the build and enter its application directory, then run ./launch.sh for terminal prompts, or:

```sh
./terrain-world-compiler compile --layout examples/layout.json --output generated/two-map-demo
./terrain-world-compiler validate --input generated/two-map-demo
```

Keep the _internal/ folder beside the executable. The release includes four real input ZIPs, usable two-/four-map layouts, all three existing compiled examples and existing terrain previews. The source archive contains the application, tests, schemas, documentation, original example inputs/outputs, reference images, a standalone build recipe and dependency notices. Original source and example data were preserved unchanged; the extra four-map-demo.json layout points at the included ZIPs.

All focused native checks passed: clean-environment startup, CLI help/version, shell and interactive terminal launchers, validation of all three existing example packages, tiny synthetic v1/v2 compilations, normalized water coverage and refusal to overwrite outputs. Compilations used disposable data; existing user worlds were copied and validated without regeneration. Other operating systems/distributions and interactive 3JHV viewing were not checked.

Every archive was read back and checked for complete member lists, SHA-256 file contents, executable permissions and safe internal symlinks. Original source copies, schema data, input ZIPs and preserved compiled examples were compared against their sources. Per-file manifests are inside both archives. Use sha256sum -c SHA256SUMS.txt for download integrity.