What problem does it solve? Testing a Decentraland SDK7 scene normally requires manual launching, walking, and eyeballing of the Explorer client. This Skill automates that loop: it connects to the Explorer's embedded MCP server, hot-reloads edited scene code, moves the player and camera, captures screenshots, and reads scene state and logs so changes can be verified in-world without manual playtesting. ## Core Features & Use Cases - In-world iteration loop: Edit scene TypeScript, watch it hot-reload, then verify with get_scene_state, get_scene_logs, and screenshots from retail camera modes. - Player and camera automation: Teleport, walk, look at targets, switch camera modes, click entities, send chat, and trigger emotes to exercise gameplay behavior. - Performance and budget measurement: Use get_scene_content_stats, get_scene_content_breakdown, and get_performance_stats to correlate scene content with measured frame rates. - Use Case: After adding a trigger area to a bowling lane scene, reload the scene, walk the player into the trigger, screenshot the result, and confirm via ECS state reads that the event fired — all without touching the client manually. ## Quick Start Ask the assistant to launch the scene with the MCP flag and verify the current scene in the running Decentraland Explorer, then iterate on any reported issues.
