> 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 will be called BreakingBlocksProject.

![](/files/RIW9ObZu0bJlBMM8LWo9)

### New Project Wizard

The New Project Wizard can help us get a quick project set up. We will leave most of the options to their default, but we will 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 will not cover how to add graphics to the Player entity.

#### Levels

* Change **Number of levels to create** to **1**. We will 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 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://docs.flatredball.com/flatredball/tutorials/platformer-plugin/breaking-blocks/01-new-project-setup.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.