AutoTiler

Component that automatically processes tilemap tiles to apply auto-tiling rules. Auto-tiling analyzes neighboring tiles and replaces them with appropriate variants to create seamless connections and transitions.

The AutoTiler supports multiple auto-tiling algorithms (EDGE_16, EDGE_CORNER_32, EXPANDED_47, etc.) and can handle complex tile arrangements including:

• Edge connections (straight borders)
• Corner pieces (diagonal connections)
• Overlapping tiles for detailed transitions
• Custom tile mappings for different tileset standards

Usage Example: #

// Define auto-tiles for grass terrain
var grassAutoTile = {
    kind: EXPANDED_47,
    gid: 10,  // Base grass tile GID
    bounds: true  // Connect with map edges
};

// Create auto-tiler
var autoTiler = new AutoTiler([grassAutoTile]);

// Add to tilemap layer
tilemapLayer.component(autoTiler);

The component automatically updates when the layer's tiles change, recomputing auto-tiling for affected areas.

Static Members #

Static lookup table mapping 8-bit masks to tile indices for EDGE_CORNER_32 auto-tiling. The mask encodes which edges and corners connect to matching tiles. Built lazily on first access.

Static lookup table for EXPANDED_BOTTOM_CORNER_26 auto-tiling. Maps 47-tile indices to their 26-tile equivalents, removing top corners. Built lazily on first access.

Static lookup table for TILESETTER_BLOB_47 tile positions. Maps tile indices to X,Y offsets in the Tilesetter blob layout. Built lazily on first access.

Inverted lookup table for EDGE_CORNER_32 mapping. Maps tile indices back to their 8-bit mask values. Built lazily on first access.

Validates whether a given edge/corner combination is valid for EDGE_CORNER_32 tiling.

Rules enforced:

• If all corners are present, all edges must also be present
• A corner can only exist if both adjacent edges are present (e.g., top-left corner requires both left and top edges)

This validation ensures visually correct tile connections without impossible configurations like floating corners.

Instance Members #

The tilemap layer data this auto-tiler processes. Automatically bound when added as a component to a TilemapLayerData entity.

Read-only array of auto-tile configurations. Each auto-tile defines a GID and algorithm for processing tiles.

Creates a new AutoTiler with the specified auto-tile configurations.

Private Members #

Internal map for fast lookup of auto-tiles by their GID. Built during construction from the autoTiles array.

Event fired when a single tile is computed during auto-tiling. Useful for custom post-processing or debugging tile placement.

Event fired after all tiles have been computed but before they are applied to the layer. Allows for final adjustments to the tile array.

Called when this auto-tiler is bound as a component to a TilemapLayerData. Sets up event listeners and performs initial auto-tiling computation.

Handles changes to the layer's tile data. Automatically recomputes auto-tiling when tiles are modified.

Core auto-tiling computation method. Analyzes each tile in the layer and applies appropriate auto-tiling transformations based on neighboring tiles.

The algorithm:

1. Iterates through each tile position
2. Checks if the tile matches any auto-tile rule
3. Examines neighboring tiles (4 cardinal + 4 diagonal)
4. Computes edge and corner masks based on matches
5. Selects appropriate tile variant from the tileset
6. Handles overlapping tiles for detailed transitions

Metadata #