> 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/01-new-project-setup.md).

# New Project Setup

### Introduction

We'll begin this tutorial with an empty project. Mine is called BreakingBlocksProject.

![](https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2Fgit-blob-03133a930752441c041376d0f341624c0ee205e5%2F2021-04-img_60777be0d952b.png?alt=media)

### New Project Wizard

The New Project Wizard helps us get a project set up quickly. We leave most of the options at their default, but change the following:

#### Player Entity

* Change **What kind of control will the player have?** to **Platformer**
* Uncheck **Add Sprite to Player Entity** unless you intend to add graphics to your Player entity. This tutorial does not cover how to add graphics to the Player entity.

#### Levels

* Change **Number of levels to create** to **1**. We only have one level in this game

### Conclusion

Now our project is ready to go and we can start adding our level.


---

# 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/01-new-project-setup.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.
