--- title: Metadata (3.4+) description: "This page explains how to **create**, **modify**, and **delete** [Metadata](https://namazustudios.com/glossary/metadata/) and [Metadata](https://namazustudios.com/glossary/metadata/) schemas in the Namazu Elements Management Console. --- ## Overview **[Metadata](https://namazustudios.com/glossary/metadata/)** in Namazu Elements are arbitrary **JSON objects** that can be used to **remotely configure your game client**.…" url: "https://namazustudios.com/docs/namazu-elements-core/metadata-3-4/" updated: "2026-08-13" category: Namazu Elements Core Features --- # Metadata (3.4+) This page explains how to **create**, **modify**, and **delete** [Metadata](https://namazustudios.com/glossary/metadata/) and [Metadata](https://namazustudios.com/glossary/metadata/) schemas in the Namazu Elements Management Console. --- ## Overview **[Metadata](https://namazustudios.com/glossary/metadata/)** in Namazu Elements are arbitrary **JSON objects** that can be used to **remotely configure your game client**. They allow you to adjust gameplay parameters, feature toggles, or live event settings without requiring a new game build. Each [Metadata](https://namazustudios.com/glossary/metadata/) entry follows a **[Metadata](https://namazustudios.com/glossary/metadata/) specification ([Metadata](https://namazustudios.com/glossary/metadata/) spec)**. A [Metadata](https://namazustudios.com/glossary/metadata/) spec defines the **structure**, **type**, and **default values** of fields allowed in a [Metadata](https://namazustudios.com/glossary/metadata/) object. Together, they provide a structured way to manage configuration data for live operations, events, and other dynamic game content. **πŸ“Using [Metadata](https://namazustudios.com/glossary/metadata/)** If you have experience with other backend systems, [Metadata](https://namazustudios.com/glossary/metadata/) in Namazu Elements functions similarly to **PlayFab Title Data** or **Remote Config** in other platforms. The key difference is that Namazu supports **arbitrary nested JSON structures** and validates them against a **defined [Metadata](https://namazustudios.com/glossary/metadata/) spec**, giving developers more control and consistency. > --- ## Creating a [Metadata](https://namazustudios.com/glossary/metadata/) Schema 1. Log in to the management console and navigate to **[Metadata](https://namazustudios.com/glossary/metadata/) β†’ [Metadata](https://namazustudios.com/glossary/metadata/) Specs**. 2. Click **Create [Metadata](https://namazustudios.com/glossary/metadata/) Spec** 3. Enter Properties: - **[name](https://namazustudios.com/glossary/name/)**: A unique [name](https://namazustudios.com/glossary/name/) for the [Metadata](https://namazustudios.com/glossary/metadata/) Schema - **Access Level:** Define which [User](https://namazustudios.com/glossary/user/) level is required to read this - **Properties**: Define fields that [Metadata](https://namazustudios.com/glossary/metadata/) using this schema will include. - *Internal [name](https://namazustudios.com/glossary/name/)*: Unique key for the field. - *Display [name](https://namazustudios.com/glossary/name/)*: Human-readable label. - *Type*: Data type (`STRING`, `INTEGER`, `BOOLEAN`, `OBJECT`, etc.). - *Default Value*: Value to use when none is provided. - *Required*: Check if the field must be present in all [Metadata](https://namazustudios.com/glossary/metadata/). 4. Click **Create** to save the schema. ![](https://namazustudios.com/wp-content/uploads/2025/11/image-7.png) Creating a new [Metadata](https://namazustudios.com/glossary/metadata/) Spec --- ## Modifying a [Metadata](https://namazustudios.com/glossary/metadata/) Schema 1. Go to **[Metadata](https://namazustudios.com/glossary/metadata/) β†’ [Metadata](https://namazustudios.com/glossary/metadata/) Specs**. 2. Locate the schema you want to change and click the **edit (pencil)** icon. 3. Update any fields such as changing default values, adding new properties, or renaming display names. 4. Click **Update** to save your changes. ![](https://namazustudios.com/wp-content/uploads/2025/11/image-8.png) Finding the [Metadata](https://namazustudios.com/glossary/metadata/) Spec to Edit ![](https://namazustudios.com/wp-content/uploads/2025/11/image-9.png) Editing a [Metadata](https://namazustudios.com/glossary/metadata/) Spec --- ## Deleting a [Metadata](https://namazustudios.com/glossary/metadata/) Schema 1. In the **[Metadata](https://namazustudios.com/glossary/metadata/) Specs** list, click the **trash** icon next to the schema. 2. Confirm deletion. ![](https://namazustudios.com/wp-content/uploads/2025/11/image-10.png) Delete Confirmation Dialog **πŸ“**Deletion Deleting a schema does not automatically remove [Metadata](https://namazustudios.com/glossary/metadata/) instances using it, but those instances will lose structural validation. --- ## Creating [Metadata](https://namazustudios.com/glossary/metadata/) In order to create a [Metadata](https://namazustudios.com/glossary/metadata/) entry, you must have created a [Metadata](https://namazustudios.com/glossary/metadata/) Spec first. 1. Navigate to **[Metadata](https://namazustudios.com/glossary/metadata/) β†’ [Metadata](https://namazustudios.com/glossary/metadata/)**. 2. Click **Create [Metadata](https://namazustudios.com/glossary/metadata/)**. 3. Provide: - **[name](https://namazustudios.com/glossary/name/)**: Unique identifier (no spaces). - **Access Level**: Controls who can view ([User](https://namazustudios.com/glossary/user/), Server, etc.). - **[Metadata](https://namazustudios.com/glossary/metadata/) Spec**: Choose which schema defines the data structure. 4. Fill in the fields defined in the selected [Metadata](https://namazustudios.com/glossary/metadata/) spec. 5. Click **Create**. ![](https://namazustudios.com/wp-content/uploads/2025/11/image-11.png) Entering a [Metadata](https://namazustudios.com/glossary/metadata/) from the [Metadata](https://namazustudios.com/glossary/metadata/) Spec ## Modifying [Metadata](https://namazustudios.com/glossary/metadata/) 1. Open **[Metadata](https://namazustudios.com/glossary/metadata/) β†’ [Metadata](https://namazustudios.com/glossary/metadata/)**. 2. Select an entry and click the **edit** icon. 3. Adjust JSON values in any defined fields. 4. Click **Update**. ![](https://namazustudios.com/wp-content/uploads/2025/11/image-12.png) Finding a [Metadata](https://namazustudios.com/glossary/metadata/) to Edit ![](https://namazustudios.com/wp-content/uploads/2025/11/image-13.png) Updating an Existing [Metadata](https://namazustudios.com/glossary/metadata/) --- ## Deleting [Metadata](https://namazustudios.com/glossary/metadata/) 1. From the [Metadata](https://namazustudios.com/glossary/metadata/) list, click the **trash** icon next to the desired entry. 2. Confirm deletion. ![](https://namazustudios.com/wp-content/uploads/2025/11/image-14.png) Options for Editing and Deleting Metdata ![](https://namazustudios.com/wp-content/uploads/2025/11/image-15.png) Delete Confirmation Dialog --- ## Additional Tips - **Keep specs generic**: Reuse schema definitions where possible to avoid duplication across projects. - **Use defaults wisely**: Setting default values ensures clients continue to operate even if updates are delayed or incomplete. - **Validate data before publishing**: Always test [Metadata](https://namazustudios.com/glossary/metadata/) changes in a staging environment to ensure schema compliance and prevent client crashes. - **Version control your specs**: Export or document schema definitions so you can roll back easily. - **Avoid hardcoding**: Keep client-side logic dynamic by referencing [Metadata](https://namazustudios.com/glossary/metadata/) keys rather than embedding configuration constants. --- ## Summary - **[Metadata](https://namazustudios.com/glossary/metadata/)** are flexible JSON objects used to configure game clients remotely. - **[Metadata](https://namazustudios.com/glossary/metadata/) Specs** define the structure and validation rules for those objects. - The Management Console provides a simple interface for creating, editing, and deleting both [Metadata](https://namazustudios.com/glossary/metadata/) and their specs. - With schema-driven configuration, live updates can be deployed safely and consistently without requiring new builds.