Custom Quests / Convert
Last updated
Last updated
Click to introduce our bot to your server.
Here's a quick overview of custom quests from the players' perspective:
You can now make your custom quests via Hype Engine. To get started, go to your and click on Hype Engine ⇒ Custom Quests ⇒ Add Quest.
For any quests, you can set up:
Title: the name of the quests (40 characters max)
Quest Type: API, Manual Check, Micro Survey, and Web3 (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 more complicated 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. Signing up and connecting with a wallet should be marked as a "one-off."
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 ask the member to do a micro survey. In this case, you will make "visit your website" a required quest before "giving feedback."
In the example below, we first asked 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.
Here are the four 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 manually mark quests as completed. 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 the API quest, we will ask you to give us an external URL where we instruct the users to go to complete the quest.
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 quests.
Once a user submits 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 surveys: single-choice and short-answer. Any Micro Survey will be marked as a one-off automatically.
You can now set up on-chain quests, especially for holding and staking.
How it works?
We reward members who complete staking quests in two ways. First, during the daily check-in, members will earn 10 points regardless of the level (vs 1 pts for regular users). Second, when the members complete all their quests, they will get an extra 10/20/50 bonus points, depending on the level.
If this is the first time the member plays on-chain quests, Hype Engine will prompt him to connect their wallet on their CommunityOne profile page. If you want to build API quests in the future, you may refer to this member using his wallet address.
Setup
To set up on-chain custom quests, go to the Custom Quests tab and toggle-ON: this is a web3 project.
Then click on + Add Quest and select Web3 as the Quest Type:
Here is a list of fields that require your input:
Contract Address: Your own token's contract address.
Reward Levels: How many tokens the users should hold in order to get extra reward. For example, we recommend starting at 1, Level 2 should be the holding amount at 33% percentile, and Level 3 should be around 66% percentile.
Python SDK is officially released now:
You can find more info .
Currently, we offer buying/staking quests for chains on EVM. Specifically for staking, we support cases where users' tokens are swapped to another "staked" token. For example, a user first purchases token X. When the user swaps the token, it is converted into a staked-X token. If you'd like us to support other staking mechanisms, please reach out on .
Chain ID/Chain Type: Currently we only support EVM. If you'd like us to support your chain type, feel free to reach out on our .
Join for questions, comments, and a little gift.
