> For the complete documentation index, see [llms.txt](https://docs.sandbox.game/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sandbox.game/en/creator/game-maker/creative-guides/experience-guide/puzzle-games.md).

# Puzzle Games

{% embed url="<https://youtu.be/UUUpei7MkM4>" %}

Puzzles are an interesting genre that require more logic. While you may decide to create a maze or sequence that allows players to collect and use items to progress through a puzzle, the new [**Game Rules system**](/en/creator/game-maker/docs/game-rules.md) offers all new possibilities for creating custom puzzles with complex logic and loops.

### Variations **of Puzzles**

<table data-view="cards" data-full-width="false"><thead><tr><th></th></tr></thead><tbody><tr><td><strong>Tile-Matching:</strong> <br>Matching identical tiles or objects to clear them from the play area.</td></tr><tr><td><strong>Physics-based Puzzles:</strong> <br>Solve challenges using realistic physics simulations.</td></tr><tr><td><strong>Logic Puzzles:</strong> <br>Challenges that require logical deduction and problem-solving.</td></tr></tbody></table>


---

# 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://docs.sandbox.game/en/creator/game-maker/creative-guides/experience-guide/puzzle-games.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.
