# Queue commands #### :crown: **Admin only commands** #### :bulb: **General command for everyone** **Required** parameters will be in \[Square brackets] **Optional** parameters will be in (Curly brackets) *** ## :crown: **Toggle test mode** ``` /queue test_mode [preference] ``` Enable or disable a test environment for trying out features. Once test mode is enabled, you'll only need 2 players to fully test all queue functionalities. Full instructions on how to use this are available [here](https://docs.inhousequeue.xyz/docs/quick-start#test-mode-)

*** ## :crown: Toggle Multiple-queue: ``` /queue join_limit [preference] ``` Change a member's permission to join two or more queues at the same time. However, once a game starts, players are **always** removed from **all other queues** they are in.

*** ## :crown: Toggle Duo queue Toggle the Duo queue feature. This allows 2 players to guarantee being on the same team in [MMR Game mode](https://docs.inhousequeue.xyz/docs/game-modes#mmr). Once activated, please send a fresh queue into your queue channel with `/start`. ``` /queue duo [preference] ``` ### How it works: 1. **Player 1** and **Player 2** **both** join the queue in separate positions/roles. 2. **Player 1** clicks the Duo button and selects the player they want to Duo with from the drop-down menu 3. They confirm their duo selection.

1. **Player 2** will receive a DM from InHouseQueue, they must accept this duo request.

1. Once **Player 2** has accepted the invitation, the duo is confirmed. 2. **Both** players will receive an emoji next to their names 1️⃣. This will happen when another player joins in the queue. If one player **DUOS** leaves the queue, their Duo status is removed.

{% hint style="danger" %} This feature will bypass MMR for Duo'd players. Keep this in mind when enabling in a more competitive environment. This can and will create unbalanced games. {% endhint %} *** ## :crown: **Toggle fill** Activate or deactivate the autofill option. An extra Fill button will appear in the queue. Players who join Fill will automatically be given a **random** available role once the game starts. Currently, Autofill only works for the [MMR Game mode](https://docs.inhousequeue.xyz/docs/game-modes#mmr) ``` /queue fill [preference] ```

*** ## Ready up timer ``` /queue ready_timeout [minutes] ``` Adjust the duration of the ready-up phase. This is how long players have to ready up once a game has been found. The default is 5 minutes. **Minimum Length:** 1 Minute **Maximum Length:** 30 Minutes

*** ## :crown: **Set a schedule** ``` /queue schedule ``` Define a schedule for queue availability. You can select Individual days of the week, or Everyday for full flexbility. InHouseQueue will automatically open your last queue at your start time. Afterwards, InHouseQueue will close the queue at the end time. ### How it works: 1. Run the `/queue schedule` command. 2. Select Add/Update schedule. 3. Select the queue you want a schedule for 4. Select your **Day** **timezone**, **start time** and **end time** To delete a schedule repeat steps 1,3, and 4, but select Remove schedule for step 2.

Players cannot join queue during the closed time

*** ## :crown: Lock a Queue to a Game mode ``` /queue mode [channel] [gamemode] /queue clear_mode [channel] ``` By default, changing the [Game Mode](https://docs.inhousequeue.xyz/docs/commands/game-modes) affects **all** queues on the server. For example, switching from [Captain mode](https://docs.inhousequeue.xyz/docs/game-modes#captain) to [MMR mode](https://docs.inhousequeue.xyz/docs/game-modes#mmr) will change **ALL** queues on your server to MMR mode. However, this command allows you to lock specific queues to certain game modes. This means you can have one queue dedicated to [Casual mode](https://docs.inhousequeue.xyz/docs/game-modes#casual), another for [Captain mode](https://docs.inhousequeue.xyz/docs/game-modes#captain), and so on. All valid game modes supported can be found [here](https://docs.inhousequeue.xyz/docs/commands/game-modes). {% hint style="info" %} This feature does **not** create separate leaderboards. Both queues will still count towards the same leaderboard. Unless you [change this](#crown-create-a-queue-with-its-own-leaderboard). {% endhint %} 1. Once you run the command, you will be asked if you wish to enable MMR for this queue.

