Decentraland LAND gives your first scene a place in Genesis City

Choose access that matches the building job

Publish on a parcel you own

Ownership provides control over the parcel asset and its deployment permissions. This suits a project where you want to retain control of the location. Keeping the scene project also matters: the editable build and the parcel token serve different purposes.

Assign a content operator

An owner can give another account permission to deploy content without giving it the ability to sell the token. That permission also allows changes to the parcel’s name or description. It’s appropriate for commissioning a build, although the operator’s ability to replace public content remains a meaningful responsibility.

Use a rental for temporary access

A rental grants deployment access under the rental’s terms. The tenant selects the operator address and can change it later. This separates the account arranging the rental from the account doing the publishing. Confirmed rental access supports a temporary installation without requiring a parcel purchase.

Fit the project to its parcel footprint

A scene’s available shape follows its selected parcels. A single LAND parcel measures 16 meters by 16 meters. Larger scenes need adjacent parcels, and their arrangement determines the usable footprint. Extra area elsewhere on the map doesn’t extend the space around a particular build.

Content outside the boundaries won’t render beyond them. Preview highlights those protrusions, which makes it useful for spotting an oversized roof or misplaced display. Resource constraints require separate attention: file size and file count limits can block deployment, while rendering limits appear as performance warnings. Creator Hub displays resource usage for the scene.

Passing upload checks doesn’t establish smooth performance on every visitor’s device.

Give a display space something visitors can inspect

A gallery or exhibition uses the parcel as a location for arranged visual content. Models and image displays provide the presentation; interactive components determine what visitors can do with it. A small, readable installation can serve this job without occupying a large Estate.

The Scene Editor includes an NFT smart item for displaying an NFT image in a frame. This is a display function. It doesn’t by itself create a purchase interaction or transfer the displayed asset. Keep the first installation’s purpose clear: viewing artwork, reading an explanation, and buying an asset require different behavior.

Connect visitor input to visible behavior

Clicks need a reachable target

Interactive objects need both a trigger and an action. A button can activate another item, while a door can respond directly to a click. Custom models also need suitable collision geometry for pointer interaction; an attractive model alone doesn’t establish a clickable surface.

Another object’s collider can intercept the pointer even when its visible shape seems clear. Troubleshooting should therefore distinguish a missing action from an unreachable target. Sound, animation, or an obvious state change helps visitors recognize a successful interaction.

Entry areas react to movement

A Trigger Area responds when a player enters or leaves its volume. Its editable cube becomes invisible during play. Conditions can restrict when its actions run, making it useful for automatic entrances or interactions tied to an existing scene state. The trigger volume and the visible object needn’t have the same shape.

Place arrivals where visitors can move

A direct arrival needs a spawn position inside the scene’s parcels and clear of obstructing objects. A doorway that works for someone approaching on foot doesn’t establish a usable teleport arrival. Furniture, raised terrain, and stairs can interfere with the initial position.

Spawn settings also control the visitor’s initial viewing direction. A clear arrival facing the main installation helps the scene communicate its purpose immediately. Multiple spawn areas support different arrival positions, but each needs usable space around it.

Publish to the coordinates the project actually occupies

Deployment connects the scene’s content to its destination parcels. Creator Hub’s LAND publishing flow distinguishes parcels where the connected account has deployment permission. A local preview alone doesn’t prove that account can publish to the intended location.

The publication details need to match the project’s footprint. A multi-parcel scene requires permission across its destination, rather than permission for only its entrance parcel. Scene metadata supplies visitor-facing information such as the title, description, and thumbnail.

An uploaded build still needs to load correctly in the client. Model processing can delay visible readiness after publication, so a successful submission and a playable installation are different observations. Avoid scheduling the first public visit around an immediate last-minute deployment.

Keep project files separate from public content

Published scene assets reach content servers so clients can download and render the experience. Deployment therefore needs a deliberate file selection. Credentials and unrelated private documents don’t belong among files intended for visitors’ clients.

The deployment tooling supports an exclusion file named .dclignore. Review the upload contents before authorization, and retain the editable project separately. Excluding a file is appropriate only when the deployed scene doesn’t need it. A missing texture or audio file can leave an otherwise valid build incomplete.

Add event functions after the space works

If a gathering includes video or other programmed activity, the scene needs the components that run it. Owning the location doesn’t supply those functions. The Video Player smart item supports prerecorded video and streams, with playback controlled through configuration or scene interactions.

Media introduces its own performance demands. Several different videos playing together can burden the client, and playback limits depend on the visitor’s quality settings. Starting media near the visitor or through interaction avoids unnecessary playback while the scene sits in the distance.

A first venue fits LAND well when its map location and spatial experience matter. A project concerned only with testing a media component can remain in preview until the component works.