deploy-worlds

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

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/stom66/dcl-bowling --skill deploy-worlds-stom66
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy-worlds
Source: https://github.com/stom66/dcl-bowling/tree/main/agent/skills/deploy-worlds
Command: npx skills add https://github.com/stom66/dcl-bowling --skill deploy-worlds-stom66

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing a Decentraland scene to a personal World requires correct scene.json configuration, NAME or ENS ownership, storage budget awareness, and a different deploy target than Genesis City, and mistakes in any of these cause failed or rejected deployments. ## Core Features & Use Cases - World Configuration: Add and validate the worldConfiguration section in scene.json, including Places opt-out, discovery metadata, and skybox fixed-time settings. - Deployment Guidance: Deploy via the /deploy command, CLI with the Worlds content server target, or the Creator Hub publish flow, including multi-scene Worlds and collaborator access. - Troubleshooting: Resolve common failures such as NAME ownership errors, storage budget overruns, and Worlds not appearing on Places. - Use Case: A creator owns my-name.dcl.eth and wants to publish a social hangout scene; this Skill walks through configuring scene.json, checking the storage budget, deploying, and sharing the visit URL. ## Quick Start Deploy my Decentraland scene to my World at my-name.dcl.eth and configure scene.json for it.

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 or ENS domain to scene.json, then run the /deploy command or npx @dcl/sdk-commands deploy with the Worlds content server target. The signing wallet must own the NAME or have ACL permission.

What is the difference between deploying to Worlds and Genesis City?▼

Worlds are personal spaces requiring a Decentraland NAME or ENS domain instead of LAND parcels, with no parcel limitations. They deploy to a different content server and are automatically listed on the Places page unless opted out.

How much storage do Decentraland Worlds get?▼

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 Worlds in the wallet. ENS-domain Worlds have a fixed 36 MB limit.

Why does my World deployment fail with NAME not found?▼

The wallet signing the deployment does not own the NAME or ENS domain specified in worldConfiguration.name. Verify ownership at builder.decentraland.org/names and ensure the exact NAME matches.

Can a World host multiple scenes at different coordinates?▼

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

How do I hide my World from the Decentraland Places page?▼

Set placesConfig.optOut to true inside the worldConfiguration section of scene.json before deploying. Without this flag, all Worlds are automatically listed on the Places page.