Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
thedivergentai avatar

Godot Tilemap Mastery

  • 225 installs
  • 454 repo stars
  • Updated July 28, 2026
  • thedivergentai/gd-agentic-skills

Use godot-tilemap-mastery for development tasks

About

godot-tilemap-mastery: A skill for development. This provides functionality for development workflows.

  • godot-tilemap-mastery

Godot Tilemap Mastery by the numbers

  • 225 all-time installs (skills.sh)
  • +19 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #1,726 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/thedivergentai/gd-agentic-skills --skill godot-tilemap-mastery

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs225
repo stars454
Last updatedJuly 28, 2026
Repositorythedivergentai/gd-agentic-skills

What it does

Use godot-tilemap-mastery for development tasks

Files

SKILL.mdMarkdownGitHub ↗

TileMap Mastery

TileMapLayer grids, TileSet atlases, terrain autotiling, and custom data define efficient 2D level systems.

Available Scripts

tilemap_data_manager.gd

Expert TileMap serialization and chunking manager for large worlds.

terrain_path_painter.gd

Advanced runtime terrain autotiling (Terrains v2) for roads, rivers, and organic paths.

destructible_tile_logic.gd

Pattern for managing tile health and breakage based on Custom Data Layers.

gameplay_data_query.gd

Efficiently reading Custom Data (friction, hazards) to drive character/physics logic.

procedural_chunk_batcher.gd

Optimized procedural generation using bulk tile placement logic for better performance.

sorting_Z_layering.gd

Handling Y-sorting and Z-index layering for 2.5D effects and multi-floor buildings.

physics_shape_interaction.gd

Expert TileMap physics: handling one-way collisions and collision layer management.

nav_mesh_teleport_fix.gd

Runtime navigation updates for dynamic world-shifting and destructible environments.

tile_pattern_stamper.gd

Using TileMapPattern for efficiently "stamping" complex, multi-tile structural pieces.

fast_metadata_cache.gd

Optimization: caching TileData metadata for high-frequency gameplay queries.

tilemap_layer_v43_upgrade.gd

Managing the transition to the Godot 4.3 standard of multiple TileMapLayer nodes.

NEVER Do in TileMaps

  • NEVER use set_cell() in loops without batching — 1000 tiles × set_cell() = 1000 individual function calls = slow. Use set_cells_terrain_connect() for bulk OR cache changes, apply once.
  • NEVER forget source_id parameterset_cell(pos, atlas_coords) without source_id? Wrong overload = crash OR silent failure. Use set_cell(pos, source_id, atlas_coords).
  • NEVER mix tile coordinates with world coordinatesset_cell(mouse_position) without local_to_map()? Wrong grid position. ALWAYS convert: local_to_map(global_pos).
  • NEVER skip terrain set configuration — Manual tile assignment for organic shapes? 100+ tiles for grass patch. Use set_cells_terrain_connect() with terrain sets for autotiling.
  • NEVER use TileMap for dynamic entities — Enemies/pickups as tiles? No signals, physics, scripts. Use Node2D/CharacterBody2D, reserve TileMap for static/destructible geometry.
  • NEVER query get_cell_tile_data() in _physics_process — Every frame tile data lookup? Performance tank. Cache tile data in dictionary: tile_cache[pos] = get_cell_tile_data(pos).

---

Step 1: Create TileSet Resource

1. Create a TileMapLayer node 2. In Inspector: TileSet → New TileSet 3. Click TileSet to open bottom TileSet editor

Step 2: Add Tile Atlas

1. In TileSet editor: + → Atlas 2. Select your tile sheet texture 3. Configure grid size (e.g., 16x16 pixels per tile)

Step 3: Add Physics, Collision, Navigation

# Each tile can have:
# - Physics Layer: CollisionShape2D for each tile
# - Terrain: Auto-tiling rules
# - Custom Data: Arbitrary properties

Add collision to tiles: 1. Select tile in TileSet editor 2. Switch to "Physics" tab 3. Draw collision polygon

Using TileMapLayer

Basic Tilemap Setup

extends TileMapLayer

func _ready() -> void:
    # Set tile at grid coordinates (x, y)
    set_cell(Vector2i(0, 0), 0, Vector2i(0, 0))  # source_id, atlas_coords
    
    # Get tile at coordinates
    var atlas_coords := get_cell_atlas_coords(Vector2i(0, 0))
    
    # Clear tile
    erase_cell(Vector2i(0, 0))

