> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/dev-guide/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/dev-guide/guidelines/code-design/subsystem.md).

# SubSystem

{% hint style="info" %}
This refers to a technical concept, not as a generic "container subsystem" or a "interactions subsystem"
{% endhint %}

A subsystem is a <mark style="color:blue;">**class**</mark> that manages something, it should work on its own, the only exception is when it needs information about other subsystems, but it is preferable that you do that by using <mark style="color:purple;">**events**</mark>, <mark style="color:purple;">**event buses**</mark>, or [<mark style="color:purple;">**network messages**</mark>](/dev-guide/networking/fishnet-networking/network-message.md).

A subsystem can be networked or not, for that you can inherit your class from <mark style="color:purple;">**SubSystem**</mark> or <mark style="color:purple;">**NetworkSubSystem**</mark>.

Here's a snipped of how you can declare a subsystem that creates an explosion somewhere.

```
public sealed class ExplosionSubSystem : NetworkSubSystem 
{
    public void CreateExplosionAt(Vector3 position, float size) 
    {
        // boom.
    }
}
```

It is also important that you know how all the subsystems work with the [<mark style="color:purple;">**SubSystems**</mark>](/dev-guide/guidelines/code-design/subsystem-locator.md) <mark style="color:blue;">**class**</mark>

{% hint style="warning" %}
Always add the postfix "**SubSystem**" in the name of the <mark style="color:blue;">**class**</mark> for your <mark style="color:purple;">**subsystems**</mark>.
{% endhint %}


---

# 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/dev-guide/guidelines/code-design/subsystem.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.