deploy-worlds

Deploy Decentraland SDK7 scenes to Worlds using a DCL NAME or ENS domain.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/ansonj-dev/neon-reverse --skill deploy-worlds-ansonj-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-worlds
Source: https://github.com/ansonj-dev/neon-reverse/tree/main/agent/skills/deploy-worlds
Command: npx skills add https://github.com/ansonj-dev/neon-reverse --skill deploy-worlds-ansonj-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing a Decentraland scene to a personal World requires correct worldConfiguration in scene.json, NAME or ENS ownership, storage budget awareness, and the right deploy target, and mistakes in any of these cause failed or invisible deployments. ## Core Features & Use Cases - World Configuration: Guides setup of worldConfiguration in scene.json, including name, placesConfig opt-out, skyboxConfig.fixedTime, and discovery metadata like title, description, tags, and thumbnail. - Deployment Workflows: Covers the /deploy command, CLI deployment to the Worlds content server, Creator Hub publishing, and multi-scene Worlds with collaborators. - Troubleshooting & Storage Budget: Explains the dynamic storage budget from NAMEs, LAND, and MANA holdings, plus fixes for common errors like NAME ownership mismatches and oversized scenes. - Use Case: A creator finishes a multiplayer scene and wants it live at my-name.dcl.eth; this Skill walks through configuring scene.json, verifying the storage budget, deploying, and confirming the World appears on Places. ## Quick Start Deploy my Decentraland scene to my World at my-name.dcl.eth and configure scene.json with the right worldConfiguration and discovery metadata.

Frequently Asked Questions about deploy-worlds

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

FAQPage Schema
How do I deploy a Decentraland scene to a World?

Add a worldConfiguration section with your NAME to scene.json, then run the /deploy command or npx @dcl/sdk-commands deploy with the Worlds content server target. The wallet signing the deployment must own the NAME or have ACL permission.

What is the difference between deploying to a World and Genesis City LAND?

Worlds require a Decentraland NAME or ENS domain instead of LAND ownership, have no parcel limitations, and use a different deploy target content server. Worlds are also automatically listed on the Places page unless you opt out via placesConfig.

How much storage do I get for a Decentraland World?

Each Decentraland NAME grants 100 MB, each LAND parcel adds 100 MB, and every 2,000 MANA held adds another 100 MB, shared across all your Worlds. ENS-domain Worlds have a fixed 36 MB limit that cannot be expanded.

Why does my World deployment fail with NAME not found?

This error means the wallet signing the deployment does not own the NAME or ENS domain in worldConfiguration.name. Verify ownership at builder.decentraland.org/names and ensure the signing wallet owns the exact NAME.

Can a World host multiple scenes at different coordinates?

Yes, enable Multi-Scene World when publishing in Creator Hub or deploy with the --multi-scene CLI flag. The World owner can then add collaborators with deploy rights and manage the layout via the Layout tab in World Settings.

Why does Places still show my old World description after publishing?

World metadata and scene metadata are stored separately. In single-scene Worlds every publish overwrites World metadata from the scene, so edit the scene settings; in multi-scene Worlds edit metadata in the Creator Hub Manage tab.