Geometry and performance budgets

The CLI and registry share a validator. The server reads the uploaded bytes and checks actual transformed vertices; it does not trust the CLI’s report or the bounds declared in a GLB accessor.

Each triangle primitive counts as a draw call. Repeated nodes count toward total drawn triangles and calls. Texture memory includes an estimated full mip chain. Embedded textures are limited to 4096 × 4096, and the decoded-memory limit still applies.

A package can contain at most 128 files, 32 MiB per file and 64 MiB total. Accounts currently allow 50 packages, 500 stored versions and 2 GiB of declared package storage. These limits apply to drafts too; remove unused unpublished versions to free space.

Fit the slot

World content stays inside a horizontal radius of 190 metres, above local y=0 and below y=480. Map and overview content stay inside radius 5.7, above y=0 and below y=14.4.

The slot is intentionally smaller than the host tile. The outer terrain band and boundary profiles belong to Threetopia. A tall building that fits the triangle budget can still fail the bounds check.

Common failures

• “Host tile is immutable”: restore tile.lock.json from your reservation or clone the package again. Do not edit its hash.
• “Geometry leaves its slot”: centre and scale the component, apply/export transforms, and check the lowest vertex.
• “Map exceeds draw calls”: merge meshes/materials and bake shared textures. One component can contain several recognizable objects, but it still has to fit the combined budget.
• “Use a self-contained GLB”: embed textures and buffers; do not reference external URLs.
• “Compressed or instanced accessors”: export an uncompressed validation-compatible GLB.
• Missing map/overview: both are mandatory for a world package, even if your detailed world already renders well.

Run threetopia check before upload. The server repeats the checks on threetopia push. A rejected draft is never publicly served as a published package.