Overview
Exports a tile map as a game-ready folder. Profiles: an image sequence (PNGs), a generic runtime bundle (atlas + tileset + map JSON), or Tiled (.tmj/.tsj + atlas). Writing is a staged → verified → atomically swapped transaction that never leaves a half-written folder.
Usage tips
pixpipeline_native_v1/tiled_v1takecanvas(the output oftile_studio);images_v1takesframesfromtile_canvas_animation_render.- The Inspector highlights inputs used by the selected profile:
framesforimages_v1, orcanvasplus optionaltile_palettefor native/Tiled output. - The authoritative spec for the native runtime format is
docs/contracts/tile-runtime-v1/README.md(coordinates, animation phase, half-open rects, …). Custom engines can read bundles against that contract. - Tiled assumes uniform cell-size tiles. Tiles larger than a cell (overhang) make the export fail with an error — nothing is silently transformed.
- The
reportoutput aggregates capability losses and warnings; review it whenever it is non-empty. - Any compile diagnostic with Error severity stops every profile before writing.
Warning and Info diagnostics remain in
reportwith severity, code, path, and cell.
Common pitfalls
- Tiled: "raster does not match the cell size" — a tile's image differs from the cell size. Re-bake the asset or use the native profile.
- images_v1 errors out — the
framesinput (List) is not connected.
Related nodes
tile_canvas_render/tile_canvas_animation_render— producing the inputstiled_map_export/tiled_tileset_export— existing single-JSON exports (kept for compat)