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

# Construction

Crew members should have the ability to alter, fix and or dismantle the structure of the [station](/design/environment/tilemaps/stations.md), that's where the Construction system comes in.

Which means that any person should be able to create or interact with walls and floor ~~and ceiling~~ of the station, should they have right materials and tools. The mane philosophy is allowing the player to affect the structure with a simple click of a mouse.

*Rules of* [*connectables*](/design/environment/connectables.md) *apply.*

### Tilemap Layers

Stations are like onions. They have layers.

The bottom layer is Plenum; the base structural layer. All the other layers are built upon this one. The plenum layer can have a few different models here like lattice and catwalk, but the main one is the plenum. This main model much like the layer it shares a name with is the core of the station's structure. Many things can be built on top and within the plenum.

<figure><img src="https://3662897456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhffJRpQgXgXOOhvtML3c%2Fuploads%2Fgit-blob-6bc65c8064165e0669f5358f767f33e01f0fca6c%2Fimage%20(11).png?alt=media" alt=""><figcaption><p>A set of uncovered plenums with several pipes laid into them and wire just on top.</p></figcaption></figure>

The plenum has room for 3 layers of atmos pipes and 1 layer for the large disposal pipe.

Immediately on top of the plenum layer is the wires layer (this may get lowered slightly down into the plenum)((we may triple this up at some point like /tg/). There's 2 main types of wires at the moment. Wires and Cables. Cables are basically the heavy duty wires.

Above cables there is 1 layer for floor tile, 1 for atmos pipes, a couple for furniture, a few for floor overlays, and 1 for walls. On wall, there are 3 layers of wallmounts (times 4, 1 for each cardinal direction).   \[\[\[add more recent image below]]]

<figure><img src="https://3662897456-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhffJRpQgXgXOOhvtML3c%2Fuploads%2Fgit-blob-3b0401eaea2db946e26a39e361d7fb09ae071c4e%2Fimage%20(19).png?alt=media" alt=""><figcaption><p>A set of pipes and junctions connecting pipes below &#x26; above the floor (we will only have 1 layer above the floor, not 4).</p></figcaption></figure>

Floors are a layer made to support furniture, walls, and even the captain's fat ass.

Walls are pretty self-explanatory: it limits the room, seals and insulates the rooms from the sides ~~and supports ceiling:~~

### Z Layers

NOT IN THE CURRENT ROADMAP but it's fun to conceptualize the idea of possible z-layers for the station itself.

{% embed url="<https://ss3d.space/assets/img/posts/19.10.01/EikoZSwap.mp4>" %}
A man can dream, right?
{% endembed %}


---

# 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/construction.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.
