🆕Custom Quests / Convert

Click here to introduce our bot to your server.

Here's a quick overview on custom quests from the players perspective:

You can now make your custom quests via Hype Engine. To get started, go to your dashboard and click on Hype Engine ⇒ Custom Quests ⇒ Add Quest

Basic Quests Configuration

For any quests, you can set up:

• Title: the name of the quests (40 characters max)

• Quest Type: API, Manual Check & Micro Survey (details to follow)

• Description: Descriptions for members to follow

• Effort Level: Easy, Medium, Hard

  • The effort level corresponds to points (10, 25, and 50, respectively).

  • The effort level inversely corresponds to the number of members who will see a quest. The harder the quest, the fewer members will receive it. We use a proprietary algorithm to determine which members are shown which quests. To maximize conversion, we avoid displaying challenging quests to new members.

• One-off task: Mark "Yes" if you only want members to see it once. Tasks such as sign up, connect with wallet should be marked as "one-off".

Advanced setup:

• Required Role: Only show this quest if the user has this role

• Required Quest: This allows you to chain quests together. For example, you can first ask a member to visit your website, and then you can ask the member to do a micro survey. In this case, you will just make "visit your website" a required quest before "giving feedback".

  • In the example below, we first ask the user to visit their communityone profile and then it was chained with "answer a quick question", which is about giving us some feedback about their profile page

• Start Date / End Date: Depending on the length between the start and end date, our algorithm will prioritize quests that will expire soon.

• Reward Role: You can grant a role if they have completed a quest.

3 types of custom quests:

Here are the 3 types of custom quests that you can make:

• API Quests: Specify your quests and receive a dedicated API endpoint to update user progress automatically. This means you no longer have to mark quests as completed manually. The key benefit is its full automation, which streamlines the process—although it requires some development work.

  • If this is your first time defining an API quest, you will also get a unique key from us.

    
  • With API quest, we will ask you to give us an external URL where we instruct the users to go to complete the quest.

  • Python SDK is officially released now: https://pypi.org/project/communityone/

  • You can find more info here.

• Manual Review: After a user completes a quest, they can submit their work by opening a support ticket. The user is awarded points once you review and approve the submission. This manual review process allows you to experiment with various quest ideas and quickly gauge their impact.

  • If you choose manual review quests, we will ask you for notify roles; this is the role we will tag when a user opens up a ticket regarding their quest.

  

Once a user submit a manual review, you can click on the Quest Completed button and we will automatically take care of the points.

• Micro Survey: You can ask your members any questions and feedback. Currently, we support two types of survey: single choice and short answer. Any Micro Survey will be marked as one-off automatically.

Join Discord for questions, comments, and a little gift