> For the complete documentation index, see [llms.txt](https://docs.clashperk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clashperk.com/others/commands/roster/create.md).

# /roster create

Create a roster

Create a roster

## Options

| Name                      | Description                                                                |
| ------------------------- | -------------------------------------------------------------------------- |
| `clan`                    | Clan of the roster                                                         |
| `name`                    | Name of the roster                                                         |
| `category`                | Category of the roster                                                     |
| `import_members`          | Whether to import members from the clan                                    |
| `allow_unlinked`          | Whether to allow unlinked members                                          |
| `max_members`             | Roster size                                                                |
| `max_accounts_per_user`   | Max accounts per user                                                      |
| `min_town_hall`           | Minimum Town Hall level                                                    |
| `max_town_hall`           | Maximum Town Hall level                                                    |
| `min_hero_level`          | Minimum combined Hero level                                                |
| `roster_role`             | Roster role                                                                |
| `sort_by`                 | Sorting order of the roster member list                                    |
| `start_time`              | Roster start time (YYYY-MM-DD HH:mm, in 24 hours format)                   |
| `end_time`                | Roster end time (YYYY-MM-DD HH:mm, in 24 hours format)                     |
| `timezone`                | Search timezone by city or country (e.g. London, Singapore, India, Sydney) |
| `allow_group_selection`   | Whether to allow members to select group                                   |
| `require_group_selection` | Whether to require members to select group                                 |
| `group_selection_text`    | Custom text shown to members when they select a roster group               |
| `allow_multi_signup`      | Whether to allow multiple roster signups                                   |
| `use_clan_alias`          | Whether to use clan alias in the roster (created by /alias command)        |
| `roster_image_url`        | Image to be used in the roster embed                                       |
| `color_code`              | Hex color code of the roster embed                                         |


---

# 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://docs.clashperk.com/others/commands/roster/create.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.