> 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/glue-reference.md). # FlatRedBall Editor ### Introduction The FlatRedBall Editor (also referred to as FRB Editor, FlatRedBall, or FRB) is a tool used to create games with FlatRedBall. The FRB Editor provides a variety of functionality, and can be extended and customized with plugins. Some of the most important functions of the FRB Editor include: * Creating new projects * Initial project setup using the New Project Wizard * Creating Screens and Entities * Setting the game's resolution and window size * Managing your csproj file by adding and removing code and content files * Generating code to load files * Providing a visual editor for creating entity instances * Editing and creating variables * Creating and managing collision relationships * Providing a "live editor" for your game * Tracking file dependencies * Reporting common errors * Measuring your game's performance * ...and much more In short, the FRB Editor provides functionality to make game development faster.

A game in the FlatRedBall Editor in Edit mode

### Is the FlatRedBall Editor Required? Ultimately the FlatRedBall Editor generates code in response to your actions. Therefore, the editor is not required to create games. You can use it to create new projects, but then do all of your coding in Visual Studio. Of course, since the FlatRedBall Editor is built to make game development easier, we recommend using it in your game. --- # 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/glue-reference.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.