LogoLogo
Visit the KGeN website
  • Introduction
  • POG
    • Five Key Dimensions
    • POG Score
    • Gamer Profile Mint, Updation, Data Ownership & Rights
    • Publishers & Brands: Data Access & Rights
    • POG-E: Augmented Gaming LLM
      • Foundational Elements
      • Key Components of POG-E tech stack
      • Foundational Data powering POG-E
      • Agent Development Framework
      • Data Orchestration
      • Developer Tools
      • Deployment, Scalability, Monitoring, Maintenance and Future Enhancements
      • AI Agent Use Cases
  • Tokenomics
    • r-KGeN
    • $KGeN
      • $KGeN Allocation and Unlock Schedule
      • $KGeN token utility
        • Demand Lever : Product
        • Demand Lever : Staking
        • Demand Lever : Business Model
  • Kratos Oracle Network
    • Oracles
    • Oracle Functionality
    • Consensus Mechanism
    • Oracle Acquisition and Staking Requirements
    • Key Purchase and Multichain Support
    • KGeN Sale and Staked Keys Growth
    • Oracle Reward Structure
    • Oracle Hardware and Software Deployment
  • Kratos Stack
    • Stack Composition and Interaction
    • Engagement
      • Play
        • KQuest
          • User Workflow
          • Technical Implementation and System Design
        • KDrop
          • User Workflow
          • Technical Implementation and System Design
        • Games API Integration
      • Compete
        • Klash
        • Protocols
          • ESports Protocol
            • User Workflow
          • Loyalty Protocol
            • User Workflow
      • Rewards
      • Redeem
        • E-Commerce
          • System Design
    • External Partner Interfaces
    • Reputation
      • The POG Engine
      • The POG Attribution
        • System Overview
      • Impact of The POG
    • Adoption
      • Web3 and Wallet Integrations
        • Foundation
        • Web3 Toolkit
        • Tokens
        • Chain abstraction
        • Solutions for Gamers
      • Clan Tools
        • Clan Chief and Member Overview
        • User Workflow
        • System Architecture
      • Profile
      • Leaderboards
    • Infrastructure and Scalability
      • Data
      • Frontend Architecture
      • Devops & Security
      • AI
  • Publishers
    • Self Serve
      • Technical Implementation
      • Publishers Flow
  • Appendix
Powered by GitBook
On this page
  1. Kratos Stack
  2. Engagement
  3. Play

KQuest

The KQuest system is a dynamic framework designed to immerse gamers in a variety of engaging challenges while fostering deeper interaction with the gaming platform. KQuests serve as actionable objectives that players can undertake to achieve specific goals. The system is crafted to deliver excitement, foster progression and enhance long-term player engagement through well-defined objectives and diverse quest types.

KQuests offer diverse gameplay experiences, each delivering unique benefits to players. Combat KQuests enhance tactical skills through defeating enemies, while Collection KQuests encourage exploration and resource gathering. Exploration KQuests uncover hidden elements and expand gameplay areas, and Puzzle KQuests test problem-solving abilities with brain-teasers. Lastly, Social KQuests foster community engagement by connecting players with developers, clans, and broader gaming networks through social interactions.

Each KQuest aligns with specific goals, creating pathways for player activation, retention, and advocacy:

  • Activation: Inspire first-time players to engage with a product, feature, or component, turning curiosity into action.

  • Progression: Deepen player immersion by encouraging advancement within the game’s storyline or mechanics.

  • Engagement: Boost the duration of gameplay by offering captivating challenges that keep players invested.

  • Retention: Re-engage dormant players by offering enticing reasons to return and continue their journey.

  • Advocacy: Empower players to invite and involve their peers, fostering community growth and loyalty.

  • Monetization: Promote in-game purchases, such as NFTs or passes, driving revenue generation.

  • Creation: Motivate players to develop in-game assets, adding a layer of creativity and personal investment.

The KQuest States define the lifecycle of a quest, guiding its progression from creation to completion. Each state ensures seamless management and clear visibility for both admins and users, enhancing the overall experience for gamers and developers.

  • Draft: The starting point where admins create and edit KQuests. This state allows full flexibility for building the quest structure and content.

  • In Review: Once ready, the KQuest is submitted for review to ensure accuracy and quality before further processing.

  • Approved: After review, the KQuest is approved, making it eligible for publishing.

  • Published: The KQuest is visible to gamers on the platform but not yet open for participation. Gamers can view KQuest details and prepare for activation.

  • Live: The KQuest is now active, and gamers can start their journey. During this phase, players can participate and work towards completing the quest objectives.

  • Live - W1, W2 (Waiting): The KQuest remains active but may have limitations on rewards availability due to submission or validation constraints.

  • Paused: The KQuest is temporarily removed from visibility and participation, often for updates or adjustments.

  • Ended: The KQuest is completed, and no further participation is allowed. Gamers can view their achievements and results.

  • Archived: The KQuest is removed from the platform but remains stored in the archives for reference.

  • Private: The KQuest is in private mode only visible to admins for testing purposes

Each state is designed to ensure proper control and flow, aligning with the goals of offering gamers a seamless and engaging questing experience while giving developers robust tools for quest management.

Starting A KQuest

Submit Proof Of Completion (To convert this section in flow diag)

Starting the KQuest:

  • User accesses quest details page and starts the quest.

  • If proof of work (POW) submission is enabled, a process is initiated.

Login Method Selection:

  • User selects a login method from a dropdown.

  • Standard validation is applied to the entered details.

  • If validation fails, an error message is shown, and the "Submit" button remains disabled.

POW Submission:

  • User sees a pop-up to upload the proof of work.

  • User selects an image file from their device and submits it.

  • The system confirms successful submission or provides an error message.

Clan Chief Referral:

  • If required, the user is prompted to provide the mobile number of their clan chief.

  • Standard validation is applied to the mobile number.

  • If the number is invalid or not registered, the system provides an error message.

  • Alternatively, the user can select an option indicating they do not have a clan chief.

Final Steps:

  • Once validated, the proof of submission and additional details are recorded.

  • If the user closes the pop-up or encounters errors, they can retry the process or abandon it.

Users can Share a Quest

KQuest Leaderboard Score Update Flow

PreviousPlayNextUser Workflow

Last updated 3 months ago