> For the complete documentation index, see [llms.txt](https://wiki.gamee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.gamee.com/gameplay/gamee-arc8-faqs/scoring-system-of-games/cranky-monkey.md).

# Cranky Monkey

Cranky Monkey is a **live turn-based multiplayer game.**&#x20;

The goal is to match gems in combinations of **3 or more** in order to get points. With the points, your monkey can attack your opponent's monkey. The winner is the player whose monkey successfully knocks down the opponent's monkey.&#x20;

**Rules**

* Take turns with your opponent to match gems to earn points for your monkey to attack. The winner is the last monkey standing.
* If you match more than 3 different colors in one turn, you activate the super **SMASH**, which deals significant damage to your opponent.
* Making a combination of 4 or more gems grants you an **extra move**.
* Making a combination of 4 gems gives you a **laser** – when activated, it destroys a whole row or column.
* Making a combination of 5 gems gives you a **bomb** – when activated, it destroys a 3x3 block
* You can use the **hammer** to remove one specific element from the board
* Collect green gems – once you have filled the bar below the monkey, you will get a **special power**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.gamee.com/gameplay/gamee-arc8-faqs/scoring-system-of-games/cranky-monkey.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
