tilemaps

Manage Phaser 4 tilemaps by loading JSON maps, creating layers, and configuring collisions.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/kehwar/pixi-square --skill tilemaps-kehwar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tilemaps
Source: https://github.com/kehwar/pixi-square/tree/main/.agents/skills/tilemaps
Command: npx skills add https://github.com/kehwar/pixi-square --skill tilemaps-kehwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tilemaps in Phaser 4 can be complex to set up and manage, requiring boilerplate to load maps, initialize layers, and configure collisions across orientations.

Core Features & Use Cases

  • Load Tiled JSON maps and create tilemap layers in Phaser 4.
  • Configure collisions, tile properties, and dynamic tiles across orthogonal, isometric, and hex layouts.
  • Use as a reference when prototyping or shipping a tile-based game, from loading maps to querying tiles during gameplay.

Quick Start

Load a Tiled JSON map and render a tile layer in a Phaser 4 scene, then enable tile collisions for gameplay.

Frequently Asked Questions about tilemaps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load a Tiled JSON map and enable tile collisions in a Phaser 4 scene?

To load a Tiled JSON map in Phaser 4, you import the map data, add the corresponding tilesets, and create tilemap layers. You then configure collisions by setting specific tile properties within the scene.

How do I perform dynamic tile operations and query tiles during gameplay in Phaser 4?

Dynamic tile operations in Phaser 4 involve using the Tilemap API to manipulate tile properties and query specific tile coordinates during gameplay. This allows real-time updates to the tilemap layers.

What is the best way to manage tilemap layers and coordinate utilities for game development in Phaser 4?

The best way to manage tilemap layers in Phaser 4 is using the Tilemap API to handle map data, initialize layers, and provide coordinate utilities. This reduces boilerplate when setting up tile-based game mechanics.

Why does setting up tile collisions across different map orientations require so much boilerplate in Phaser 4?

Setting up tile collisions across orthogonal, isometric, and hex layouts requires boilerplate because each orientation demands specific coordinate utilities and tile property configurations. Managing these distinct map formats manually increases code complexity.