generate2dmap

Choose a map mode first, then generate a foundation-only base image with imagine_text_to_image, plan object placement with an in-world reference mockup, and produce separate props plus collision and placement metadata. A playable map is never a single baked image.

Generate the prop sheet on a solid #FF00FF magenta background, then run extract_prop_pack.py with the grid rows, columns, and labels. The script chroma-keys the background, isolates connected components, and writes per-prop PNGs plus a manifest.

Use side_scroll_mode for platformers, runners, brawlers, and Metroidvania rooms. It delivers scenery-only parallax layers on a shared stage_canvas, separate platform and hazard objects, collision data, scene hooks, and camera bounds.

Yes, engine_target supports raw_canvas, Phaser, Tiled JSON, LDtk, Godot TileMap, and Unity Tilemap. For this browser sandbox the default is raw_canvas or Phaser; engine-native exports are used only when explicitly requested.

Objects needing collision, y-sorting, interaction, reuse, or independent render order must remain separate runtime assets. Baking them into the base prevents editing and correct occlusion, so such images are regenerated or demoted to reference artifacts.

Use square prop packs only for four or more compact decorative props sharing one style. Wide platforms, tall buildings, gates, and collision-aligned objects must be generated one-by-one, as platform strips, or as custom wide packs.