Scenes

Scenes are the entities that produce behavior in different parts of Decentraland. They can span multiple land parcels, and players walking through them in a World Explorer will execute special code provided by the scene.

You can find a complete real-life example in this scene’s manifest on the Foundation’s content server.

Pointers #

Scenes have one or more associated pointers in the form of parcel coordinate strings, such as "0,0". Every parcel running the scene will be listed in the pointers array of the entity manifest, and all those pointers will be resolved by the content server to that scene.

In other words, you can choose the x/y coordinates of a parcel and locate the scene it’s running by querying the content server for the "<x>,<y>" pointer. This is the way World Explorers decide whether to enable a scene’s behavior as the player navigates the world.

A typical pointers array looks like this:

{
  "pointers": [
    "-113,-134",
    "-113,-133",
    "-113,-132",
  ],
  // ... other entity properties
}

This data is also available in the metadata.scene.parcels field detailed below, in case you want to save only the scene-specific object in the manifest.

Metadata Fields #

There are several special properties for entities of type scene located in the metadata top-level field.

Display #

In metadata.display, you’ll find properties that are useful to inform players about the scene before they enter it.

An example:

{
  "title": "my_cool_scene",
  "favicon": "favicon.png",
  "navmapThumbnail": "thumbnail.png"
}

Scene #

The metadata.scene property is an object describing the position of this scene in the world map.

In practice, it looks like this:

{
  "parcels": [
    "17,-112", 
    "17,-113"
  ],
  "base": "17,-112"
}

The base field is always included in the parcels array.

Contact #

The metadata.contact object contains the contact information of the scene’s owner or maintainer.

In JSON:

{
  "name": "cool_scene_maker",
  "email": "[email protected]"
}

While the name field is filled in every scene, you’ll find that in actual practice the email field is often an empty string. This is a privacy choice made the scene’s creator.

Spawn Points #

The metadata.spawnPoints field defines an array of points and camera directions determining where players entering the scene should appear, and where they should be initially looking. There must be at least one defined spawn point.

Each item in the array has a number of properties:

For example:

[
  {
    "name": "spawn1",
    "position": { "x": 10.02, "y": 5.27, "z": 15.23  },
    "cameraTarget": { "x": 10.02, "y": 6.27, "z": 31.23 },
    "default": true
  }
]

Required Permissions #

In metadata.requiredPermissions you’ll find an array of well-known strings declaring which permissions should be asked from the player before the World Explorer allows certain actions. This is incumbent on the Explorer, on other clients built for different purposes may choose to ignore this.

This is the current set of supported permissions:

Feature Toggles #

The metadata.featureToggles field lets a scene indicate whether certain features of the World Explorer should be enabled or disabled.

The field contains an object of the form { [featureName]: 'enabled' | 'disabled' }, like this one:

{
  "voiceChat": "enabled"
}

Currently, voiceChat is the only commonly supported feature flag.