# Glossary

### Metaverse

Metaverses in Otherside are creatively autonomous yet interoperable. They are groups of virtual worlds that exist as part of the broader interoperable M² network.

The metaverse is M²'s unit of organisation. Every M² virtual world is part of a particular metaverse, and each metaverse has separate access control, billing, etc.

Each metaverse has its own URL based on its codename:

> **\<codename>.m2worlds.io**

### Dashboard

The dashboard is the entry point to both metaverses and tools. It is how developers and other metaverse operators interact with the M² network. From here:

* Admins can manage access across the metaverse, handle billing, and additional configuration
* Developers can download the editor, and launch virtual worlds that are made from it
* Event runners can run events in virtual worlds using content uploaded by developers

You can find your metaverse's dashboard based on your `organization id`:

> **https\://{organization-id}.m2worlds.io/dashboard**

**For example:**

* Construct's dashboard is [https://construct.m2worlds.io/dashboard](#m)

### Worlds

Worlds are single instanced virtual spaces, individually capable of up to \~10ks CCUs. Worlds are launched by clicking `Launch` in the header and involve selecting a map (from a mod), runtime, size (how many players can it handle), and more.

<figure><img src="/files/OHxRq8uGpyVEuLiXBLsB" alt=""><figcaption><p>Configure a world to launch</p></figcaption></figure>

Standard worlds will be deleted after the duration of the world has ended. If this is not your desired outcome, you can set up persistent or always on worlds.

[Persistent worlds](https://docs.msquared.io/production/starting-worlds/persistent-worlds) - Worlds that always exist, but are not always on. By setting up persistent worlds for events, the creator will not have to remake or reconfigure access groups, live config, links, events, and any other world state already configured.

[Always on worlds](https://docs.msquared.io/production/starting-worlds/how-to-make-an-always-on-world) - An extension of persistent worlds that are set up without a duration end time.

### Mods

Mods are developer-uploaded Unreal projects that can be used to start worlds. Each developer gets their own mod which is automatically created for them the first time they click upload in the editor. All future uploads will be part of the same mod. When starting a world, you always select a mod (and a map within that mod) to run. By default, only the mod creator (and admins) can use a given mod to launch worlds.

Mods can be viewed in the `Mods` tab of the dashboard. Below, you can see the `ally's game` mod, and a history of the 14 different versions of it that have been uploaded.

<figure><img src="/files/pF7jm8L43G3CSzXowgLV" alt=""><figcaption><p>Mod list</p></figcaption></figure>

### Events

Events are a dedicated concept for engagement of users into a running world. You can create an event to advertise your metaverse events ahead of time using them as placeholders on your end user website with calendar links, YouTube trailers, and more. At show time, you can link the event to a running world to connect users into a world based on your content.

<figure><img src="/files/BAGlqcAzcDpdcwuhxeki" alt=""><figcaption></figcaption></figure>

### Projects

[Projects](https://docs.msquared.io/admins/projects) are isolated sections of a metaverse which let you separate groups of content, worlds, and people developing within your metaverse.

### Editor

The M² editor is an extended Unreal Editor including plugins for creating worlds with high-scale rendering/networking/audio, MML, interoperable objects, avatars, and tooling to upload to our content pipeline.

<figure><img src="/files/wGGVNv7StXZe9Ic6QISZ" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.otherside.xyz/platform-documentation/morpheus-platform/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
