# Metadata Structure

We have designed our game to contain SFTs divided into two categories: resources and items. We have considered resources the intermediaries to purchasing or crafting, while items can be equipped and used in order to advance into the game's plot. Each item has power attributes depending on the level and the base material which it is built of.

The structure is straight forward and simple as most data is stored directly on-chain for the attributes of the items. 

<figure><img src="/files/P5VpbxJUkOsdTVeN0iY6" alt=""><figcaption><p>The SFT logic</p></figcaption></figure>

### Metadata structure for a resource:

```json
{
  "sip": 16,
  "name": "Gold",
  "image": "ipfs://QmcQzR4zcamVTzCPfCRBYywHVHGVncB2o3YpojvRmakVkC/1.png",
  "attributes": [
    {
      "trait_type": "type",
      "value": "Resource"
    }
  ],
  "properties": {
    "image_in_game": "ipfs://QmcQzR4zcamVTzCPfCRBYywHVHGVncB2o3YpojvRmakVkC/1.png",
    "collection": "Base_Game_SFTs"
  }
}
```

We have the sip-16 specified because it follows the metadata standard. Fields to be easily readable and displayed, especially on marketplaces, such as name and image. Attributes field to describe the type, which is resource for all the resources. Properties field for the in-game image representation of the item and the collection it belongs to.&#x20;

{% embed url="<https://stacksgamefi.mypinata.cloud/ipfs/QmdrB3pecXRiTcPUoX6mresftQHfXfSebpZNyVKzuGa57S/1.json>" %}
Hosted metadata on decentralized storage
{% endembed %}

### Metadata structure for an item:

```json
{
  "sip": 16,
  "name": "Iron Sword 3",
  "image": "ipfs://QmcQzR4zcamVTzCPfCRBYywHVHGVncB2o3YpojvRmakVkC/10.png",
  "attributes": [
    {
      "trait_type": "type",
      "value": "Sword"
    },
    {
      "trait_type": "level",
      "display_type": "number",
      "value": 3
    },
    {
      "trait_type": "element",
      "value": "Iron"
    }
  ],
  "properties": {
    "image_in_game": "ipfs://QmcQzR4zcamVTzCPfCRBYywHVHGVncB2o3YpojvRmakVkC/10.png",
    "collection": "Base_Game_SFTs"
  }
}
```

Similar to what the resource structure looks like, with some slight updates. The name includes the element of the item ( wood, iron, enhanced ), the type of the item ( sword, armor, helmet etc. ) and the level of the item so it is easily readable on the marketplaces. These are also present in the attributes as three different ones, level also being a number. The properties are the same format as on the resource metadata.

{% embed url="<https://stacksgamefi.mypinata.cloud/ipfs/QmdrB3pecXRiTcPUoX6mresftQHfXfSebpZNyVKzuGa57S/10.json>" %}
Hosted metadata on decentralized storage
{% endembed %}


---

# 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.degenlab.io/gamefistacks/sfts/metadata-structure.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.