Runtime Tile Placement

extends TileMapLayer

func _input(event: InputEvent) -> void:
    if event is InputEventMouseButton and event.pressed:
        var global_pos := get_global_mouse_position()
        var tile_pos := local_to_map(global_pos)
        
        # Place grass tile (assuming source_id=0, atlas=(0,0))
        set_cell(tile_pos, 0, Vector2i(0, 0))

Flood Fill Pattern

func flood_fill(start_pos: Vector2i, tile_source: int, atlas_coords: Vector2i) -> void:
    var cells_to_fill: Array[Vector2i] = [start_pos]
    var original_tile := get_cell_atlas_coords(start_pos)
    
    while cells_to_fill.size() > 0:
        var current := cells_to_fill.pop_back()
        
        if get_cell_atlas_coords(current) != original_tile:
            continue
        
        set_cell(current, tile_source, atlas_coords)
        
        # Add neighbors
        for dir in [Vector2i.UP, Vector2i.DOWN, Vector2i.LEFT, Vector2i.RIGHT]:
            cells_to_fill.append(current + dir)

Terrain Auto-Tiling

Setup Terrain Set

1. In TileSet editor: Terrains tab 2. Add Terrain Set (e.g., "Ground") 3. Add Terrain (e.g., "Grass", "Dirt") 4. Assign tiles to terrain by painting them

Use Terrain in Code

extends TileMapLayer

func paint_terrain(start: Vector2i, end: Vector2i, terrain_set: int, terrain: int) -> void:
    for x in range(start.x, end.x + 1):
        for y in range(start.y, end.y + 1):
            set_cells_terrain_connect(
                [Vector2i(x, y)],
                terrain_set,
                terrain,
                false  # ignore_empty_terrains
            )

Multiple Layers Pattern

# Scene structure:
# Node2D (Level)
#   ├─ TileMapLayer (Ground)
#   ├─ TileMapLayer (Decoration)
#   └─ TileMapLayer (Collision)

# Each layer can have different:
# - Rendering order (z_index)
# - Collision layers/masks
# - Modulation (color tint)

Physics Integration

Enable Physics Layer

1. TileSet editor → Physics Layers 2. Add physics layer 3. Assign collision shapes to tiles

Check collision from code:

func _physics_process(delta: float) -> void:
    # TileMapLayer acts as StaticBody2D
    # CharacterBody2D.move_and_slide() automatically detects tilemap collision
    pass

One-Way Collision Tiles

# In TileSet physics layer settings:
# - Enable "One Way Collision"
# - Set "One Way Collision Margin"

# Character can jump through from below

Custom Tile Data

Define Custom Data Layer

1. TileSet editor → Custom Data Layers 2. Add property (e.g., "damage_per_second: int") 3. Set value for specific tiles

Read Custom Data

func get_tile_damage(tile_pos: Vector2i) -> int:
    var tile_data := get_cell_tile_data(tile_pos)
    if tile_data:
        return tile_data.get_custom_data("damage_per_second")
    return 0

Performance Optimization

Use TileMapLayer Groups

# Static geometry: Single large TileMapLayer
# Dynamic tiles: Separate layer for runtime changes

Chunking for Large Worlds

# Split world into multiple TileMapLayer nodes
# Load/unload chunks based on player position

const CHUNK_SIZE := 32

func load_chunk(chunk_coords: Vector2i) -> void:
    var chunk_name := "Chunk_%d_%d" % [chunk_coords.x, chunk_coords.y]
    var chunk := TileMapLayer.new()
    chunk.name = chunk_name
    chunk.tile_set = base_tileset
    add_child(chunk)
    # Load tiles for this chunk...

Navigation Integration

Setup Navigation Layer

1. TileSet editor → Navigation Layers 2. Add navigation layer 3. Paint navigation polygons on tiles

Use with NavigationAgent2D:

# Navigation automatically created from TileMap
# NavigationAgent2D.get_next_path_position() works immediately

Best Practices

1. Organize TileSet by Purpose

TileSet Layers:
- Ground (terrain=grass, dirt, stone)
- Walls (collision + rendering)
- Decoration (no collision, overlay)

