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

# Roles

Player roles.

***For technical documentation on this system, use the link below.***

{% content-ref url="/spaces/95OhrYYgKj0eUTnfM9sL/pages/qzuITQWJHdYSgB7c4yN6" %}
[Roles](https://ss3d.gitbook.io/systems/roles)
{% endcontent-ref %}

SS3D focuses on a dynamic that is primarily between players. Aside from a few basic mobs, this game features very few NPC’s. Instead, the well-being of the station hinges completely on the competence of the crew members, and the antagonists who put it in danger.

Victory for each player can mean something completely different depending on who – or what – you are. This is because each player occupies a specific role that contributes in some way to the environment around them. In this section, we focus on the types of roles the players will be occupying.


---

# 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/entities/roles.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.