> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/design/basic-game-mechanics/examine.md). # Examine Players should be able to examine the things that are being visually displayed to them. This is vital due to simplistic [art style](/design/readme/art-style.md) of the game and the amount of unique qualities of many objects. ## Basic Examine

AKA "Hover Examine", this basic form of examine happens continuously to display the name of the object your cursor is hovering over.

## Detailed Examine

Detailed examining is self explanatory in that it not only displays the object's name but also more details about the object like a description, inventory, custom ui, etc. (if it has those). It has to be activated by the player via holding a key (see [Controls](/design/basic-game-mechanics/controls.md)).

We can also add more detail to the description of an item the longer someone is examining it (while close). So if you examine someone running past you just get their skin, hair color, and some clothing yet miss their name for example. ### Custom UI The custom UIs on certain objects can provide more information than to the player than just a name and description. Below you can see a character's ID card with his name, age, occupation, and even a photo.

Custom examine UIs are distance-sensitive though. Meaning they only show up if you are within a certain distance, otherwise you will only see a basic name & description or even just a name. ![](/files/KMn0PGmZnh7tM70CaBDm) Some objects may show their inventory contents even, like characters for example.

--- # 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://ss3d.gitbook.io/design/basic-game-mechanics/examine.md?ask=&goal= ``` `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.