> For the complete documentation index, see [llms.txt](https://zynoxdev.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://zynoxdev.gitbook.io/docs/zynox-resources/zx_tsunami/installation.md).

# Installation

Zynox Studio Documents > ZYNOX RESOURCES > 🌊 ZX - Restart Warning

## 📥 Installation

Dependencies, drag and drop setup, server.cfg order, txAdmin, and a quick test.

***

### 1️⃣ Check dependencies

Make sure your server environment meets the basic prerequisites:

* **Artifacts**: FXServer Recommended Build **5848** or higher.
* **Framework**: Compatible with **Qbox**, **QBCore**, **ESX Legacy**, **vRP**, or **Standalone**.
* **txAdmin**: Enabled on your server for automated restart event triggers.
* **External Libs**: None! (0 external script dependencies required).

***

### 2️⃣ Add the resource

1. Download the resource from your [Cfx.re Keymaster Grants](https://keymaster.fivem.net/asset-grants).
2. Extract the downloaded `.zip` archive.
3. **Drag and drop** the resource folder into your server's `resources` directory:

   ```
   resources/
   └── Zynox_Restart_Warning_escrow/
   ```

   *(You may rename the folder to your preferred convention, such as `zx_restart_warning`)*.

> \[!TIP] Ensure the folder name does not contain spaces or unusual special characters.

***

### 3️⃣ Update server.cfg

Open your `server.cfg` file and add the startup command:

```cfg
ensure Zynox_Restart_Warning_escrow
```

> \[!NOTE] If you organize your resources inside sub-categories (e.g. `[scripts]` or `[assets]`), make sure the folder name is ensured or start the resource directly.

***

### 4️⃣ Permissions setup

The manual admin simulation command `/testrestart` is protected by FiveM ACE permissions (by default `command.testrestart`).

Add the following to your `server.cfg` or `permissions.cfg`:

```cfg
# Grant permission to your server admin group
add_ace group.admin command.testrestart allow

# Or grant to a specific moderator group
add_ace group.mod command.testrestart allow

# Or grant to a specific player license identifier
# add_principal identifier.license:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx group.admin
```

***

### 5️⃣ txAdmin Scheduled Restarts

To have emergency announcements trigger automatically when a scheduled server restart approaches:

1. Open your **txAdmin Web Panel** (`http://<server-ip>:40120`).
2. Go to **Settings** ➔ **FXServer**.
3. Under **Scheduled Restarts**, enter your daily restart times (24-hour format separated by commas):

   ```
   00:00, 06:00, 12:00, 18:00
   ```
4. Verify that **Announcements** are enabled in txAdmin.
5. Click **Save FXServer Settings**.

When txAdmin reaches the remaining minutes listed in `Config.WarningTimes` (default: 15, 10, 5, 2, 1), the resource automatically catches the event and broadcasts the disaster warning.

***

### 6️⃣ Test in-game

Join your server and verify everything works using the built-in test commands:

#### Trigger a 5-minute warning test:

```
/testrestart 5
```

* High-intensity siren sounds.
* AI voice broadcasts the countdown announcement.
* Streetlights flicker, surge, and plunge into blackout.
* Sky smoothly transitions to stormy thunder.

#### Test cancellation ("All-Clear"):

```
/testrestart cancel
```

* Halts active sirens.
* Plays friendly "threat passed" voice broadcast.
* Instantly restores electrical grid and sunny clear weather.

***

-# © 2026 Zynox Development • [Official Store](https://zynoxdev.tebex.store/) • [Discord](https://discord.gg/2yuPTmsqjX)


---

# 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://zynoxdev.gitbook.io/docs/zynox-resources/zx_tsunami/installation.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.