> 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/karate-kido.md).

# Karate Kido

Scoring system for Karate Kido on Arc8

## **Game principles**

\
The principle of the game is simple. You control a karate master chopping down a pole.\
Every punch destroys a part of the wooden pole. You need to be careful to avoid the wooden sticks. If your character is hit by a stick, it's game over!\
\
There is also a timer for the gameplay, and each punch adds more time to it. Playing too slowly means you can run out of time.\
\
During the game, you can gain power-ups, depicted as lamps.<br>

## **Power-ups**

* **Time Freeze** – freeze the timer for a short time
* **God Mode** – activate a mode where the character automatically punches, quickly and without mistakes
* **Extra Time** – refill the timer
* **Double Score** – double your points for a short time

\
**Score system**
----------------

* You gain 10 score points for each punch.&#x20;
* If the Double Score power-up is active, it's 20 points per punch.&#x20;
* Special blocks can also change the score.

\
**Special blocks**
------------------

* **Ice** – punch twice to destroy it, but gain only 10 pts
* **2x** – punch twice to destroy it and gain 20 pts
* **3x** – punch three times to destroy it and gain 30 pts

## **Possible ends of the game**

* **Game Over** – the character was hit by a stick
* **Times Up** – the timer ran out of time
* **Success** – the player survived until the end


---

# 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/karate-kido.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.
