> For the complete documentation index, see [llms.txt](https://tools.fluxinc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tools.fluxinc.io/flux-inc.-services/adventure-platform-1.md).

# Adventure Platform

## Overview

Flux Inc.’s **Adventure Platform** is a customizable, chance‑based mission system built for NFT collections seeking to deepen engagement and reward holders. Launch adventures with flexible durations, reward types, and full UI branding—all while maintaining holder custody of their NFTs.

***

## How It Works

* **Backend Setup**: Your team defines the adventures—selecting prizes, duration, maximum adventurers, cost, and reward probabilities.
* **Holder Interaction**: Holders choose their NFT, initiate the adventure, and the NFT becomes temporarily frozen in their wallet (they retain ownership).
* **Claiming Rewards**: Once the adventure is complete, the holder unfreezes the NFT and receives the outcome.
* **Batch Adventure Mode**:
  * PC: send or claim up to **18 NFTs** at once.
  * Mobile: up to **9 NFTs** at once.

***

## Key Features & Customization

<table><thead><tr><th width="262">Feature</th><th width="445">Details</th></tr></thead><tbody><tr><td><strong>Custom Adventure UI</strong></td><td>Fully branded screens, artwork, and UX so the adventure feels like part of your collection.</td></tr><tr><td><strong>Flexible Reward Types</strong></td><td>Earn NFTs, tokens, or other assets with configurable chance probabilities.</td></tr><tr><td><strong>Multiple Use Cases</strong></td><td>Idle game‑style missions, gamified raffles via adventures, or custom quest systems.</td></tr><tr><td><strong>Scalable Adventure Options</strong></td><td>Adjustable adventure length and participant limits to suit community size.</td></tr><tr><td><strong>White‑Label &#x26; Fast Turnaround</strong></td><td>Full white‑label versions, often live within 24 hours once info is provided.</td></tr></tbody></table>

***

## Benefits

### For Projects

* Boost community engagement and return visits.
* Generate recurring revenue.
* Token burn potential to increase tokenomics value.
* Strengthen brand identity through custom UI.

### For Holders

* Participate in adventures for rewards while maintaining NFT ownership.
* More fun & social interaction—something to share and talk about.
* Higher appeal and retention due to batch adventure support.

***

## Use Cases

* Idle‑game style questing similar to “The Heist” where players repeatedly take on missions.
* Holders paying token or NFT to join an adventure which may yield rare rewards.
* Using adventures as a creative form of raffle or lottery embedded in missions.

***

## White‑Label Option

* Available under several customizable payment plans.
* Deployment ready in as little as **24 hours**, given required assets and configuration.
* Full support and ongoing updates included.

***

## Visual Previews

> 📌 *Insert image of Adventure UI / mission selection screen*\
> 📌 *Insert animation or mockup of claim flow or reward outcome*

***

## Getting Started

Ready to bring Adventure to your NFT project?

* Join our [Discord](https://discord.gg/zdpK4NEKbF)
* Reach out via our [website](https://fluxinc.io)
* Our team will guide you through setup and launch.

***

*Last updated: {{insert update date}}*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://tools.fluxinc.io/flux-inc.-services/adventure-platform-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.