---
title: Progress and Missions
description: "--- ###### Elements allows the creation of Missions, in which users can make progress that is tracked in their [User](https://namazustudios.com/glossary/user/) [Profile](https://namazustudios.com/glossary/profile/). Missions are structured tasks through which users can progress. Mission steps are tracked in the [User](https://namazustudios.com/glossary/user/)'s progress. Common use…"
url: "https://namazustudios.com/docs/namazu-elements-core/progress-and-missions/"
updated: "2026-08-13"
category: Namazu Elements Core Features
---

# Progress and Missions

---

###### Elements allows the creation of Missions, in which users can make progress that is tracked in their [User](https://namazustudios.com/glossary/user/) [Profile](https://namazustudios.com/glossary/profile/).

Missions are structured tasks through which users can progress. Mission steps are tracked in the [User](https://namazustudios.com/glossary/user/)'s progress.

Common use cases for missions are a game's level structure or a game's achievements. Missions also allow for the [User](https://namazustudios.com/glossary/user/) to earn rewards when steps are completed.

Missions serve as definitions. When a [User](https://namazustudios.com/glossary/user/) begins his first mission, a copy of that mission definition is made in the progress attached to that [User](https://namazustudios.com/glossary/user/)'s [Profile](https://namazustudios.com/glossary/profile/) for that [Application](https://namazustudios.com/glossary/application/). The progress will then record the [User](https://namazustudios.com/glossary/user/)'s step completion, as well as rewards issued for step completion.

Warning

A limitation of the current system is that when a mission definition is copied to the progress, it is locked in the state it was defined at that time. So, if developers modify that mission after progress is saved by an [User](https://namazustudios.com/glossary/user/), existing users who have started that mission won't see the changes - only users who have not yet started the mission will.

This section will guide you on how to interact with the progress and missions APIs.

### Mission Structure [#mission-structure](#mission-structure)

Missions contain an arbitrary number of steps, followed by a single (optional) final repeat step. As the [User](https://namazustudios.com/glossary/user/) of your [Application](https://namazustudios.com/glossary/application/) progresses through a mission, they will go through the steps in sequence.

Once all steps are completed, if there is a final repeat step, that step can be repeated again an unlimited number of times.

For example, you can use the steps for a tiered set of achievements to be completed in sequence, each step with its own set of rewards:

- Collect 5 Stars
- Collect 10 Stars
- Collect 20 Stars

#### Mission [#mission](#mission)

- **[name](https://namazustudios.com/glossary/name/):** This is a string representing the [name](https://namazustudios.com/glossary/name/) of your mission. It must be unique and have no spaces.
- **tags:** You may include a list of tags as strings. Tags are an easy way to search for groups of missions or sort them among your applications.
- **displayName:** This is a string representing your mission's display [name](https://namazustudios.com/glossary/name/).
- **description:** This is a string that serves as a description for your mission.
- **steps:** Here, all the steps of the mission are represented. Steps have their own structure that is [detailed below](#mission-step), with their own corresponding fields.
- **finalRepeatStep:** This is the optional final repeat step of the mission, which has a similar structure to an individual step.
- **[Metadata](https://namazustudios.com/glossary/metadata/):** [Metadata](https://namazustudios.com/glossary/metadata/) is optional. It can include any number of named strings or integers. [Metadata](https://namazustudios.com/glossary/metadata/) can have many uses. For example, secondary descriptions, asset paths, types, or any arbitrary values assigned to your mission.

#### Mission Steps [#mission-step](#mission-step)

Mission steps define the actual content of the mission. The final repeat step has a structure identical to any other step.

- **displayName:** This is a string representing your mission's display [name](https://namazustudios.com/glossary/name/).
- **description:** This is a string that serves as a description for your mission.
- **count:** This is an integer that defines how many times an action has to be executed for the step to be completed. For example, if the mission step was "collect 20 stars," you might have you [Application](https://namazustudios.com/glossary/application/) increment the [User](https://namazustudios.com/glossary/user/)'s progress on this step each time a star is collected, and then the step would be completed when the threshold is reached.
- **rewards:** Here, the rewards are what the player earns for the completion of the steps that are listed. Rewards are [items](../digital-goods#items) accompanied by a quantity.
- **[name](https://namazustudios.com/glossary/name/)**: A string naming the [Item](https://namazustudios.com/glossary/item/) reward. This must match the unique [name](https://namazustudios.com/glossary/name/) of a defined [item](../digital-goods#items).
- **quantity**: This is an integer determining how many of each [item](../digital-goods#items) will be rewarded.
- **[Metadata](https://namazustudios.com/glossary/metadata/):** [Metadata](https://namazustudios.com/glossary/metadata/) is optional. Steps can have their own [Metadata](https://namazustudios.com/glossary/metadata/) separate from the overarching mission. It can be any number of named strings or integers. [Metadata](https://namazustudios.com/glossary/metadata/) can have many uses. For example, secondary descriptions, asset paths, types, or any arbitrary values assigned to your mission step.

In the database, the mission will also have an **_id** field. This is automatically generated when the mission is created and serves as an internal reference for that mission.

### Managing Missions Using the Console [#managing-missions-using-the-console](#managing-missions-using-the-console)

Missions are managed in the Missions section of the admin console, which can be accessed from the upper nav bar or in the hamburger menu.

The "Add Mission" button will open the new [Item](https://namazustudios.com/glossary/item/) panel.

Missions can be edited by tapping the *Edit* button next to that mission or they can be deleted by tapping the *Delete* button. Use the search function to easily find specific missions.

![](https://namazustudios.com/wp-content/uploads/2025/08/mission_editor.png)
Mission Editor

#### Editing Mission [Metadata](https://namazustudios.com/glossary/metadata/) [#editing-mission-metadata](#editing-mission-metadata)

Mission [Metadata](https://namazustudios.com/glossary/metadata/) is edited identically to how [Item](https://namazustudios.com/glossary/item/) [Metadata](https://namazustudios.com/glossary/metadata/) is edited. See [Editing Item Metadata](../digital-goods#editing-item-metadata).

#### Editing Mission Steps [#editing-mission-steps](#editing-mission-steps)

Use the *Add Step* button to create a new step.

Step content can be displayed or hidden with the dropdown button on the right side of the header. If you have multiple steps, they can easily be reordered by dragging them in the list from the handle icon on the left of the header.

Step rewards are added by naming the reward [Item](https://namazustudios.com/glossary/item/) and adding a quantity, then using the "+" button to add additional rewards. [Item](../digital-goods#items) names must be items that exist in your Elements instance.

Step [Metadata](https://namazustudios.com/glossary/metadata/) is edited just like general mission [Metadata](https://namazustudios.com/glossary/metadata/), or [item metadata](../digital-goods#editing-item-metadata).

Use the *Delete Step* button to delete the step.

Toggling the *Final Repeat Step* checkbox will set that step as the final repeat step and automatically move it to the end of the sequence.

![](https://namazustudios.com/wp-content/uploads/2025/08/Screenshot-2025-08-11-at-10.49.57-AM-1024x898.png)

Mission Step Editor

#### JSON Structure of Missions [#json-structure-of-missions](#json-structure-of-missions)

This is a sample mission represented in JSON.

```
[{
  "name": "missionName",
  "tags": ["tag1", "tag2", "tag3"],
  "displayName": "Mission Name",
  "description": "This is the mission's description",
  "steps": [
    {
      "displayName": "Step Name 1",
      "description": "This is step 1's description",
      "count": 1,
      "rewards": [
        {
          "item": {
            "name": "itemName"
          },
          "quantity": 1
        }
      ],
      "metadata": {
        "metadata_string": "this is a string",
        "metadata_int": 1
      }
    },
    {
      "displayName": "Step Name 2",
      "description": "This is step 2's description",
      "count": 1,
      "rewards": [
        {
          "item": {
            "name": "itemName"
          },
          "quantity": 1
        },
        {
        "item": {
          "name": "itemName2"
        },
        "quantity": 1
      }
      ],
      "metadata": {
        "metadata_string": "this is a string",
        "metadata_int": 1
      }
    }
  ],
  "finalRepeatStep": {
    "displayName": "Repeat Step Name",
    "description": "This is the repeat step's description",
    "count": 1,
    "rewards": [
      {
        "item": {
          "name": "itemName"
        },
        "quantity": 5
      }
    ],
    "metadata": {
        "metadata_string": "this is a string",
        "metadata_int": 1
    }
  },
  "metadata": {
    "metadata_string": "this is a string",
    "metadata_int": 1
  }
}]
```

Note

The **_id** field for the mission is not included in the above example. If you were to use a script to batch upload/update missions, your JSON would look like the above example. The **_id** field would not be included since that is autogenerated.

Looking directly in the database, you'll notice that the rewards for a step are listed as below, using the object [id](https://namazustudios.com/glossary/id/) for the [Item](https://namazustudios.com/glossary/item/) rather than its [name](https://namazustudios.com/glossary/name/).

```
"rewards" : [
            {
                "item" : {
                    "$ref" : "items",
                    "$id" : ObjectId("5cdb1204c44033001a6a2908")
                },
                "quantity" : 50
            }
            ]
```