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

# Troubleshooting

Fixes for the most common issues.

**"You do not have access to jumpscares."** Add `add_ace group.admin rayn_jumpscare.use allow` to `server.cfg` and check that your player is in `group.admin`, or add your framework group to `Config.adminGroups`.

**Character names are not shown** Start `rayn_jumpscare` after your framework and check `Config.showCharacterName = true`.

**My jumpscare does not appear in the panel** Check the entry in `Config.jumpscares` and restart the resource. The `image` and `sound` names must match the files in `html/jumpscares/` exactly (letter case too).

**The video is black or does not play** Convert it to `.webm` (VP8/VP9). Some `.mp4` files are not supported by the FiveM browser.

**Sound and picture are out of sync** For a video with its own sound set `sound = ''`. If you use a separate sound file, it follows the video automatically. Very large files may need a longer black screen to load.

**"This player was scared recently."** The cooldown is active. Wait or lower `Config.cooldown`.


---

# 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://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_jumpscare/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.