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

# Using the script

Commands, admin panel and player menu.

## Commands

| Command                | Who              | What it does                                    |
| ---------------------- | ---------------- | ----------------------------------------------- |
| `/pedmenu`             | players          | Your peds: use one or go back to your character |
| `/pedadmin`            | admins           | Admin panel                                     |
| `/pedadmin [id]`       | admins           | Admin panel with the player already selected    |
| `/setped [id] [model]` | admins / console | Gives a ped without the panel                   |

Command names are set in `Config.commands`.

## Admin panel

* **Players** – everyone online. Click a player to see the peds he owns.
* **Owned peds** – the selected player's peds. The default one is marked, the bin icon takes a ped away.
* **Catalog** – search by name or model, filter by category. **Give** adds the ped to the selected player.
* **⋯ on a card** – thumbnail menu: generate in game, set an image link or remove the thumbnail.
* **Generate missing** – makes thumbnails for every ped without a picture.

## Player menu

`/pedmenu` shows the player's peds. **Use** switches to the ped and makes it the default, so it is applied again after the next login. **Back to my character** loads the normal skin; the peds stay saved.

When a ped is taken away from a player who is using it, he goes back to his character automatically.


---

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