> 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/default-values-cheatsheet.md).

# Default values cheat-sheet

Default values for every Ticket King setting.

What every setting starts at by default. Labels match the dashboard.

## Server Settings and Logging

| Setting                     | Default        |
| --------------------------- | -------------- |
| Server Language             | English (US)   |
| Main Embed Color            | #d4af37 (gold) |
| Max Active Tickets          | 500            |
| Max Active Tickets Per User | 1              |
| Support Roles               | None           |
| Main Ticket Categories      | None           |
| Opened Tickets Log Channel  | None           |
| Closed Tickets Log Channel  | None           |

## Ticket Claiming

| Setting                     | Default                    |
| --------------------------- | -------------------------- |
| Ticket Claiming Mode        | Enabled - Private on Claim |
| Ping Ticket Author on Claim | On                         |
| Roles to Add on Claim       | None                       |

## Ticket Style and Claiming

| Setting                             | Default      |
| ----------------------------------- | ------------ |
| Manual Ticket Style                 | Text Channel |
| Archive Thread Tickets              | Delete       |
| Continuous Ticket Numbering         | On           |
| Global Ticket Numbering             | On           |
| Ping Support Roles                  | Off          |
| Ticket Creates Private Staff Thread | Off          |
| Code-Wrap Question Responses        | Off          |

## Ticket Close and Transcript

| Setting                          | Default                          |
| -------------------------------- | -------------------------------- |
| Close Requires Support Role      | Off                              |
| Close Requires Reason            | Off                              |
| Hide Closing User                | Off                              |
| DM User Close Message            | On                               |
| Log Staff Message Counts         | On                               |
| Role-Specific Transcript Viewing | Off                              |
| Default Ticket Close Reason      | Blank (uses the built-in reason) |

## Ticket Autoclose

| Setting                                | Default |
| -------------------------------------- | ------- |
| Autoclose Leave                        | Off     |
| Auto-Close Inactivity (Premium)        | Off     |
| Auto-Close Inactivity Period (Premium) | 7 days  |

## Ticket Rating (Premium)

| Setting                   | Default                   |
| ------------------------- | ------------------------- |
| Ticket Rating             | Off                       |
| Ticket Rating Mode        | Rating + Optional Comment |
| Ticket Rating Log Channel | None                      |

## Steam Linking (Premium)

| Setting                | Default |
| ---------------------- | ------- |
| Steam Linking Duration | 30 days |

## New panel

| Setting                     | Default          |
| --------------------------- | ---------------- |
| Panel Type                  | Ticket Panel     |
| Default Ticket Style        | Text Channel     |
| New button color            | Secondary (grey) |
| New question response style | Paragraph        |
| New question Required       | Off              |

## Bot Personalizer (Premium)

| Setting  | Default                            |
| -------- | ---------------------------------- |
| Bot Name | Empty (uses the bot's normal name) |
| About Me | Empty                              |
| Avatar   | None                               |
| Banner   | None                               |

## New custom command (Premium)

| Setting                  | Default |
| ------------------------ | ------- |
| Enabled                  | On      |
| Ticket Only              | Off     |
| Delete Command Message   | Off     |
| Reply to Command Message | On      |
| Allow All Staff          | Off     |
| Allowed Roles            | None    |

## New application option

| Setting                | Default                                     |
| ---------------------- | ------------------------------------------- |
| Allow Reapplication    | On                                          |
| Cooldown Period        | None (shown when Allow Reapplication is on) |
| Min Account Age        | None                                        |
| Min Server Membership  | None                                        |
| DM Result to Applicant | On                                          |

## Related

{% content-ref url="/pages/98HCTUU4LdSQxw2WPDnQ" %}
[Limits cheat-sheet](https://ticketking.xyz/docs/reference/limits-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/default-values-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.
