> 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/platformer-animations-values/01-new-project-setup.md).
# New Project Setup
This tutorial begins with a new platformer project. To create a new platformer project, see the [Platformer Basics](/flatredball/tutorials/platformer-plugin/platformer-basics.md) tutorial. In short, the easiest way to get an animated character is to use the new project wizard.
If you started a new project without using the wizard, you would need to [create an entity with a sprite](/flatredball/glue-reference/objects/object-types/glue-reference-sprite.md#creating-an-entity-with-a-sprite) and [assign a .achx file](/flatredball/glue-reference/objects/object-types/glue-reference-sprite.md#animations) to the sprite. If you don't have a .achx file prepared already, use these below to give yourself a head start.
{% file src="/files/9jcFhmMLiOOsYgPQnx5L" %}
Once finished, your project has a character that is animated and ready to go. The remainder of the tutorials in this series cover how to modify the animations on the player and how to add new animations in response to game logic.
---
# 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/platformer-animations-values/01-new-project-setup.md?ask=&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.
