> 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/entities/glue-reference-customdestroy.md).

# CustomDestroy

### Introduction

CustomDestroy is a method that is called once on every Screen/Entity instance when it is no longer needed. Any objects that are created in custom code (as opposed to objects added through Glue) need to be removed/destroyed in CustomDestroy.

### Example Usage

Objects which are created in CustomInitialize or CustomActivity must be properly destroyed in CustomDestroy. There are two categories of objects which must be destroyed:

1. Entities must have their Destroy method
2. Objects added to the engine (like Sprites) must be removed from the engine

The following example shows a Sprite created in CustomInitialize, then later destroyed in CustomDestroy:

```
// At class scope:
Sprite mSprite;
void CustomInitialize()
{
   mSprite = SpriteManager.AddSprite("redball.bmp", ContentManagerName);
}
// ...
void CustomDestroy()
{
   SpriteManager.RemoveSprite(mSprite);
}
```


---

# 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/entities/glue-reference-customdestroy.md?ask=<question>&goal=<user_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.