> 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/using-the-panel.md).

# Using the panel

Commands, panel and cooldown.

## Commands

| Command                       | What it does                                          |
| ----------------------------- | ----------------------------------------------------- |
| `/jumpscare`                  | Opens the panel                                       |
| `/jumpscare [id]`             | Sends the first jumpscare from the list to the player |
| `/jumpscare [id] [jumpscare]` | Sends the chosen jumpscare, e.g. `/jumpscare 12 eyes` |
| `jumpscare [id] [jumpscare]`  | The same from the server console                      |

The command name is set in `Config.command`.

## Panel

* **Players**: everyone online with character name, FiveM name, ID and ping. Your own row is marked. Use the search field to filter by name, character name or ID. The refresh button reloads the list.
* **Jumpscare library**: click a card to make it the default for every row. Click **Preview** to see and hear it on your own screen (no black screen, nothing is sent).
* **Per-player jumpscare**: the dropdown in a row changes the scare only for that player.
* **Black screen**: the slider sets how long the screen stays black before the scare, from 0 to 5 seconds.
* **Send**: sends the selected scare. A message at the top shows the result.

Close the panel with the X button or ESC. ESC also stops a preview.

## Cooldown

After a scare the same player cannot be scared again for `Config.cooldown` seconds. Sending to yourself ignores the cooldown, so you can test freely.


---

# 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/using-the-panel.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.