> For the complete documentation index, see [llms.txt](https://docs.ucr.ucserver.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ucr.ucserver.it/commands/spawn.md). # Spawn If you need to spawn manually a Custom Role you can use the **Spawn** command. ### Syntax ``` ucr spawn (method) ``` ### Permission ``` ucr.spawn ``` ### Description With this command you can spawn **one or more player** as a Custom Role. The method parameter allows you to decide if spawn the role synchronously or asynchronously.\ If you need to spawn it **synchronously** then put `sync` as method. ### Player pointers There are different pointers that you can use to point a single player, a defined group of player or everyone. If you put **a simple player id or name** then only the selected player will be spawned as the Custom Role. If you put **different player ids, divided by a comma** (`,`) then these players will be spawned as the Custom Role. If you put `all` then every player in the server will be spawned as the Custom Role. If you put `spectators` or `spect` then only the spectators will be spawned as the Custom Role. If you put `alive` or `al` then only the alives will be spawned as the Custom Role. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ucr.ucserver.it/commands/spawn.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.