> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/flatredball/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/flatredball/tutorials/platformer-plugin/breaking-blocks.md).

# Breaking Blocks

This set of tutorials covers how to add breakable blocks to your platformer game. Breakable blocks have been popularized in the Super Mario Bros franchise, but are also common in other games such as Castlevania, Metroid, and Mega Man.

{% embed url="<https://youtu.be/7qirrV8w5SQ?t=15>" %}

Despite being introduced in an early Nintendo Entertainment System (and arcade) game, the feature of being able to break blocks requires advanced FlatRedBall collision functionality. We cover the following FlatRedBall topics:

* Creating entities in Tiled
* Using TileShapeCollections to adjust Entity RepositionDirections
* Dynamic destruction of entities
* Combining manual collision calls with CollisionRelationships
* Manually calling CollisionRelationship


---

# 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.flatredball.com/flatredball/tutorials/platformer-plugin/breaking-blocks.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.
