> For the complete documentation index, see [llms.txt](https://whitepaper.angryfloki.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.angryfloki.com/minigames.md).

# Minigames

The AngryFloki project has dived into a new approach for minigames where their focus is on incentivising gaming. The minigames P2E rewards will be in the form of $ANGRYFLOKI token. Players who complete each stage of the AngryFloki mini games will be rewarded. Each stage has their own difficulty, the higher the difficulty of the stage is the more $AFLOKI token will be rewarded to the players. There are also NFT that will be available to purchase in the marketplace, and these NFTs are integrated to unlock specific characters that have their own unique abilities that will help player complete the stage easier.

This Strategy is crucial because we want to create minigames that are very fun and inspire growth. In addition, the NFT characters that are integrated to the mini games will bring more value to the NFT themselves in the NFT marketplace. With each milestone you hit in the game, great prizes are waiting for you. We are encouraging all budding players to come and challenge themselves on our platform and get a chance to earn from their skills.


---

# 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, and the optional `goal` query parameter:

```
GET https://whitepaper.angryfloki.com/minigames.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
