> For the complete documentation index, see [llms.txt](https://docs.allout.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allout.game/using-the-editor/inspector.md).

# Inspector

At the top of the inspector, you have basic properties about the entity like its position and scale.

<figure><img src="/files/yyZD124wzqTvuX3Z6laZ" alt=""><figcaption></figcaption></figure>

Below the entity properties are all of the components you have currently added to that entity.

Each component can provide "fields" for you to edit which. For example, Interactable components allow you to change their `Text` or `Radius` fields.

Your own custom components made with scripts can expose fields to the inspector as well. For example, you could make a tycoon purchase interactable with a field to change its price in the editor.

```go
TycoonUnlockButton :: class : Interactable {
    price: int @ao_serialize;
    is_unlocked: bool;
    
    on_interact :: method(player: Player) {
         if Economy.can_withdraw_currency(player, "Coins", price) {
            Economy.withdraw_currency(player, "Coins", price);
            is_unlocked = true;
        }
    }
    
    // Logic to show/hide the item based on is_unlocked status...
}
```

Now when you add the `TycoonUnlockButton` component to any entity, you can set a price for that entity to unlock.


---

# 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.allout.game/using-the-editor/inspector.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.