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

# Secondary Antags

**Secondary antagonists** are 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.**

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

Blobs are a station-eating blobulous mass that intends on feasting on the station everyone inhabits. The goal for the blob is simple: consume. As a blob, the player must choose a location for the core of their body to spawn, from which point the blob will begin to spread.

Spreading into occupied tiles will destroy the tile. Performing actions as a blob costs resource points, which generate over time. The player can choose to allocate resource points to lay down specialized blob tiles, as well as production of smaller allies that can travel and deal damage.

For a comprehensive list of the blob’s abilities, [see here](https://tgstation13.org/wiki/Blob#Blob_Powers). Biologically, not all blobs are alike, and each blob may have different attributes depending on its strain. For a list of blob strains and how they react, [see here](https://tgstation13.org/wiki/Blob#Blob_Powers).

Victory for the blob occurs when the blob reaches its goal for the number of tiles occupied.

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

We will write up more details about some of these or just link to SS13 wikis about them later. Not crucial right now.

* **Gray aliens** who abduct crew members for experimentation.
* **Chest-bursting aliens** who serve the queen.
* **Giant spiders** who want to turn the station into a nest.
* **Self-replicating robots** that eat all the station’s resources.
* **Phantoms** who aim to exact vengeance on the station.
* **Morphs**, creatures that can look like anything, and just desire to eat.
* **Shadow creatures** who aim to destroy all lights on the station.
* **Space ninjas** which utilize stealth and deadly force to fulfill objectives.
* **Slaughter demons**, which simply aim to kill everybody.
* **Pirates** that strive to steal any and all things valuable.
* **Sentient diseases** which aim to find a way to spread off-station.
* **Fugitives** which use the station as their refuge from…
* **Hunters** which storm the station to find fugitives.
* **Space dragons** which aim to fill the station with space carp.
* **Sentient slimes** who may or may not be aggressive.
* **Rat kings**, who want an army of rats. And cheese.


---

# 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/secondary-antags.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.