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

# Antagonists

As a compliment to any good protagonist, antagonist roles also exist on the station. Many antagonists are capable of existing at the start of rounds, or can appear in the middle of the round as well.

Antagonists (aka Antags) are categorized into 2 main categories; primary and secondary.

1. **Primary Antagonists** - usually more detailed with more complex abilities and goals. **They are designed to have a large impact on the round, and as such, they are usually only spawned at the start of a round.**
2. **Secondary Antagonists** - usually more basic with less unique abilities and goals. **They are designed to have little impact on the round, and as such, they are usually only spawned in the middle of the round.**

That being said, primary antags can be spawned mid-round and secondary antags can be spawned at round-start if the admins choose to do so.


---

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