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

# Releases

## Release **Versioning**

The release naming is defined by <mark style="color:purple;">**`gamestate`**</mark>**`.`**<mark style="color:red;">**`major`**</mark>`.`<mark style="color:orange;">**`minor`**</mark>`.`<mark style="color:yellow;">**`hotfix`**</mark>\
In which the rules are:

<details>

<summary><mark style="color:purple;">Game State</mark></summary>

Refers to the overall state of the game. `0.x.x.x` version indicates the game is still in a alpha/beta/pre-complete phase. Once we have reached a point where we have ported over most of the systems and content from ss13, and feel satisfied, we can then move to `1.x.x.x` and b~~e~~yond with new content.

</details>

<details>

<summary><mark style="color:red;">Major</mark></summary>

Refers to large **milestone**. Major milestones are large changes that may span numerous months and PRs.

An example of a major milestone would be several new systems or reworked systems that together make up a large change in how the game feels. Milestones will have their version number in their name. e.g. "**0.2 - Milestone Name"**.

</details>

<details>

<summary><mark style="color:orange;">Minor</mark></summary>

Refers to small **milestones**. Minor milestones are usually a single large system or a collection of smaller changes.

An example might be a rework to the health system, or a collection of new content for a couple recently added systems.&#x20;

</details>

<details>

<summary><mark style="color:yellow;">Hotfix</mark></summary>

Refers to quick fixes post a <mark style="color:red;">major</mark> or <mark style="color:orange;">minor</mark> release. An example would be a critical bug that was undetected until after release and needs to be quickly fixed.

Any example might be a bug that prevents players from joining and needs to be updated in a release ASAP instead of waiting for the next <mark style="color:orange;">minor</mark> release.

</details>

## Automated Releases

Soon we will move to automated releases much like many of the SS13 servers and such. First they will likely start off as monthly releases but after we gain a lot of momentum we will eventually move to nightly releases.

These will be registered as <mark style="color:yellow;">hotfix</mark> releases. Devs will still be able to push manual releases at anytime for <mark style="color:yellow;">hotfixes</mark> as well.


---

# 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/roadmap/releases.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.