> For the complete documentation index, see [llms.txt](https://docs.inhousequeue.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inhousequeue.xyz/docs/commands/user-commands.md).

# User commands

#### :crown: **Admin only commands**

#### :bulb: **General command for everyone**

<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:**Update members IGN**

```
/user update_ign [ign] [member] [game]
```

A command for Admins to update a member's in-game name (IGN).

***

## :crown: Manually change a player's Win/loss

```
/user manage score
```

<div align="left"><figure><img src="/files/DHjJwzI8TEjhzhKJd4A4" alt=""><figcaption></figcaption></figure></div>

You can manually add or remove a win or loss from a player.

This command simply adds a win or loss to the player. It does **NOT**:

* **Change MMR**
  * Adjusting the player's MMR to account for the change is not feasible due to <mark style="color:red;">InHouseQueue</mark>'s dynamic MMR system. The system calculates MMR adjustments based on the MMR of all players involved, making it extremely difficult to accurately adjust a player's MMR when this command is run. Manual MMR adjustments can't provide the necessary information for precise calculations.
* **Change historic/lifetime statistics.**
  * <mark style="color:red;">InHouseQueue</mark> tracks every single game played and uses this information to provide historical data. Since this command simply adds or removes a win or loss, it does not count as an **actual** game. Consequently, some commands may return expected results. Commands such as: `/stats` `/match_history` `/all_time_leaderboard`

***Please be aware of these limitations when using this command.***

## :crown: **Remove users from a queue**:

```
/user dequeue [member]
```

Remove specific players from the current queue. Ideal if a player is AFK.

If used during the ready-up phase, the player is still removed and other players are unaffected, the ready-up phase returns to a normal queue.

***

## :bulb: Decay Notifications

If you have [MMR decay](/docs/premium/premium-commands/tier-2.md#mmr-decay-system-) on, players will receive a DM from <mark style="color:red;">InHouseQueue</mark> about their decay status. Players can opt out of receiving direct messages with this command.

```
/decay_notifications [receive_notifications]
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.inhousequeue.xyz/docs/commands/user-commands.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.