# Understanding the Functionality of Tempy Tags

## What are Tempy Tags?

The Tempy tag is a special tool that can be used within the Tempy Discord bot to reference information about a user or guild. By using the Tempy tag in a specific format, the bot is able to replace the tag with the corresponding information at runtime. This allows users to customize the behavior of Tempy and tailor it to their specific needs. In this documentation, we will be discussing the functionality of the Tempy tag and how it can be effectively used within the Tempy Discord bot. Understanding the use and capabilities of the Tempy tag is essential for making the most of the features offered by Tempy.

## How Do Tempy Tags Work?

{% hint style="success" %}
Copy and paste the Tempy tag(s) shown in the table to customize the Tempy channel names during setup or configuration.
{% endhint %}

<details>

<summary>Examples</summary>

* `/global name {user}'s Channel`\
  Any temporary channels created will be named after the user who created them, followed by "'s Channel". So if a user with the name "ARealWant" and the descriminator "0001" creates a new channel, the channel will be named **"ARealWant#0001's Channel"**.
* `/global name {user.name}'s Channel`\
  Any temporary channels created will be named after the user who created them, followed by "'s Channel". So if a user with the name "ARealWant" creates a new channel, it will be named **"ARealWant's Channel"**.
* `/global name #{tempy_count} | {user.name}'s Channel`\
  Any temporary channels created will be named with a number representing the order in which they were created, followed by a pipe symbol "|" and the name of the user who created them, followed by "'s Channel". So if a user with the name "ARealWant" creates a new channel, it will be named **"#1 | ARealWant's Channel"** if it is the first channel created, "#2 | ARealWant's Channel" if it is the second channel created, and so on.

</details>

| Tempy Tag             | Description                                                | Replaced Examples      |
| --------------------- | ---------------------------------------------------------- | ---------------------- |
| {tempy\_count}        | References the amount of Tempy voice channels              | *14*                   |
| {voice\_count}        | References the amount of all voice channels                | *14*                   |
|                       |                                                            |                        |
| {user}                | References the user object.                                | *ARealWant#0001*       |
| {user.name}           | References the name of the user.                           | *ARealWant*            |
| {user.discriminator}  | References the discriminator of the user.                  | *0001*                 |
| {user.id}             | References the unique ID of the user.                      | *754634421457387670*   |
| {user.created}        | References the date and time the user account was created. | *2022-05-31 18:35:21*  |
|                       |                                                            |                        |
| {guild.name}          | References the name of the guild.                          | *My favourite server!* |
| {guild.id}            | References the unique ID of the guild.                     | *787660599826972683*   |
| {guild.member\_count} | References the number of members in the guild.             | *100*                  |
| {guild.created}       | References the date and time the guild was created.        | *2022-05-31 18:35:21*  |


---

# Agent Instructions: 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:

```
GET https://docs.tempybot.me/faq-and-more/tempy-tags.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.