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

# Installation & setup

Install ped models and distinguish asset issues from menu, appearance, or animation issues.

## Install and test the model

Copy the complete ped package and start it as instructed. Check whether the package is a full add-on ped or clothing/components for an existing model. These require different integrations.

Test the specified model name using an existing ped menu or suitable administration tool. Starting the resource does not automatically create an NPC or replace the player model.

## Connect your server systems

Add the model to your ped, spawn, or administration menu. For persistent player models, your appearance/skin system must support saving the model and loading it again on login. Not every system supports arbitrary add-on peds.

Check separately whether another script resets the model on login, job change, or death.

## Common symptoms

| Symptom                                  | First check                                                    |
| ---------------------------------------- | -------------------------------------------------------------- |
| Model unavailable                        | Exact model name, running resource, complete files             |
| Fully or partly invisible                | Original package, conflicting model names, included components |
| Returns to the default model after login | Appearance-system save and restore settings                    |
| Movement or animations look wrong        | Animations and rig behavior intended for that ped              |
| Model missing from a menu                | Menu configuration and model allowlist                         |

## Test safely

1. Test the untouched package without additional ped mods on a development server.
2. Check standing, walking, and the actions intended for the product.
3. Compare with a second client to see whether the issue affects everyone or one player.
4. Re-enable appearance and menu integrations one at a time.

Do not edit protected model files to troubleshoot. Report a reproducible issue with the model name, product version, and a short video.

[Models & textures](/studioworks-docs/troubleshooting/models-textures.md) · [Prepare a support ticket](/studioworks-docs/support/preparing-a-ticket.md)

***

[StudioWorks Store](https://tebex.studio-works.net/) · [Discord & Support](https://discord.gg/UmqU67rp4v)


---

# 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://studioworks.gitbook.io/studioworks-docs/peds/installation.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.