> 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/~/changes/gNj2FHThLRTX82fsombt/gameplay/gamee-arc8-faqs/scoring-system-of-games/run.md).

# Run!

In Run!, players have to guide their ghost around a maze, collecting pellets and avoiding the ghosts. The match ends when the time runs out or when a player is caught by a ghost.

Players can get **points** in Run! in the following ways: 

1. Collecting pellets – 1 eaten pellet is equal to 1 score point
2. Big pellet – 10 points
3. Each 100 pellets in a row = 500 points; 200 pellets (x2) = 1000 points; 300 pellets (x3) = 1500 points, and so on
4. Killing enemies – The first killed enemy gives 200 points. Every other is 50 points extraplus. (Second = 250, third = 300, etc.) 
5. Time bonus – 10 points for every second survived per survived second

**Multiplier** – if the player collects pellets in a row, they activate the multiplier. The multiplier affects a player's score from eating pellets. Every 10th pellet increases the multiplier. Once a row of pellets is interrupted, the multiplier is reset.

The maximum multiplier is 25x.


---

# 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/~/changes/gNj2FHThLRTX82fsombt/gameplay/gamee-arc8-faqs/scoring-system-of-games/run.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.