> 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/objects.md).
# Objects
### Introduction
The Objects folder contains most visual and collidable game objects. Objects can be added to Screens and Entities, and when added through Glue, objects will automatically be managed. Objects can be grouped in one of three categories:
1. Instances of entities
2. Primitive types (such as FlatRedBall Sprite or Circle)
3. Objects obtained from a file
### Creating an Entity Instance
Entity instances can be created in Glue by drag+dropping an entity onto the Objects folder of a Screen or another entity.
Using the right mouse button when performing the drag+drop allows the selection of a single instance or a list.
Entities can also be added through the right-click menu.
Entities can also be added to screens or other instances of entities.
---
# 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/objects.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.