Available Scripts

MANDATORY: Read before implementing terrain systems or runtime placement.

terrain_autotile.gd

Runtime terrain autotiling with set_cells_terrain_connect batching and validation.

tilemap_chunking.gd

Chunk-based TileMap management with batched updates - essential for large procedural worlds.

2. Use Terrain for Organic Shapes

# ✅ Good - smooth terrain transitions
set_cells_terrain_connect(tile_positions, 0, 0)

# ❌ Bad - manual tile assignment for organic shapes
for pos in positions:
    set_cell(pos, 0, Vector2i(0, 0))

3. Layer Z-Index Management

# Background layers
$Background.z_index = -10

# Ground layer
$Ground.z_index = 0

# Foreground decoration
$Foreground.z_index = 10

Common Patterns

Destructible Tiles

func destroy_tile(world_pos: Vector2) -> void:
    var tile_pos := local_to_map(world_pos)
    var tile_data := get_cell_tile_data(tile_pos)
    
    if tile_data and tile_data.get_custom_data("destructible"):
        erase_cell(tile_pos)
        # Spawn particle effect, drop items, etc.

Tile Highlighting

@onready var highlight_layer: TileMapLayer = $HighlightLayer

func highlight_tile(tile_pos: Vector2i) -> void:
    highlight_layer.clear()
    highlight_layer.set_cell(tile_pos, 0, Vector2i(0, 0))

Expert TileMap Architectures

1. Isometric TileMap (Z-Sorting / Y-Sorting)

To master isometric rendering in Godot 4.x, configure the TileSet with TILE_SHAPE_ISOMETRIC. To ensure correct depth-sorting between tiles and dynamic entities (like players), enable y_sort_enabled on all TileMapLayer nodes and their mutual Node2D parent. Use y_sort_origin on TileData to precisely tune the sorting pivot for tall objects.

class_name IsometricMapOrchestrator extends Node2D
## Configures multiple TileMapLayers for isometric Y-sorting.

@export var ground: TileMapLayer
@export var objects: TileMapLayer

func _ready() -> void:
    # Enable global Y-sorting for this container.
    y_sort_enabled = true
    
    # Configure individual layers.
    ground.y_sort_enabled = true
    objects.y_sort_enabled = true
    
    # Optional: Offset the objects layer to fake height.
    objects.y_sort_origin = 16 

2. Procedural Generation (TileMapPattern Stamping)

For high-performance procedural generation, use TileMapPattern to store and "stamp" pre-fabricated tile structures. This is significantly faster than calling set_cell() in individual loops and preserves all tile identifiers (source_id, atlas_coords, alternative_tile) perfectly.

class_name TileStamper extends Node
## Efficiently stamps pre-fabricated patterns into a TileMapLayer.

@export var target_layer: TileMapLayer
var _house_pattern: TileMapPattern

func capture_pattern(coords: Array[Vector2i]) -> void:
    # Encapsulate a set of cells into a reusable pattern resource.
    _house_pattern = target_layer.get_pattern(coords)

func stamp_at(position: Vector2i) -> void:
    if _house_pattern:
        # Bulk-paste the pattern at the target coordinates.
        target_layer.set_pattern(position, _house_pattern)

3. Tilemap Diff (Layer Delta Merging)

To implement world-saving or destruction-syncing, calculate the "diff" between two TileMapLayer nodes. By iterating through get_used_cells(), you can identify discrepancies in source_id or atlas_coords and apply only the changes to a target layer, optimizing network or disk I/O.

class_name TileDiffManager extends Node
## Calculates and applies the delta between two TileMapLayers.

func apply_layer_diff(source: TileMapLayer, target: TileMapLayer) -> void:
    var source_cells := source.get_used_cells()
    
    for coord in source_cells:
        var s_id := source.get_cell_source_id(coord)
        var t_id := target.get_cell_source_id(coord)
        
        # If tiles differ, sync the target to the source.
        if s_id != t_id:
            var atlas := source.get_cell_atlas_coords(coord)
            var alt := source.get_cell_alternative_tile(coord)
            target.set_cell(coord, s_id, atlas, alt)

Reference

Related

  • Master Skill: godot-master

Related skills

Backend & APIsbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.