2. Once confirmed, Queues that have been locked to a Game mode can be recognised by the padlock in the embed.

*** ## :crown: AFK Queue timer ``` /queue timeout [hours] ``` If you notice players staying in the queue for long periods without accepting because they’re AFK, you can set up a inactivity timer. This timer will automatically remove all players from the queue after a specified number of hours, using the join time of the **most recent** player as the reference point.

InHouseQueue will send a fresh queue once the inactivity timer has been reached. *** ## :crown: Limit Duo's with MMR or Games played ``` /queue duo_restrictions [queue_channel] (mmr_value) (games_played) /queue duo_restrictions_remove [queue_channel] [restrictions] ``` If you have enabled [Duo queue](#crown-toggle-duo-queue), you can set an MMR or Games played limit to control who is allowed to duo. For example, if a player has more than 2500 MMR, they will no longer be able to duo queue with anyone. Or, if you set the **Games Played** to 5, all players with more than 5 Games in the selected queue will no longer be able to duo. This helps create more balanced games by preventing high-ranking players from pairing up together. You can remove previously set restrictions with `/queue duo_restrictions_remove`

## :crown: Create a queue with its own Leaderboard ``` /queue set_unique_leaderboard [queue_channel] [game] ``` Select a Queue channel and create a new leaderboard for it. #### How it works: 1. Use `/setup` and select `Create new queue` Detailed instructions [here](https://docs.inhousequeue.xyz/docs/quick-start/create-more-queues).

2. Now that we have another queue channel, run `/queue set_unique_leaderboard` and select the new queue channel you just created.

2. InHouseQueue will create a new Leaderboard channel, and mark your queue as **Unique.** Games played in this queue will be tracked separately.

You can recognise unique leaderboard queues by the footer message.

