> 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/features/captain-queue.md). # Captain Queue The Captain Queue feature brings a strategic element to team selection by allowing two captains to take turns choosing their team members. Captains can be assigned based on **Highest MMR**, **Lowest MMR**, **Randomized Selection**, or an **Admin Decision**. This feature supports a variety of pick orders, including snake drafts and alternate turns, to ensure balanced and fair gameplay. Admins can also create a dedicated **Captain Select Channel** where captains are assigned, followed by a **Team Select Channel** where players are picked one by one. Only the captains can interact in these channels, streamlining the process. Once all players are selected, teams are finalized, and the game proceeds. This feature is ideal for competitive servers looking to add a layer of strategy and player interaction to their in-house games. Find out how to set up Captain Queue [here](/docs/commands/captain-commands.md#crown-enable-captain-queue) --- # 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/features/captain-queue.md?ask=&goal= ``` `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.