> 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/stations.md).

# Stations

Because the stations in SS3D are user-created, they may be highly diverse in their shapes, sizes, and arrangement. Despite this, stations will likely share many similarities.

## Life Sustainment <img src="https://lh3.googleusercontent.com/Gu82RVgvMEJshQ79i0fFAW66sFtgTQLpF0AfwWAyR1F3l7HRUfMEF4FfTpmX8vjrk_9rxG7ehL-0jjHLnOS2A6S8CC0wLM7EWRi5OGGk5-j8qg-7am-LlKL4CxpPE6MiTQBYwsnmByIs66rAcKTFVw" alt="" data-size="line">

The first and most important thing to note about stations is that they truly are surrounded by the void of space. **Therefore, stations must be equipped with facilities that allow the station to be inhabited by human life, such as:**

* Atmospheric supply system (network of pipes & machines).
* Facilities for growing & cooking food.
* Places for crew members to eat and sleep.
* Places for emergency and medical treatment of the crew.
* Ports for cargo & arrival/departure shuttles + emergency pods.
* Sustainable electricity & gravity generators.
* Work stations to perform tasks for NT (?)

Station designers may take great liberties in designing the placement of these systems, but they almost certainly must be present.

## Work Environments <img src="https://lh3.googleusercontent.com/Gu82RVgvMEJshQ79i0fFAW66sFtgTQLpF0AfwWAyR1F3l7HRUfMEF4FfTpmX8vjrk_9rxG7ehL-0jjHLnOS2A6S8CC0wLM7EWRi5OGGk5-j8qg-7am-LlKL4CxpPE6MiTQBYwsnmByIs66rAcKTFVw" alt="" data-size="line">

Additionally to the life-sustaining aspects of the station, it’s important to remember that the station is filled with work environments, where specific sectors have restricted access to specific crew members. Medical doctors probably don’t need to be in the hydroponics basin; cargo workers probably shouldn’t be dwelling in the armory.

Because of these factors, **all crew members are equipped with an ID, which almost all airlocks in the station should be programmed to respond to.**

A crew member without an ID may be heavily restricted by where he can go, as doors will simply refuse to open unless they can prove they has access. IDs may also serve the purpose of locking specific equipment, such as lockers & briefcases, to prevent other crew members stealing one’s equipment.

## Structure <img src="https://lh3.googleusercontent.com/Gu82RVgvMEJshQ79i0fFAW66sFtgTQLpF0AfwWAyR1F3l7HRUfMEF4FfTpmX8vjrk_9rxG7ehL-0jjHLnOS2A6S8CC0wLM7EWRi5OGGk5-j8qg-7am-LlKL4CxpPE6MiTQBYwsnmByIs66rAcKTFVw" alt="" data-size="line">

Unfortunately, most things on the station are breakable. This includes the structure of the station like airlocks, walls, floors, and windows. These can all be broken with possible devastating effects to the station's ability to sustain life, like sucking out the atmosphere if an external wall is broken.

However, all elements of the station can also be rebuilt or added upon, using a wide range of raw materials and fabrication technology. And as long as you have the gases to do so, you can repressurize the station if needed.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ss3d.gitbook.io/design/environment/tilemaps/stations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
