generate2dmap
Generate2dmap
Overview
Build the smallest playable map bundle that satisfies the game. Start by choosing a user-facing map_mode, then map it to the lower-level pipeline axes. Do not treat a map as only one image unless the user explicitly asks for a flat visual background.
map_mode:tile_mode|scene_mode|side_scroll_mode|grid_mode|room_chunk_mode|baked_scene_modevisual_model:baked_raster|layered_raster|tilemap|layered_tilemap|parallax_layersruntime_object_model:none|separate_props|platform_objects|y_sorted_props|interactive_scene_objects|foreground_occluders|scene_hookscollision_model:none|coarse_shapes|precise_shapes|tile_collision|polygon_walkmesh|trigger_zonesengine_target:raw_canvas|Phaser|Tiled_JSON|LDtk|Godot_TileMap|Unity_Tilemap| project-native
Use user-specified parameters when present. When the user does not specify them, infer the lightest playable pipeline from the existing game, camera, collision needs, map scale, and editing needs.
For requests that imply a playable game map, level, stage, room, prototype, or engine scene, do not ship a single baked image as the runtime map unless the user explicitly asks for a flat background only. A baked image may be a background, reference, or preview artifact, but the playable deliverable must expose gameplay geometry and objects as separate layers, props, tile/object data, collision, zones, or engine-native scene nodes.
This skill is for scenes and maps. Do not generate character, enemy, boss, projectile, NPC, player, or animation sprite assets as map deliverables. The map may include scene hooks such as player spawns, actor spawn marker metadata, patrol/encounter zones, arena entrances, gates, exits, and camera triggers, but actor artwork, projectiles, and animations belong in $generate2dsprite.
Read references/map-strategies.md when the pipeline choice is not obvious. Read references/layered-map-contract.md before implementing a layered raster map. Read references/prop-pack-contract.md before batching generated props into a sheet.