> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/reference/limits-cheatsheet.md).

# Limits cheat-sheet

Every cap and limit in Ticket King, in one table.

A single-page reference for every cap that applies in Ticket King.

## Panels and templates

| Limit                      | Free          | Premium   |
| -------------------------- | ------------- | --------- |
| Panels per server          | 10            | Unlimited |
| Templates per server       | 1             | 25        |
| Custom commands per server | Not available | 25        |

## Per panel

| Limit                            | Value                 |
| -------------------------------- | --------------------- |
| Component rows                   | 5                     |
| Buttons per row                  | 5                     |
| Buttons per panel (max)          | 25                    |
| Dropdown menus per panel         | Up to 5 (one per row) |
| Options per dropdown menu        | 25                    |
| Questions per option             | 5 free / 100 premium  |
| Embeds per panel message         | 10                    |
| Message content above the embeds | 2000 characters       |

## Per application option

| Limit           | Value                |
| --------------- | -------------------- |
| Questions       | 5 free / 100 premium |
| Decision reason | 1000 characters      |
| Decision note   | 1000 characters      |

## Per ticket

| Limit                         | Default                  | Range     |
| ----------------------------- | ------------------------ | --------- |
| Max active tickets per user   | 1                        | 1 to 2000 |
| Max active tickets per server | 500                      | 1 to 2000 |
| Ticket creation cooldown      | 10 seconds               | Fixed     |
| Rename cooldown               | 2 renames per 10 minutes | Fixed     |

## Transcripts

| Limit                            | Free  | Premium |
| -------------------------------- | ----- | ------- |
| Messages captured per transcript | 1,000 | 5,000   |

Transcripts are kept indefinitely. There is no expiry.

## Auto-close (Premium)

| Limit                        | Default | Options                           |
| ---------------------------- | ------- | --------------------------------- |
| Auto-close inactivity period | 7 days  | 6h, 12h, 1d, 2d, 3d, 7d, 14d, 30d |

## Roles and categories

| Limit                                                | Value   |
| ---------------------------------------------------- | ------- |
| Server-wide support roles                            | 25      |
| Server-wide blocked roles                            | 25      |
| Server-wide ticket categories                        | 25      |
| Support, required, blocked, or ping roles per option | 20 each |
| Categories per option                                | 10      |
| Roles to add on claim                                | 25      |
| Roles that can be given dashboard access             | 50      |

## Temporary dashboard access

| Limit                  | Value                                |
| ---------------------- | ------------------------------------ |
| Active links at a time | 1                                    |
| Duration options       | 30 minutes, 1 hour, 3 hours, 6 hours |

## Discord-side caps

| Limit                             | Value                                    |
| --------------------------------- | ---------------------------------------- |
| Channels per Discord server       | 500                                      |
| Active threads per Discord server | 1,000                                    |
| Channels per category             | 50                                       |
| Roles per Discord server          | 250                                      |
| Fields per pop-up form            | 5 (this sets the free-plan question cap) |

## Bot Personalizer (Premium)

| Limit                      | Value          |
| -------------------------- | -------------- |
| Bot name                   | 32 characters  |
| About Me                   | 190 characters |
| Avatar or banner file size | 5 MB           |
| Changes per hour           | 2              |

## Character limits (embeds)

| Field              | Cap  |
| ------------------ | ---- |
| Embed title        | 256  |
| Embed description  | 4096 |
| Embed field name   | 256  |
| Embed field value  | 1024 |
| Embed footer text  | 2048 |
| Embed author name  | 256  |
| Fields per embed   | 25   |
| Total embed length | 6000 |

## Character limits (buttons and dropdown menus)

| Field                            | Cap |
| -------------------------------- | --- |
| Button label                     | 80  |
| Link button URL                  | 512 |
| Dropdown menu placeholder        | 100 |
| Dropdown menu option label       | 100 |
| Dropdown menu option value       | 100 |
| Dropdown menu option description | 100 |

## Character limits (forms and messages)

| Field                              | Cap                                                                                                             |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| Question label                     | 45                                                                                                              |
| Question placeholder               | 100                                                                                                             |
| Question response length           | Set between 1 and 4000 (default 500)                                                                            |
| Custom Embed Content (per option)  | 2048                                                                                                            |
| Custom Ticket Message (per option) | 1024                                                                                                            |
| Admin Thread Message (per option)  | 1024                                                                                                            |
| Custom Ticket Name                 | 100 characters of format, placeholders included (the final channel name is separately capped at 100 by Discord) |

## Steam Linking (Premium)

| Limit                  | Default | Range         |
| ---------------------- | ------- | ------------- |
| Steam Linking Duration | 30 days | 1 to 365 days |

## Related

{% content-ref url="/pages/sM0Y0Pbydyr64Z8LYCJQ" %}
[Default values cheat-sheet](https://ticketking.xyz/docs/reference/default-values-cheatsheet.md)
{% endcontent-ref %}

{% content-ref url="/pages/DO8q2U0yqg5NpPKoSscT" %}
[Glossary](https://ticketking.xyz/docs/reference/glossary.md)
{% endcontent-ref %}


---

# 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://ticketking.xyz/docs/reference/limits-cheatsheet.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.
