> For the complete documentation index, see [llms.txt](https://monster-lord.gitbook.io/monsterlord/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monster-lord.gitbook.io/monsterlord/function-modules/take.md).

# Take

In Monster Lord, the TAKE module is an innovative economic feature designed to generate MOLO through player activities, with its price supported by the SOL contract pool. Players can redeem SOL tokens at 90% of the current TAKE price and have all their MOLO tokens burned.

**Key Features:**

1. **MOLO Generation and Burning**:
   * All MOLO is generated through player activities. In the Monster Factory game, when players participate using SOL, 3% of each SOL input goes into the contract pool, with 2% entering the pool and simultaneously generating MOLO at the current TAKE price. When players use MOLO in the game, 1% of each input is directly burned to maintain token scarcity.
   * In the Monster Gold Rush game, when players use SOL to purchase gear, all SOL goes into the contract pool, generating MOLO at the current TAKE price, allowing players to embark on adventures and earn rewards.
2. **SOL Contract Pool**:
   * Based on the TAKE module, the game has established a SOL contract pool. The price of MOLO is determined by dividing the amount of SOL in the pool by the total circulating supply of MOLO, ensuring that every circulating MOLO has real SOL value backing it.

**Purpose:**

The TAKE module is designed to ensure the value and scarcity of MOLO tokens. This mechanism not only protects token scarcity but also ensures continuous appreciation, allowing each participant to maximize their value within the game.


---

# 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://monster-lord.gitbook.io/monsterlord/function-modules/take.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.