> For the complete documentation index, see [llms.txt](https://docs.mutate.games/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mutate.games/guides/creating-game-logic-in-mutate/item-visibility.md).

# Item Visibility

To make an item that can only be collected once, let’s create another link.

Click on the collectible and add the ‘**Hider**’ component, and then go to Linking. 

Add another link by pressing + and select **‘Interacted**,’ then link back **onto the object itself** by clicking a little box that will appear just above the + on the top right corner. Select ‘**Hide**’ — now, when you interact to collect the item, it will disappear.

![](/files/rX7sOe76fZiTRwmxkRZk)

{% hint style="info" %}
Objects that have 'disappeared' will still have collision on them - meaning, you can still run into them and they will act as an invisible wall. To avoid this, you'll need to also assign the entity the **Collision Toggler** component, and create some more links.

Learn how to do that here.
{% endhint %}

![](/files/KToBQomA7oTEow6GpfOE)


---

# 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.mutate.games/guides/creating-game-logic-in-mutate/item-visibility.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.