Key Concepts

This page covers Platform Module, Artifact, World, Manifest, Config, and Registry.

Morpheus Platform is build in extendable way: not only Morpheus team can add features, but also other developers. Moreover, these features can be made available to a specific Universe, that is, to a specific client of Morpheus. Thus, each of the clients can have their own metaverse full of bespoke features, objects, and environments.

Platform Modules

Platform Modules (=Modules) is the overarching concept for any feature or feature set with which the Morpheus Platform is extended. Core features of Morpheus Platform as Voice and Media support, Social and In-app Creator features are organised in Modules, at least conceptionally.

Platform Module comprises one for more interactive objects and environments.

Anything (except plain media) that Content Creators would like to upload to Morpheus, needs to be packaged into a Module. Upcoming Morpheus Marketplace will operate with Modules as well: clients of Morpheus would be able to install different Modules to their metaverse or purchase a license which will result in payout to all Creators who contributed to the Module.

We have several built-in modules which are bundles of Morpheus’ core features: Voice, Media, Decorator, Social, Portals.

Worlds — Interactive Environments

Each Place in the Morpheus Metaverse hosts one or several Worlds which are interactive environments for visitors to arrive, walk about, and interact with.

To create a World, a Content Creator must first create a Unity Bundle with Geometry Data and upload it via Admin Portal to a particular Universe. Then the World will be available in Places of that Universe. The process is described in detail in the corresponding section of For Content Creators.

For the purpose of the Marketplace, Worlds should be packaged into Modules and provided with a Module Manifest.

Worlds can be made interactive, that is contain certain features that players can activate by coming closer, by touching or pointing at. See the section For Content Creators for details.

Artifacts — Interactive Objects

Besides interactive environments, Morpheus Platform allows creation of interactive objects called Artifacts. These object can be either held in users’ hands (e.g., microphones) or placed somewhere in the world (e.g. mirrors).

Similar to Worlds, to create an Artifacts, a Content Creator must first create a Unity Bundle with Geometry Data and upload it via Admin Portal to a particular Universe. Then the Creator must create an Artifact Manifest which describes certain properties of the Artifact, e.g., its name or if it can be worn. The process is described in detail in the corresponding section of For Content Creators.

Artifacts are made available in the Places that are configured to enable spawning certain Artifact. For details, see Modules in Places section.

Module Manifest

Module Manifest is a simple text file in JSON or YAML format that describes a particular Artifact, World, or set of those. Below is a very simple example of a Module Manifest which describes a module with two Artifacts:

assetId: asset.morpheusxr.car
name: Car
meta:
  preview: https://storage.googleapis.com/xmorpheus-public-assets/artifacts/previews/v2/car.png
contents:
  - artifact:
      id: car.ford
      data: data.uZ_dpln_mTUK3IGmeb46H.JOmjpVD5l-eEYrzAkvAUQ
  - artifact:
      id: car.bmw
      data: data.onveouruohpfpp9gfwpwi.orvouqv90ar9e0pf97vgr

Each Module Manifest contains one or more Artifact, World, and Avatar Manifests. For further details on Manifests, please read Module Manifests.

Module Config

Module Config is a simple text file in JSON or YAML format which follows the Module Manifest structure. Effectively, a Module Config is an override of the Module Manifest with the same assetId or moduleId.

Configs can override Modules completely or partially. Here is an example of a Config that overrides the Module’s example found above. This Config instructs the platform to use only one Artifact.

assetId: asset.morpheusxr.car
name: Ford Car
contents:
  - artifact:
      id: car.ford
      data: data.uZ_dpln_mTUK3IGmeb46H.JOmjpVD5l-eEYrzAkvAUQ

To be used in a particular Place, Platform Modules must be configured by Module Config which is the uploaded in one of the Content Folders of the Place (same folders that are used in Media Module). Artifacts then become spawnable in-app. Starting from Release 6, Worlds will also be configured from the modules. Starting from Release 7, so will do Avatars.

Module Configuration is described in details in the namesake section.

Module Registry

Module Registry is a list of Module Manifests which can be configured to be used in Places of a particular Universe. Each Universe has its own Module Registry thus allowing for bespoke modules: the content that is only available in the metaverse of a certain Client.

There are also Core Module Registries curated by Morpheus. Adding a Module Manifest to such registry makes its module available in all Universes.

More is found in Module Registry section.

Last updated