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

# Troubleshooting & FAQ

Quick solutions for common questions and setup issues with Zynox Restart Warning

***

## 🛠️ Common Issues & Fixes

### 1. 🔇 No Sound or Voice Announcement Heard

* **Potential Cause 1**: The client has muted FiveM NUI CEF audio in Windows Volume Mixer.
  * **Fix**: Press Alt+Tab, right-click the Windows Volume icon, open **Volume Mixer**, and ensure **FiveM CEF** (Chromium Embedded Framework) is not muted or set to 0.
* **Potential Cause 2**: In-game Master / SFX Volume is too low.
  * **Fix**: Check `Settings ➔ Audio` in the FiveM pause menu.
* **Potential Cause 3**: Audio volume values in `config.lua` are too low.
  * **Fix**: Check `Config.Warning1Volume`, `Config.Warning2Volume`, and `Config.BackgroundMusicVolume` in `config.lua`. Ensure they are set between `0.4` and `1.0`.

***

### 2. ⏳ Warning Does Not Automatically Trigger on txAdmin Restarts

* **Potential Cause 1**: txAdmin Scheduled Restarts are disabled.
  * **Fix**: Open txAdmin (`http://<ip>:40120`) ➔ **Settings** ➔ **FXServer** ➔ Ensure **Scheduled Restarts** are configured and saved.
* **Potential Cause 2**: Warning times in `config.lua` do not match txAdmin intervals.
  * **Fix**: In `config.lua`, ensure `Config.WarningTimes` includes the countdown minutes txAdmin announces (default: `{ 15, 10, 5, 2, 1 }`).
* **Potential Cause 3**: txAdmin Announcements are disabled.
  * **Fix**: In txAdmin FXServer settings, ensure the **Announcements** toggle is turned **ON**.

***

### 3. 🚫 "You do not have permission to execute this command"

* **Potential Cause**: The player executing `/testrestart` lacks the required ACE permission.
* **Fix**: Add the following line to your `server.cfg`:

  ```cfg
  add_ace group.admin command.testrestart allow
  ```

  And verify that your player identifier is added to `group.admin`.

***

### 4. ⚡ Streetlights / City Power Does Not Flicker or Shut Off

* **Potential Cause 1**: `Config.EnablePowerFlicker` is set to `false`.
  * **Fix**: Open `config.lua` and set `Config.EnablePowerFlicker = true`.
* **Potential Cause 2**: Another script is continuously overriding `SetArtificialLightsState()`.
  * **Fix**: Some blackout scripts or map mods may force lights on every frame. Disable any third-party blackout resources to prevent conflicts.

***

### 5. ⛈️ Weather Snaps Back Instantly or Does Not Change

* **Potential Cause**: An external weather synchronization resource is overriding the world weather every tick.
* **Fix**: If you use scripts like `vSync`, `cd_easytime`, or `qb-weathersync`:
  * **Option A**: In `config.lua`, set `Config.EnableWeatherTransition = false` to let your weather resource handle it.
  * **Option B**: Use your weather resource's server export or admin command to trigger storm weather during server restarts.

***

## 🙋 Frequently Asked Questions (FAQ)

<details>

<summary><strong>Does this script require a paid TTS API key (like ElevenLabs or Google Cloud)?</strong></summary>

**No.** The script utilizes the client's built-in **Web Speech API** running directly inside FiveM's Chromium browser engine. It generates high-quality natural voice output 100% free, forever, with zero external subscription costs.

</details>

<details>

<summary><strong>What is the resmon / CPU performance of this resource?</strong></summary>

**0.00ms.** When idle between announcements, the script consumes zero CPU ticks. During the active emergency sequence (sirens + light surges), it runs smoothly at under 0.01ms.

</details>

<details>

<summary><strong>Can I translate or customize the voice announcement text?</strong></summary>

**Yes!** In `config.lua`, you can edit `Config.SpeechText` to any text or language you want. You can also change `Config.SpeechLanguage` (e.g. to `"es-ES"`, `"fr-FR"`, `"de-DE"`).

</details>

***

## 💬 Still Need Help?

If you've followed these steps and are still facing difficulties, join our [**Discord Server**](https://discord.gg/zynox) and open a support ticket.


---

# 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/troubleshooting.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.