> 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/tiled-plugin/flatredball-tilegraphics-layeredtilemap/destroy.md).

# Destroy

### Introduction

Destroy method fully removes the LayeredTileMap from the engine. Specifically this method performs the following:

* Removes the LayeredTileMap from the engine's DrawableBatch list (removes it from being rendered)
* Removes all TileShapeCollections that have been created when the LayeredTileMap was loaded
* Removes any ShapeCollections created by shapes included in the LayeredTileMap
* Removes this object from being managed by the engine (if the map uses velocity, acceleration, or other every-frame variables)

This method is automatically called if the LayeredTileMap is loaded from a TMX in generated code, but must be called manually if the map is created manually in custom code.

### Code Example

The following code destroys the calling LayeredTileMap:

```lang:c#
LayeredTileMapInstance.Destroy();
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flatredball.com/flatredball/tiled-plugin/flatredball-tilegraphics-layeredtilemap/destroy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.