> For the complete documentation index, see [llms.txt](https://docs.uct.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.uct.ucserver.it/custom-teams/first-steps.md).

# First steps

## What's a Custom Team?

Custom Team defines a unit consisting of Custom Roles, designed to replicate teams such as the Nine-Tailed Fox or Chaos Insurgency. The plugin supports extensive configuration through easy-to-manage `YML` files.

UCT is compatible with UCR (UncomplicatedCustomRoles); this integration allows roles defined in either UCR or UCT to spawn during a Custom Team spawn wave.

## Why mention roles from UCT or UCR?

Since UCT utilizes UCR to register Custom Roles internally, UCT Roles and UCR Roles **must not share the same ID.** However, if you want to import an existing role from UCR to UCT, you simply need to set the UCR role ID in place of the UCT role ID. Remember to also change the role name!

### Folder structure

UCT maintains a straightforward directory structure.

Located at `LabAPI/configs/UncomplicatedCustomTeams/{your-server-port}`, you will find `example-team.yml`, which contains the default Custom Team config.

To create new team files in the port folder, you can:

* Manually: Copy and paste existing files.
* Automatically: Run the command `uct generate <name>`.


---

# 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.uct.ucserver.it/custom-teams/first-steps.md?ask=<question>&goal=<endgoal>
```

`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.