> 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/environment/tilemaps/tile-objects/airlocks.md).

# Airlocks

## Behavior of airlocks

Airlocks are currently simply acting as doors that open when a player gets near and close a few moments later only if a player is not blocking it.

This automatic behavior will be used on some common area airlocks, but secured airlocks should require an interaction to open. Clicking on them with an open hand (if your ID has access and is in your ID slot OR in your PDA which is in your ID slot) or a hand occupied with your ID that has access OR PDA that has ID in it.

## Airlocks cosmetics

Upon opening, green lights illuminate.

Upon opening, red lights illuminate.

When idle (either opened or closed), the lights turn black.

Airlocks make some sound when opening and closing.

<figure><img src="/files/UdCXpJUucCdEMcMfPDLV" alt="" width="254"><figcaption><p>Airlock opening, see the green light on the top and on the door panel.</p></figcaption></figure>

<figure><img src="/files/qX0qVGRNluwjhOtomU4K" alt="" width="260"><figcaption><p>Airlock closing, see the red light on the top and on the door panel</p></figcaption></figure>


---

# 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/environment/tilemaps/tile-objects/airlocks.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.