What Are Custom Quests?

Forge provides some quests by default. These are called native quests.
Examples include LINK AN ACCOUNT and PLAY A STEAM GAME.

In some cases, one may want to create a quest that is not available by default and is based on thier own requirements. These are called Custom Quests.

Custom quests allows one to define their own rules for when a quest is considered completed.

Examples of custom quests:

• Play a game for a specific number of hours
• Play a game for a certain number of days
• Unlock one or more achievements in a game
• Reach a specific in-game milestone
• Buy a product or NFT from a webshop

Ways to Configure Custom Quests

Forge supports two ways to configure custom quests:

1. Using Data Ingestion APIs
2. Using Webhooks

The method you choose depends on how quest completion can be detected.

Custom Quests Using Data Ingestion APIs

With this method, you send in-game data, such as gameplay time or achievement information, to Forge. Forge uses this data to track quest progress and determine whether the quest is completed.

You should use this method to set up quests like:

1. Play the game for N hours
2. Play the game for N days in a week
3. Play the game for N days in a row
4. Unlock a specific in-game achievement or title
5. Unlock N in-game achievements

Configure Custom Quests Using Data Ingestion APIs

Custom Quests Using Webhooks

Data Ingestion APIs support a defined set of quest patterns. Some quests, however, can only be verified by your backend systems, for example, purchases, external milestones etc.

For such cases, Forge supports Webhook-based Custom Quests.

When a user clicks “Verify Now” on Forge, we trigger your webhook endpoint. Your system then validates whether the user has completed the quest and returns the verification result.

This approach allows us to support any custom quest logic, as long as your system can determine completion.

Configure Custom Quests Using Webhooks