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

# 🐹 Game Mechanics

## Section: Game Mechanics

```markdown
# Game Mechanics

## Core Gameplay Loop

1. **Prepare**: Create or upgrade your hamster
2. **Race**: Enter your hamster in maze races
3. **Watch**: Observe as your hamster navigates autonomously
4. **Assist**: Trigger skills at strategic moments
5. **Progress**: Gain experience and unlock new abilities

## Hamster Personalities

Each hamster has one of four distinct personalities that affect their maze-solving behavior:

| Personality | Description |
|-------------|-------------|
| **Cautious** | Prefers safer paths, avoids revisiting recent locations |
| **Adventurous** | Takes risks, makes more random choices, may find unexpected shortcuts |
| **Strategic** | Prioritizes moving toward the exit, plans ahead, makes optimal decisions |
| **Random** | Makes completely unpredictable movement choices |

Different personalities perform better in different maze types, so choose wisely!

## Skills System

As hamsters gain experience and level up, they unlock special abilities:

| Skill | Level | Effect |
|-------|-------|--------|
| **Wall Breaker** | 1 | Break through a single wall |
| **Teleport** | 2 | Jump 2 cells in any direction |
| **Speed Boost** | 3 | Move faster for 5 seconds |
| **Pathfinder** | 4 | Reveal optimal path for 3 seconds |

Skills must be triggered manually by the player during races, adding a strategic element to the otherwise autonomous gameplay.

## Progression System

- Complete mazes to earn experience points
- Every 10 XP grants a level up
- Each level unlocks new skills or upgrades
- Track your progress on the global leaderboard
```


---

# 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://hme.gitbook.io/hme/game-features/game.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.