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

# Troubleshooting

Fixes for the most common issues.

**"You do not have access."** Add `add_ace group.admin rayn_playerped.admin allow` to `server.cfg` or add your framework group to `Config.adminGroups`.

**The player does not get his ped after logging in** Raise `Config.applyDelay` (e.g. `5000`) if your clothing script loads the skin later.

**"Back to my character" does not load the clothes** Change `Config.ResetSkin` in `config.lua` to the event of your clothing script.

**An addon ped has no thumbnail** Vanilla thumbnails are downloaded automatically; addon peds need one made in game, a link or a file. See [Peds and thumbnails](/rayn-scripts-docs/rayn_playerped/peds-and-thumbnails.md).

**The thumbnail generator is greyed out** Start `screenshot-basic` before rayn\_playerped.

**The ped is not centred on the thumbnail** Change `offsetZ` in `Config.thumbnails.generator` and generate the thumbnail again.

**An addon ped does not spawn or shows the wrong model** Two resources stream a model with the same name. Keep one, or give the other files and its `peds.meta` entry a unique name and restart the server.


---

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