> 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/beefball.md).
# Beefball - A Full FlatRedBall Tutorial Project
### Introduction
If you're looking for a jump-start on how to make games with FlatRedBall and the FlatRedBall Editor, you've come to the right place. The following tutorials walk you through how to make a game called **Beefball**. Beefball is a fast-paced physics based game similar to air-hockey. What are you waiting for, let's get started!
Beefball Icon
Completed Project: [Beefball.zip](https://files.flatredball.com/content/Tutorials/Beefball.zip)
### Code Only Projects
This tutorial covers how to create Beefball with the FlatRedBall Editor, which is the typical way to work with FlatRedBall. Of course, you can also use FlatRedBall without the editor. If you are interested in developing in a *code only* environment, you can download the BeefballCodeOnly project which is located in the FlatRedBall Samples folder:
{% embed url="" %}
BeefballCodeOnly Sample
{% endembed %}
You can still look through this documentation to see how the project might be structured conceptually as you browse the sample code.
---
# 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/beefball.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.
