🛠️Creating a Quest token

---

🔹 1. Create a New Quest Token

• Click “Define New Object”

• Select your experience from the dropdown

• Choose the “Quest” template

• You’ll now see the Quest definition form

---

🔹 2. Fill Out the Quest Metadata Form

🏷️ General Fields

Field	Purpose
name	Display name of the quest
description	Summary of what the quest is about
image	URL to the image shown in UI
type	Must be "quest" — this enables quest tracking in-game

---

📦 quest Object Fields

Field	Description
group	Logical group for filtering in UI or in-game
xp	Optional XP awarded on completion
tasks[]	List of task definitions, each with a title and description
rewards[]	Optional: Array of Token IDs to grant on quest completion. For help creating a badge, see Creating a Badge token

After completing the form, you will be presented with the generated metadata

---

🧾 Example Quest Token Metadata

jsonCopyEdit{
  "name": "Example Quest",
  "description": "Do your exercises",
  "image": "https://generatedimage.link",
  "type": "quest",
  "quest": {
    "type": "global",
    "group": "whitespace",
    "displayType": "quantity",
    "completionQuantity": 4,
    "xp": 123,
    "tasks": [
      {
        "title": "Jump 3 Times",
        "description": "Perform 3 jumps to get your body moving!"
      },
      {
        "title": "Run 500m",
        "description": "Run a total distance of 500 meters. Cardio is key!"
      },
      {
        "title": "Glide for 100m",
        "description": "Glide gracefully through the air for at least 100 meters!"
      }
    ],
    "rewards": [
      "33139:0x1122334455667788991122334455667788991100:3",
      "33139:0x1122334455667788991122334455667788991100:4"
    ]
  }
}

---

📌 Important: completionQuantity will be automatically set to one more than the number of tasks This accounts for:

• 1 token to start the quest

• 1 token per completed task

Example: 3 tasks → completionQuantity: 4 → 1 token to start + 3 tokens for each completed task.

Before minting:

Once development is complete this token should be non-transferable so that users cannot trade progress or restart the quest, but during the development process it is better to set this to transferable so that it can be deleted from a users wallet and allow the user to retry the quest.

• Price → usually 0 for dev

• Transferable:

  • ✅ True during dev — allows testing/resetting progress

  • 🚫 False for production — prevents replaying quests via trading tokens

---

🔹 6. Mint the Token

After saving, click “Mint”.

You’ll be returned to the creator dashboard and shown a Token ID in this format:

ChainID:ContractAddress:TokenID

Example:

33139:0x1122334455667788991122334455667788991100:1

Part	Meaning
33139	Chain ID (APECHAIN)
0x1122...	Contract address for your experience
:1	Unique identifier for this token

---

🔹 7. Preview & Access Metadata

• You can click the token’s image on the dashboard to view metadata.

• This page reflects the JSON you just configured and is used in-game by clients and UI.

• You can update the token metadata at any time using the "Update Metadata" button