> For the complete documentation index, see [llms.txt](https://striga.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://striga.gitbook.io/docs/updates-and-versions.md).

# Updates & Versions

How Striga scripts tell you about updates, and which versions work together.

## Current versions

| Script                | Resource           | Version   | Needs striga-core |
| --------------------- | ------------------ | --------- | ----------------- |
| Striga Core           | `striga-core`      | **0.1.0** | -                 |
| Striga Tokyo HUD      | `striga-tokyo-hud` | **1.0.0** | 0.1.0 or newer    |
| Striga Chat           | `striga-chat`      | **1.0.0** | 0.1.0 or newer    |
| Striga Notify         | `striga-notify`    | **1.0.0** | 0.1.0 or newer    |
| Striga Text UI        | `striga-text-ui`   | **1.0.0** | 0.1.0 or newer    |
| Striga Inventory      | `striga-inventory` | **1.0.0** | 0.1.0 or newer    |
| Striga Multicharacter | `striga-multichar` | **1.0.0** | 0.1.0 or newer    |

***

## Update check

**striga-core** checks for new versions of every Striga script on your server:

* the first check runs **10 seconds** after the server starts, then **every 6 hours**
* it reads one public file: `versions.json` from [github.com/Striga7z/striga-core](https://github.com/Striga7z/striga-core)
* it never stops or changes anything, it only prints

When a script is out of date, you see a red line in the server console:

```
[striga-core] UPDATE: striga-notify 1.0.0 -> 1.0.1. Download: https://...
```

A short note about the update can follow on the next line.

{% hint style="info" %}
If the check cannot reach GitHub, you see one yellow `version check failed` line. It tries again in 6 hours. Your scripts keep working.
{% endhint %}

### Turn it off

In `striga-core/config.json`:

```json
"versionCheck": false
```

Restart striga-core.

***

## Minimum core version

Every Striga script says in its `fxmanifest.lua` which striga-core it needs:

```lua
striga_core_min '0.1.0'
```

| Situation                 | What happens                                                             |
| ------------------------- | ------------------------------------------------------------------------ |
| striga-core is missing    | The script does not start (striga-core is a `dependency`)                |
| striga-core is too old    | striga-core stops the script and prints a red line in the server console |
| striga-core is new enough | The script starts                                                        |

The red line looks like this:

```
[striga-core] striga-chat needs striga-core >= 0.1.0 (installed 0.0.9). Update striga-core.
```

{% hint style="success" %}
**Fix:** download the newest striga-core and restart the server.
{% endhint %}

***

## How to update a script

{% stepper %}
{% step %}

### Download

Download the new version from [portal.cfx.re](https://portal.cfx.re) → **Granted Assets**. See [Claim Purchase](/docs/claim-purchase.md).
{% endstep %}

{% step %}

### Keep your edits

Save a copy of the old `editable/` folder (config and translations).
{% endstep %}

{% step %}

### Replace

Replace the old folder with the new one. Copy your changes back into the new `editable/` files (new versions can add options, so compare instead of overwriting).
{% endstep %}

{% step %}

### Update striga-core too

If the script needs a newer striga-core, update striga-core first.
{% endstep %}

{% step %}

### Restart

Restart the server.
{% endstep %}
{% endstepper %}


---

# 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://striga.gitbook.io/docs/updates-and-versions.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.