# Tier 2

<mark style="color:red;">**Required**</mark>\*\* parameters will be in \[Square brackets]\*\*

<mark style="color:green;">**Optional**</mark>\*\* parameters will be in (Curly brackets)\*\*

## :crown: Admin only

***

## :crown: Rename Teams

```
/premium rename_teams [blue] [red] [queue_channel]
```

<figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FKGyfH8g7S9PQjDYmrKek%2Frename_teams.png?alt=media&#x26;token=e4aa04bb-8ee0-4571-9149-24e371e9943d" alt=""><figcaption></figcaption></figure>

Are you bored with the standard "Blue" and "Red" team names? Use this command to change the names! This works especially well with [Roster](https://docs.inhousequeue.xyz/docs/commands/game-modes#rosters) queue feature. This feature operates on a **per-queue** basis. So, you may have a different set of team names for each queue.

### How it works

For the [Roster](https://docs.inhousequeue.xyz/docs/commands/game-modes#rosters) game mode, names are immediately displayed. This is because the teams you see in the queue will be the final teams.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FwQ1lrB94v4bbOzuztkA6%2Fteam_names_queue_team-based.png?alt=media&#x26;token=3e212b8d-8ad8-4102-80ed-95a2a64ef86b" alt=""><figcaption></figcaption></figure></div>

For all other game modes, the dedicated team names will only be visible inside a lobby channel (Channels explained [here](https://docs.inhousequeue.xyz/docs/quick-start#channels-and-categories-explained)) once a game has started. This is because the teams are only final once <mark style="color:red;">InHouseQueue</mark> has created balanced teams, or randomised the teams.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2F9ZFlq7gIDW9vRFwEit45%2Fchange_teams_lobby.png?alt=media&#x26;token=fc32d0e8-26e0-4952-86c3-6990d8052694" alt=""><figcaption></figcaption></figure></div>

Voice channels will also be renamed

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2Fz0ZHhLRElpxWOiWqcEUc%2Frename_teams_voice.png?alt=media&#x26;token=5a1b28c9-0603-4544-981a-99f36dc43b66" alt=""><figcaption></figcaption></figure></div>

Match history will also include the team names.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FkHquJoHSDrs0iD50sT84%2Fchange_teams_match_history.png?alt=media&#x26;token=f595341c-ccf9-450d-ad1e-cf1d64c1c676" alt=""><figcaption><p>Match history</p></figcaption></figure></div>

***

## :crown: List teams

```
/premium list_teams
```

If you have added many [custom team names](#crown-rename-teams) and need a reminder, this command gives you a quick overview of all the team names you've set and their associated queue channels.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FeImnoV1frWu5HqBw4xw0%2Flist_team_names_embed.png?alt=media&#x26;token=1839d866-a471-4e91-a0fe-ffdb8f7c4c39" alt=""><figcaption></figcaption></figure></div>

***

## :crown: Hide players names

```
/premium anonymize [preference] [queue_channel]
```

This command will hide player names as they join the queue. Players will remain anonymous until a match starts. This also works for [Duo queue](https://docs.inhousequeue.xyz/docs/commands/queue-commands#crown-toggle-duo-queue) and [Roster](https://docs.inhousequeue.xyz/docs/commands/game-modes#rosters) game mode. This option can be enabled on a per-queue basis.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FTKKypQpkSNJLkwRMivT1%2Fhide_player_names_acitivate.png?alt=media&#x26;token=57d3a295-f99f-4fdb-b287-42336d89011c" alt=""><figcaption></figcaption></figure></div>

### How it works

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FYBBmvGiruJ29ulOOMhvA%2Fhide_player_names.png?alt=media&#x26;token=94eaddb1-e8c2-4274-b2a2-86978c4ab718" alt=""><figcaption><p>Anonymous Players in queue</p></figcaption></figure></div>

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FM5aCVT8REYwXBV0P4oBf%2Fhide_player_names_duo.png?alt=media&#x26;token=ed4b0959-8325-4044-9bfb-f8c1d6f30175" alt=""><figcaption><p>Anonymous Players in Duo drop down</p></figcaption></figure></div>

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FprbngNFNQKGji0jmWQ8Y%2Fhide_player_names_duo_accepted.png?alt=media&#x26;token=812c302c-4438-4ca4-a33d-7c166e6a9613" alt=""><figcaption><p>Anonymous Players in successful duo</p></figcaption></figure></div>

***

## :crown: Ready up Penalties

```
/premium ready_penalty [preference] (duration_1) (duration_2) (duration_3)
```

Have one or two players who never seem to ready up on time? You can bring in small punishments for players who are not ready.

Once enabled, players that don't ready up are given a temporary queue ban. Failing to ready up increments the offence counter by +1, up to a maximum of 3.

At the highest penalty level (tier 3), players must wait the full tier 3 penalty time until they successfully ready up at least once. For example, assuming the maximum penalty of 1 hour, If a player misses a ready check while at warning level 3, they will face a 1-hour wait every time they miss a ready check.

### How it works

1. Run the command and enter an amount. For example for 5 minutes enter `5m`, for 3 hours 5 minutes enter `3h 5m`. The maximum wait time you can set is `24h` or `1d`, the minimum is `1m` for one minute;
2. If a player misses the ready check, they will have to wait for the duration you set for `first_offence_duration` .
3. Once they wait out the ban, they can queue again. If they fail to ready up again, they will then wait for the duration you set for `second_offence_duration`. If they fail to ready up the third time, they will stay on the `third_offence_duration` until they learn not to AFK while in a queue!
4. The default durations are 5, 10 and 15minutes.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FpRzYLaIoaOlaDw1neUrv%2Fready_penalty_values.png?alt=media&#x26;token=d553b65b-db9e-4c96-85ff-a27d0d6fe648" alt=""><figcaption><p>Ready Up Penalty enabled</p></figcaption></figure></div>

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FCPFzodTi0tSI799WT8jw%2Fready_check.png?alt=media&#x26;token=d67c3f4a-b5d1-4c9c-a68d-d8476d97bc5c" alt=""><figcaption><p>Player is temporary banned from Queue</p></figcaption></figure></div>

***

## :crown: Reset penalties for a user or the whole server

Remove a queue ban from a player, or your whole server with these two commands

```
/premium reset_server_penalties

/premium reset_user_penalty [user]
```

***

## :crown: View ready-up penalty settings

A dashboard is available to view your ready penalty configuration and track current player penalties.

```
/premium ready_penalty_info
```

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FbNVhcvFMFkhO000j1YEc%2Fready%20penalty%20info.png?alt=media&#x26;token=352fd0c6-8bdd-49e3-82a9-7cdaa2a002c1" alt=""><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FB7oxclWu3j1KRrkbv2sw%2Fready%20penality%20users.png?alt=media&#x26;token=9d66178c-bf12-4eea-8d50-badda4428635" alt=""><figcaption><p>Player is temporary banned from Queue</p></figcaption></figure></div>

***

## :crown: Best of 3 or 5 series

```
/premium best_of_series [preference] [queue_channel] [series_type]
```

Best of 3 or 5.

### How it works

This will be enabled on a per-queue basis. So you may have a dedicated queue channel for best of 3 or 5 series. This feature works especially well with [Roster Mode](https://docs.inhousequeue.xyz/docs/commands/game-modes#rosters), as it aligns perfectly with Scrims.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FNWq3hDPDFiNdoQHlYHeW%2Fbest_of_series-command.png?alt=media&#x26;token=4c66d938-30c9-4a67-80b9-c29403709302" alt=""><figcaption></figcaption></figure></div>

Players will be reminded in the lobby that it's a best of 3 or 5. Admins or players will be required to end a game every time a match finishes within a series. Feel free to take a break between matches!

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FDLANA0D8kzkRQAjcEWTi%2Fbest_of_series_3.png?alt=media&#x26;token=f1a1976e-d287-4190-b692-5c1b3e7a352e" alt=""><figcaption></figcaption></figure></div>

Once a series has been completed, the scores will be attached to the match history embed.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FX269wRjHt3elQ3hoB6F8%2Fbest_of_series_history.png?alt=media&#x26;token=ca069a22-55c1-4438-9833-9cbdb2ed8edd" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
As of writing, **one** series counts as **one** game. For example, a best of 3 will not count as 3 total games or 3x MMR.
{% endhint %}

***

## MMR Decay system

```
/premium decay [game]
```

**MMR Decay** is a system designed to keep the matchmaking rankings fair and competitive. It ensures that player rankings accurately reflect current activity and skill levels. If a player becomes inactive for a certain period, their Matchmaking Rating (MMR) will gradually decrease over time.

### Features

* **Inactivity Period**: If you don't play any matches for a specified number of days, your MMR will begin to decay.
* **Decay Amount**: The amount of MMR deducted depends on your current MMR and the decay settings. The decay can be a fixed number or a percentage of your current MMR.
* **Decay Intervals**: MMR decay happens at regular intervals. For example, after **14 days** of inactivity, decay may occur, and it can repeat if inactivity continues.
* **Notifications**: You'll receive a warning **1 day** before your MMR starts to decay, giving you a chance to play and reset the decay timer.
* **Exemptions for Specific Games**: Administrators can exempt players from MMR decay for particular games.

### How it works

1. Run `/premium decay [game]`You will see the MMR Decay menu. Here is where you can adjust all settings related to MMR Decay.

{% hint style="warning" %}
[Global leaderboards](https://docs.inhousequeue.xyz/docs/quick-start/leaderboards-explained#how-does-the-leaderboard-work) **ALL** share decay settings. You do not need to select every channel individually. Only select another channel if it's a [Unique leaderboard](https://docs.inhousequeue.xyz/docs/quick-start/leaderboards-explained#creating-a-unique-leaderboard).
{% endhint %}

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FGfPjoGjBXC4AFiGZ7l4p%2Fdecay_menu.png?alt=media&#x26;token=7b57a668-6a99-4a24-93e0-9d7049c480ab" alt=""><figcaption><p>MMR Decay Menu!</p></figcaption></figure></div>

2. Select the channel you want to manage using the dropdown. If the channel you select is a :globe\_with\_meridians:<mark style="color:blue;">Global leaderboard</mark>, the same decay settings will apply to **ALL** :globe\_with\_meridians: <mark style="color:blue;">Global leaderboard</mark> queues. Read more about how leaderboards work [here](https://docs.inhousequeue.xyz/docs/quick-start/leaderboards-explained).

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FntGKU1GYwdwtPjpPFj7g%2F1.5_decay.png?alt=media&#x26;token=ef41e19d-3b69-49df-96b6-b186e39aa6b2" alt=""><figcaption></figcaption></figure></div>

3. Next, click on <mark style="color:purple;">**Set Decay amount**</mark> :chart\_with\_downwards\_trend:. This is how much MMR will be removed. For this example, we will use **30**.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FIuplaFU6lUqqDI35lmcQ%2F2_decay.png?alt=media&#x26;token=68fa565c-0868-4924-b86e-b641fa78f489" alt=""><figcaption></figcaption></figure></div>

4. Next, we can change the <mark style="color:purple;">**Decay type**</mark> :arrows\_counterclockwise:. This will toggle between **percentage** and **flat** for the **Decay amount.** For this example, we will use **percentages** as we think this scales better.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2Fg33yYFXb98JEsimbNf8O%2F3_decay.png?alt=media&#x26;token=788c105d-2d45-4311-a521-6641aeda87ce" alt=""><figcaption></figcaption></figure></div>

5. Next, we will set our **MMR intervals** :calendar:**.** This is how many days the players within each MMR bracket can stay inactive before decay. For this example we will have these settings:
   1. Players with <mark style="color:purple;">1000 MMR</mark> and **above**, will decay after <mark style="color:green;">**20 days**</mark> of inactivity.
   2. Players with <mark style="color:purple;">2000 MMR</mark> and **above**, will decay after <mark style="color:green;">**10 days**</mark> of inactivity.
   3. Players with <mark style="color:purple;">3000 MMR</mark> and **above** will decay after <mark style="color:green;">**5 days**</mark> of inactivity.
   4. Players with <mark style="color:purple;">4000 MMR</mark> and **above** will decay after <mark style="color:green;">**3 days**</mark> of inactivity.

{% hint style="info" %}
Players **UNDER** 1000 MMR decay after **365** days by default. This cannot be changed. So, in most cases never :relaxed:
{% endhint %}

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FYXStZKUhbpKI4dkMbXmg%2F4_Decay.png?alt=media&#x26;token=961aa3d8-e3f0-49c2-91a5-011a6a53693d" alt=""><figcaption></figcaption></figure></div>

6. Lastly, make sure always to save!

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FNouDZ4Th1iQNtVfPwi2b%2F5_decay.png?alt=media&#x26;token=ed750457-2e1b-41e9-9771-2bd5883d2b47" alt=""><figcaption></figcaption></figure></div>

That's all for setup!

### Decay Events

<mark style="color:red;">InHouseQueue</mark> will direct message members 1 day before they are due to decay. This is considered a warning message. This will also be logged in your InHouseQueue [log channel](https://github.com/InHouseQueue/In-HouseQueue/blob/public-docs/public-docs/commands/server-commands/README.md#server-logs).

<figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FcxWXH1vFJehK4euG5ckm%2Fdecay_warning_message.png?alt=media&#x26;token=1f01589b-9ce4-4270-9e38-d7af9b714114" alt=""><figcaption><p>Direct Message from InHouseQueue warning the player.</p></figcaption></figure>

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FWpNH3OSbrzr4aYHkycQx%2F6_decay.png?alt=media&#x26;token=888b6c7a-9c45-47e6-a90b-db128b22aa5e" alt=""><figcaption><p>MMR Decay is logged in the Admin Logs channel</p></figcaption></figure></div>

On the day of the Decay, InHouseQueue will DM the player notifying them of their decay and how much they lost. Players can opt out of receiving DM's by running `/decay_nofitifcations` inside the server.

<mark style="color:red;">**Players will decay every day until they play a game.**</mark>

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FcxY7BdsmMwcAFJV914xK%2Fdecay_stop.png?alt=media&#x26;token=1fd1e90b-180c-4cec-9350-7da63815dbd2" alt=""><figcaption><p>DM from InHouseQueue when a member decays</p></figcaption></figure></div>

***

## Ignore Decay

Allow certain members to be exempt from decay. This is useful if a member won't be able to play for an extended period.

```
/premium ignore_decay [user] [game] [exempt]
```

## Apply decay manually

InHouseQueue will automatically apply decay once a day. If you don't wish to wait you can initiate the Decay event yourself at any point.

If the channel you select is a :globe\_with\_meridians:<mark style="color:blue;">Global leaderboard</mark>, the same decay settings will apply to **ALL** :globe\_with\_meridians: <mark style="color:blue;">Global leaderboard</mark> queues. Read more about how leaderboards work [here](https://docs.inhousequeue.xyz/docs/quick-start/leaderboards-explained).

```
/premium apply_decay [game] [queue_channel]
```
