The stats are used to track specific user actions or achievements that contribute to quest progression. Stats serve as quantitative measures of user activity or accomplishments within games, allowing for dynamic and personalized quest objectives.

• Games can define custom stats relevant to their gameplay mechanics and quest requirements.

• Examples include "kills", "collectibles-found", "distance-traveled", etc.

• Each stat corresponds to a specific user action or milestone that contributes to quest progression.

Stat Naming Convention

• Choose descriptive and intuitive names for stats that accurately represent the associated user actions or achievements.

• Use consistent naming conventions to facilitate easy integration and understanding across games.

Example

• Quest Objective: Defeat 100 enemies.

• Associated Stat: "kills"

The Stats feature in the Quest System offers a flexible and versatile framework for tracking user progress and enabling dynamic quest experiences within games. By defining custom stats and integrating them with quest objectives, game developers can create engaging and immersive gameplay scenarios that incentivize user participation and advancement.

1. Stat Requirement:

   • Games specify the stat(s) that users must progress to complete the quest.

   • Stats serve as quantitative measures of user activity or accomplishments within the game, such as kills, collectibles found, distance traveled, etc.

2. Title:

   • Each quest is accompanied by a catchy and descriptive title that captures the essence of the challenge and encourages user participation.

   • Titles should be engaging and evoke curiosity or excitement to motivate users to undertake the quest.

3. Description:

   • Quests include a clear and concise description outlining the objectives and requirements for completion.

   • Descriptions provide users with guidance on what they need to do to progress through the quest and earn rewards.

4. Image:

   • Games provide an image to accompany each quest, enhancing visual appeal and recognition.

   • Images are displayed on the game quest card within the platform's interface, using a resolution of 500px x 400px for optimal display quality.

Example Quest

• Title: "Dragon Slayer Challenge"

• Description: "Embark on an epic journey to defeat the mighty dragons terrorizing the kingdom. Arm yourself with courage and skill as you venture into the dragon's lair and face formidable foes. Slay 10 dragons to prove your valor and earn exclusive rewards!"

• Stat Requirement: "dragon_kills"

Once you have tested your Quest, and you've confirmed that it is working fine, you should be able to submit it for review.

Then one of our content reviewers will check that the quest its working fine and will assign the appropriate amount of trophies.

After approval, your quest will be included in the Season Pass Game Quest pool for users to start enjoying!

Edit & Delete

As a Publisher, you will be able to remove or edit your DRAFT quests before submitting them for review. Once a Quest is approved, you won't be able to modify it.

Archive & Suspend

Once your Quest its approved you will be able to suspend it if you don't want that quest to be available anymore, or archive it to disable it temporarily.

Finally, the Progress Reporting Endpoint enables game servers to securely report user progress events to the Quest System API. This server-to-server communication ensures the integrity and authenticity of progress reports through RSA signature-based authentication.

Authentication Workflow:

1. API Key Generation:

   • Game developers will need to get their key pairs consisting of public and private keys.

   • Private keys are securely stored on the game server and used to sign progress reports.

2. RSA Signature Generation:

   • Before sending a progress report, the game server generates an RSA signature for the request payload using its private key.

   • The signature is appended to the request headers for authentication purposes.

3. Signature Verification:

   • Upon receiving a progress report, the Quest System API server extracts the RSA signature from the request headers.

   • The API server validates the signature against the corresponding public key associated with the game server.

   • If the signature is valid, the progress report is accepted and processed. Otherwise, the request is rejected.

The Progress Reporting Endpoint facilitates secure and reliable communication between game servers and the Quest System API, ensuring the integrity and authenticity of progress reports through RSA signature-based authentication. By following the authentication workflow and adhering to the request format, game developers can seamlessly integrate progress reporting into their server-side systems, enabling users to advance in quests and earn rewards effectively.