{% hint style="info" %} We suggest you rename this queue, so it's easy to identify! {% endhint %} {% hint style="danger" %} If the unique queue is deleted, you will lose the stats for the queue! So do not delete it unless you are sure! We will soon have a command that will allow you to transfer queue stats. {% endhint %} This queue is now entirely independent in terms of MMR, wins, and losses. This is useful for separating casual queues from competitive queues. Certain commands, such as `/leaderboard` and `/rank` have an optional parameter for selecting the queue channel. Once selected, you'll see the leaderboard or rank for the selected queue. Selecting a Text channel that is **not** a valid queue will default to the [Global Leaderboard](https://docs.inhousequeue.xyz/docs/quick-start/leaderboards-explained#-leaderboards-explained) {% hint style="info" %} As of writing our Website leaderboard [https://inhousequeue.xyz/leaderboard/](https://inhousequeue.xyz/leaderboard/1112808150966485126)\ has not been updated to allow the selection of different queues. So, if you create a unique leaderboard and games are played in both queues, some members may appear multiple times on the website leaderboard. {% endhint %} ## :crown: Suspend a player from queue ``` /queue suspend [user] (duration) (reason) ``` This command suspends/bans a player from entering a queue. If you provide a **duration** they will automatically be unsuspended after the set duration. Allowing them to play again. If you do not provide a **duration** their suspension will be indefinite (forever), until you manually unsuspend them. {% hint style="info" %} This command does **NOT** ban a player from the whole Discord server. It **only** stops them from entering **any** queue in the server. {% endhint %} ### How it works {% hint style="info" %} Give your moderators permissions to suspend players by using `/grant queue_commands` and selecting `Ban players` {% endhint %} 1. Run the `/queue suspend` command. Enter your duration and reason, reason is optional. The duration fields recognises `d` `h` `m` and `s`. For example, to suspend a player for 1 day, you would enter `1d` into duration field. To suspend a player for 1 day and 5 hours, you would enter `1d 5h`. This gives you complete control over how long to suspend a player.

2. Once you've decided on your suspension duration, you'll get a confirmation. For transparency, the player being suspended also receives a DM from InHouseQueue. This action is also logged in your [Admin log channel](https://github.com/InHouseQueue/In-HouseQueue/blob/public-docs/public-docs/commands/server-commands/README.md#crown-server-logs).

3. When the player attempts to queue while their suspension is active, they are blocked and receive a message like this. The message includes the Reason and Duration.

4. Once a suspension has been lifted, it's logged in your [Admin log channel](https://github.com/InHouseQueue/In-HouseQueue/blob/public-docs/public-docs/commands/server-commands/README.md#crown-server-logs)

## :crown: Unsuspend a player from queue ``` /queue unsuspend [user] (reason) ``` If you want to unsuspend a player earlier, use this command.

## :crown: Suspensions Menu ``` /queue suspensions ``` This command gives you an overview of Suspended players, their suspension durations and the Moderator who gave them the suspension. This should help you manage your server effectively.

*** ## :crown: **Set a Discord Role for InHouses** ``` /queue role [role] [game] (queue_channel) ``` Assign a specific Discord role for participation in InHouse games. All members must have this role before they can join the queue. If you no longer want to set this please run `/defaults queue_role` and select `False`. You may also select a specific `queue channel`. If a `queue_channel` is not selected this restriction will be applied to **ALL** queues.

Players without the dedicated role you set, cannot play.

## :bulb: **Sign up with your IGN** ``` /ign [game] [ign] ``` Allows players to enter their In-Game Name (IGN). A player's IGN should ideally match their player name within the game they are playing. InHouseQueue uses the IGN in various places to streamline player interactions. ### Key Features 1. **Player Stats**: Players can view their IGN when using the [`/rank view`](https://docs.inhousequeue.xyz/docs/leaderboard-commands#bulb-view-a-players-stats) command.

2. **Game Lobbies**: IGNs are displayed in the lobby for [Preset games](https://docs.inhousequeue.xyz/docs/preset-games) when a game starts, making it easier for players to invite each other. ### IGN Validation To ensure accurate IGNs, InHouseQueue validates entries for certain [Preset games](https://docs.inhousequeue.xyz/docs/preset-games). Validation rules are as follows: 1. **League of Legends & Valorant**: IGNs must include a `#`, following Riot Games' new format. 2. **Crossfire & Dota**: IGNs must be numeric, as these games use numerical values like SteamIDs to identify players. This ensures smooth gameplay and eliminates errors caused by incorrect or invalid IGNs. *** ## :crown: **Force IGN sign up** ``` /require_ign [condition] ``` Require that players use `/ign [name] [game]` before they can join the queue. This is especially useful for all the [Preset Games](https://docs.inhousequeue.xyz/docs/preset-games) so that the player profile links are accurate. *** ## :crown: **Assign Discord role for specific queue positions** ``` /restrict_role [discord_role] [queue_role] /unrestrict_role [queue_role] ``` If your server focuses more on competitive play, you might want players to queue only for specific positions. This helps ensure higher game quality, as players stick to roles they are skilled in. We leave it up to your creativity to decide how players assign themselves Discord roles that represent the positions they play. However, we recommend not allowing players to select **ALL** positions, as this defeats the purpose of Role restriction. Once players have their assigned Discord roles, you can **Restrict** certain role buttons in the queue to **only** allow players with the corresponding **named** Discord role to join. For example:

Remove this at any time with `/unrestrict_role [queue_role]` *** ## :crown: Edit Queue Labels ``` /queue edit_labels [queue_channel] [labels] ``` For **Custom** games only, you may edit the labels (roles) for a specific queue channel at any time using this command. This is great for servers who want a 3v3 queue and another 1v1 queue (as an example). 1. **Role Labels:** * Each role must have a **unique name**. * Do **not** use the same name more than once. * Each label must be 20 characters or fewer. ### How it works (Option 1) 1. Make sure you select a valid Queue channel that is for **Custom** and Enter your new labels separated by commas.

2. You will be able to confirm the labels you've entered.

3. Your labels for only this queue have changed

### Option 2 1. Rerun the setup command

2. Select 'Custom'

3. Select "Create new Labels". You will be greeted with the Modal to enter your new labels.

4. A new channel will be created with your new labels entered from step 3.