> For the complete documentation index, see [llms.txt](https://doc.realvirtual.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.realvirtual.io/components-and-scripts/mu-movable-unit/sink.md).
# Sink
A Sink is responsible for deleting [MUs](/components-and-scripts/mu-movable-unit.md). Using a Box Collider, the Sink deletes all colliding ([MUs](/components-and-scripts/mu-movable-unit.md)):
If needed, the Sink can be controlled by a Signal *Delete*. This will activate and deactivate the Sink. The same can be done with the setting *Delete Mus*. If you define a Tag under *Delete Only Tag* only [MUs](/components-and-scripts/mu-movable-unit.md) with the specific Tag will be deleted.
> Please take care that the Sink is situated on the correct layer, to enable collision detection. Usually the sink should be placed on the rvSensor Layer (before 2022 g4aSensor Layer).
Please check the [Realvirtual.io Class Reference](https://realvirtual.io/apidoc/classrealvirtual_1_1_sink.html) for more information about the properties and methods of this component.
© 2025 realvirtual GmbH [https://realvirtual.io](https://realvirtual.io/) - All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including printing, saving, photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher.\\
---
# 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://doc.realvirtual.io/components-and-scripts/mu-movable-unit/sink.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.