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

# Planets

Planets work on the same principle as stations, with a few differences.

The first one is that the map structure is no longer completely surrounded by a vacuum. There could be atmosphere on the planet itself, though it might still not be exactly breathable. For example, a planet completely covered in CO2.

The second one is that there is no longer a need for an artificial gravity generators. The gravity outside of the station might still be lower (or higher) then what the crew might find comfortable, but it's probably not going to be zero.

Next is power generation. Some power generators like solar panels may be less efficient in general and have less workable hours at all due to day/night cycle on the planet.

Finally, the station is going to be in a middle of some environment, be it a sea of lava, a blasted desert, a rocky mine or something else.


---

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