> For the complete documentation index, see [llms.txt](https://docs.epicapes.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.epicapes.io/games/epicapes-expeditions.md).

# EpicApes Expeditions

Expeditions - a gamified web activity where on the EpicApes Web Platform, allowing users to send their EpicApes NFTs on resource-gathering missions. Unlike the EpicApes idle adventure game, which is a standalone product, Expeditions serve as an interactive staking mechanism, rewarding players with valuable resources for crafting and upgrading NFTs to enhance their staking potential.

The ultimate goal of Expeditions is to craft [staking-based traits](/ecosystem/nft-collection/trait-system.md) — special traits that empower NFTs to passively generate $SP tokens daily.&#x20;

{% hint style="success" %}
The more varied and powerful the traits applied to an NFT, the greater its daily staking rewards.
{% endhint %}

NFTs upgraded with multiple high-value staking traits will not only earn more tokens but also become highly sought-after assets in the marketplace, significantly increasing their trading value.

***

## How it Works

Players use their EpicApes NFTs as characters and deploy them to different locations to gather resources. These resources are essential for crafting new traits, including the Staking Traits required for token generation.

Each location has specific entry requirements, mission success chances, time constraints, and token fees, adding a strategic layer where players must optimize their NFT selection for the best rewards.

***

## **Key Mechanics**

1. **Power Score (PS) Requirements**
   * Every EpicApes NFT has a Power Score (PS), determined by its traits.
   * Locations have a minimum PS requirement that must be met to enter.
   * Players can send multiple NFTs to fulfill the requirement and access more challenging locations.
   * Players can also form a squad, sending a primary character along with supporters to complete harder missions.
2. **Success Chance & Mission Time**
   * Each location has a success rate — the harder the location, the lower the base success chance.
   * Missions have a fixed duration, requiring players to wait for completion before receiving rewards.
3. **Resource Drops & Crafting**
   * Completing an expedition rewards players with resources for crafting new traits.
   * Some traits require recipes, which can be:
     * Freely available to all players.
     * Purchased from the in-game store.
     * Obtained from difficult locations.
4. **Token Fee & Staking Utility**
   * Every mission requires a small token fee as an entry cost.
   * This ensures long-term sustainability and reinforces NFT utility within the ecosystem.

***

By strategically upgrading their NFTs with Staking Traits, players can increase their token generation capacity and significantly boost the NFT’s market value.

Expeditions create a unique blend of staking, resource management, and gamification, ensuring a rewarding experience for all EpicApes NFT holders while enhancing the value of their assets over time.

***

{% hint style="success" %}
$SP (Staking Points) is an off-chain token and plays a crucial role in determining each holder's share of the $EPIC token airdrop. To ensure fairness and transparency, all $SP-related activities are recorded on-chain, even though the token itself remains off-chain.
{% endhint %}


---

# 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://docs.epicapes.io/games/epicapes-expeditions.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.
