# Creating Quests

<figure><img src="https://3845669459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fr43xlqdW27feUIXGLDzJ%2Fuploads%2FVQLNMyVkf2n7B4w6LkEU%2FCreating%20Quests%20V2.png?alt=media&#x26;token=10d3e567-7c78-436b-8b4a-61fb1279d077" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
To explore the complete list of quest templates and their specifications, visit [this link](https://docs.gamerbase.gg/).
{% endhint %}

<details>

<summary>Selecting a Template</summary>

The Admin starts by selecting a quest template. They will be able to choose between four categories:

* **Actions:** Visiting links, submitting emails, checking user levels, and more
* **Answers:** Polls, quizzes, answers, and more
* **Social:** X (Twitter), Discord, Twitch, and other social-relevant quests
* **Gaming:** Steam, FACEIT, Riot Games, and other gaming-relevant quests

Quest templates include additional fields that the admin must configure. For example:

* **Actions:** Specify which link to visit or the required in-app level
* **Answers:** Provide options for polls or correct answers for quizzes.
* **Social:** Configure actions on platforms like X and Discord, such as retweeting or checking a role.
* **Gaming:** Define actions on platforms like Steam or Riot Games, such as achieving CS2 kills or victories in LoL ARAM.

</details>

<details>

<summary>Set Properties</summary>

**Basic Properties**

The admin can now configure various quest properties:

* **Featured:** Determine whether the quest should be featured at the top of the App.
* **Tag:** Assign an identifier to categorise the quest with related ones. Create a new tag or select from existing tags. More details are available in the [**Tags section**](https://onboarding.xborg.com/admin-panel/quests-and-events/managing-tags).
* **Ordering:** Configure the order in which the quest should appear in a chain of quests. Choose between <mark style="color:red;">**`First`**</mark>, <mark style="color:red;">**`Last`**</mark> or <mark style="color:red;">**`Custom`**</mark> options. The custom option will prompt the Admin with ordering options based on available quests.

**Advanced Properties**

After configuring basic properties, the admin can further customise quests with Advanced Properties:

* **End Date:** Set the date and time when the quest will close.
* **Requirements:** Add criteria users must meet before accessing the quest. Requirements include five parameters: <mark style="color:red;">**`Quests`**</mark>, <mark style="color:red;">**`Wearables`**</mark>, <mark style="color:red;">**`Levels`**</mark>, and <mark style="color:red;">**`Discord`**</mark>.
* **Quest Visibility:** Choose from three options—<mark style="color:red;">**`Visible`**</mark>, <mark style="color:red;">**`Hidden`**</mark>, <mark style="color:red;">**`Hidden if Locked`**</mark>.&#x20;
* **Quest Reoccurrence:** Define if and how the quest should repeat—<mark style="color:red;">**`Once`**</mark> (default), <mark style="color:red;">**`Daily`**</mark>, or <mark style="color:red;">**`Weekly`**</mark>. These settings unlock Quest Streaks:
  * **Quest Streaks:** Users earn extra <mark style="color:red;">**`XP`**</mark> for consecutive completions. Missing a quest resets the streak.
  * **Streak Boost:** Increases rewards with each consecutive completion.
  * **Reward Cap:** Maximum <mark style="color:red;">**`XP`**</mark> a user can earn; the Streak Boost stops once the cap is reached.
* **Expiration:** Set conditions for quest closure—<mark style="color:red;">**`None`**</mark> (default), <mark style="color:red;">**`Date`**</mark>, or <mark style="color:red;">**`Participants`**</mark>. "Date" unpublishes the quest on the chosen expiry date, while "Participants" unpublishes it when the limit is reached.

</details>

<details>

<summary>Adjust Content</summary>

The Content section covers properties that immediately affect the user:

* **Language:** The Admin Panel supports a selection of languages. Quests must include titles and descriptions in all desired languages to ensure correct translation on the front end.
* **Title:** Provide a clear and concise title for your quest. This will be the first thing users see and should capture the essence of the quest.
* **Description:** The description should guide users on how to complete the quest successfully. Offer details, including objectives, requirements, and essential information.

</details>

<details>

<summary>Configure Reward</summary>

The penultimate step is selecting an appropriate reward:

* **Basic Rewards:**
  * **XP:** The in-app currency that increases player levels
  * [**Custom rewards**](https://onboarding.xborg.com/admin-panel/community-management/rewards)**:** Special rewards such as gift cards, jerseys, and signatures.
* **Premium Rewards:**
  * [**Wearables**](https://onboarding.xborg.com/admin-panel/community-management/digital-collectibles#inventory-items)**:** Items that customise user avatars
  * [**Achievement**](https://onboarding.xborg.com/admin-panel/community-management/digital-collectibles#achievement-badges)**:** Badges that highlight specific achievements and landmarks

</details>

<details>

<summary>Draft, Publish, or Schedule</summary>

With all steps complete, the Admin can select from the following actions:

* **Publish:** Immediately publish the quest to your app.
* **Schedule:** Select a time and date to publish the quest.
* **Save as Draft:** If you are not ready to publish the quest, save it as a draft to edit, reconfigure, and publish later.
* **Archive:** Close the quest and move it to the archives.

**Timezones**

* The CSM uses localized timezones (i.e. the admin's local system clock, then converted to UTC).
* In the case of the `Schedule` feature, the quest will be publish at the start of the selected day.

If an admin is in the CEST timezone and schedule a quest for November 30th, the quest will be published at `2024-11-30 00:00:00`CEST.

</details>