> For the complete documentation index, see [llms.txt](https://itemsadder.devs.beer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://itemsadder.devs.beer/adding-content/furnitures/chair.md).

# Chair

To create a chair you just have to follow the furniture creation tutorial and add a simple attribute to the furniture to make it "sittable".

Just add the `furniture_sit` behaviour and specify the `sit_height`.

```yaml
behaviours:
  furniture:
    # .....
  furniture_sit:
    sit_height: 0.5
```

### `sit_height`

Height of the sit position

### `opposite_direction`

Default: true. Enable if you want the player rotate of 180 degrees when they sit on this furniture.

### `passenger_front_view_on_sit`

Default: true. Rotate the player to face the front of the furniture when they sit on it.

### `passenger_rotate_body`

Default: false. Rotate the player body while sitting on the furniture.


---

# 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://itemsadder.devs.beer/adding-content/furnitures/chair.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.
