# Advanced Settings

Once you've finished the initial setup, there are some settings we recommend to help you organize and improve your InHouses effectively.

***

## Force IGN

If you're playing one of the [preset game modes](https://docs.inhousequeue.xyz/docs/preset-games), we <mark style="color:green;">highly recommend</mark> enabling this feature. Once enabled, Players won’t be able to queue until they set their IGN using [`/ign`](https://docs.inhousequeue.xyz/docs/commands/queue-commands#bulb-sign-up-with-your-ign). To turn this on, run `/require_ign`.

<mark style="color:red;">InHouseQueue</mark> integrates with the following player profile websites:

* **League of Legends:** [OP.GG](https://www.op.gg)
* **Valorant:** [OP.GG](https://www.op.gg)
* **Dota 2:** [Dotabuff](https://www.dotabuff.com)
* **Crossfire:** [Crossfire](https://crossfire.z8games.com)
* **Pokemon Unite:** [Unite API](https://uniteapi.dev)

Players can enter their in-game name (or Steam ID) into the [`/ign`](https://docs.inhousequeue.xyz/docs/commands/queue-commands#bulb-sign-up-with-your-ign) command. This will generate profile links for all players at the start of each game, allowing for scouting and strategizing before gameplay begins.

This feature is perfect for servers with a competitive focus, as it helps players plan and adapt their strategies effectively.

### Full details here:

[Force IGN](https://docs.inhousequeue.xyz/docs/commands/queue-commands#crown-force-ign-sign-up)

***

## Scheduling Queues

Having a set time for games makes queues more predictable. When players know games start at a specific time, like 6 PM, they can plan to be available.

If queue scheduling is enabled, players can only join queues during the times you set.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FBFOQtmbHpf8kaDh7oZcE%2Fschedule.png?alt=media&#x26;token=8c1a5b74-5a82-4b54-a22f-91c814e0f865" alt=""><figcaption><p>Schedule Dashboard</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%2FO7waYsc7UmeBRKUaNsGg%2Fschedule_start_time.png?alt=media&#x26;token=ff172ddf-1889-47c4-87e3-a0905e9fd2de" alt=""><figcaption><p>Players cannot join the queue during the closed time</p></figcaption></figure></div>

### Full details here:

[Scheduling Queues](https://docs.inhousequeue.xyz/docs/commands/queue-commands#crown-set-a-schedule)

***

## Restrict Roles

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 <mark style="color:green;">**Restrict**</mark> certain role buttons in the queue to <mark style="color:green;">**only**</mark> allow players with the corresponding <mark style="color:green;">**named**</mark> Discord role to join. For example:

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FIR5TL9CrSQ2Amx5jcaaa%2Frestrict_example.png?alt=media&#x26;token=61d27b91-5ff8-4f1a-b153-bf2758c38065" 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%2Fgit-blob-6e870108e77137d8cb6de71190aedbfc094f52ba%2Frestrict_role_2.png?alt=media" alt=""><figcaption></figcaption></figure></div>

### Full details here:

[Restrict Roles](https://docs.inhousequeue.xyz/docs/commands/queue-commands#crown-assign-discord-role-for-specific-queue-positions)

***

## Custom Lobby Information

You can use a command to provide important information for each game when it starts. This is great for giving instructions or reminding players of rules. For example, you might want to ban certain characters due to a bug or remind players that one person should create the game in the dedicated client and invite everyone.

You can add this information with `/lobby add_info` and remove it later with `/lobby remove_info`. From our experience we think this is a great feature to have enabled in the early days of using <mark style="color:red;">InHouseQueue</mark>. You may find that members will still need some guidance, this is a great way to provide that.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2Fgit-blob-67e9d3e292ca467d440d9698fb9ddd6ff50e48ad%2Flobby_info_new.png?alt=media" 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%2Fv6pQsOUsO9CI8JchmObf%2Flobby_info_preview.png?alt=media&#x26;token=ccf1baaf-8b1d-4321-8aef-cfe821869e13" alt=""><figcaption></figcaption></figure></div>

### Full details

[Custom Lobby Information](https://docs.inhousequeue.xyz/docs/commands/game-commands#crown-customised-lobby-information-)

## Show Player MMR

If you want to be transparent about players' current MMR ratings, you can enable it with `/mmr show`.

When enabled, the MMR of each player will be visible as soon as they join the queue.

{% hint style="info" %}
MMR is meant to be a general guide to a player's skill level, not a tool for criticism. In competitive environments, some players may "dodge" queues by not accepting if they see a player with low MMR. This can create issues, but we provide solutions to handle such behavior.
{% endhint %}

For more details on how to punish toxic players, see the next feature [**Suspend Players from Queue**](#suspend-players-from-queue).

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2FfVadJCHO70nIwuy1DHAd%2Fmmr_display.png?alt=media&#x26;token=5a80e4e4-b7ac-4f21-b8a4-9b078daa3482" alt=""><figcaption></figcaption></figure></div>

### Full details here:

[Show Player MMR](https://docs.inhousequeue.xyz/docs/commands/mmr-commands#crown-show-player-mmrs)

***

## Suspend players from queue

If a player is being disruptive, sometimes a short cooldown is all they need. You can suspend a player from queuing by running `/queue suspend`.

<div align="left"><figure><img src="https://1130318129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwcHfLjgS9hMDSoOpDEDo%2Fuploads%2Fgit-blob-eeb8bd3df8f96f2a3a22915e880763d8c637ea28%2Fbans_3.png?alt=media" alt=""><figcaption><p>Confirmation for the Moderator</p></figcaption></figure></div>

### Full details here:

[Suspend players from queue](https://docs.inhousequeue.xyz/docs/commands/queue-commands#crown-suspend-a-player-from-queue)

***

## Voice Lobby/Waiting Rooms

<mark style="color:red;">InHouseQueue</mark> can automatically move players to their designated voice channels once a game starts. However, please note that Discord bots cannot move members who are not already in a voice channel.

This feature allows you to dedicate specific voice channels in your server as "Lobby" or "Waiting Room". Players waiting in these channels will automatically be moved to their team voice channels when a game begins.

To enable this feature, use the `/voice set` command. If you want to disable it later, use `/voice unset`. You can set up multiple Waiting Rooms by running `/voice set` again as required.

### Full details here:

[Voice Lobby/Waiting Rooms](https://docs.inhousequeue.xyz/docs/commands/voice-commands#-voice-commands)

***

## Default Settings

<mark style="color:red;">InHouseQueue</mark> offers many customizable settings that can be turned on or off, such as creating voice channels or muting spectators. You can see the available settings by using the `/defaults` command or visiting [this page](https://docs.inhousequeue.xyz/docs/commands/server-commands#crown-turn-features-on-and-off) for the full list.

### Full details here:

[Default Settings](https://docs.inhousequeue.xyz/docs/commands/server-commands#crown-turn-features-on-and-off)


---

# 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.inhousequeue.xyz/docs/quick-start/advanced-settings.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.
