> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidscout/strategy-guide/mock-alliance-selection.md).

# Mock Alliance Selection

**Alliance Selection › Mock Alliance Selection** is a practice alliance selection, always played as 4469. Strategists and drive coaches open it. It needs the team list first; the odds follow its order.

## Set it up

* **Seeding:** until quals are done, choose the seed we'd have, and how the others are seeded (**Others seeded by**: event rank, Match13 xP or our scouting). After quals, the **Event ranking** decides.
* **Others pick by:** Match13 xP, our scouting, our team list, or a Pick Priorities profile's score.
* Championship divisions get 3 picks per alliance (set in **Manage › Events**).

## Play it

{% tabs %}
{% tab title="Phone" %}
![Mock Alliance Selection with Save scenario, Others pick by, the eight alliances and Auto-pick to our turn, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-b6fc4d8e8e4d6d908649c2b512b560e7a80def29%2Fmock-alliance-selection-phone.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![Mock Alliance Selection with Save scenario, Others pick by, the eight alliances and Auto-pick to our turn, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-5a729472300bf98c8c0b4410a6bda2019a4da3c2%2Fmock-alliance-selection.jpg?alt=media)
{% endtab %}
{% endtabs %}

The **Alliances** sit on one short line each. The teams to pick are a table (**Team**, **Ours**, xP, **Team list** place, **Captain**, **Pick**), sorted by its headings, our list first by default.

* Play each alliance's pick yourself, or **Auto-pick to our turn**.
* **Who's likely left at our picks** shows the chance each team on the Team list is still there at each of our picks. It assumes we'd decline an invite.
* When we're a captain, a higher seed may invite 4469 in round 1. Picking us, or auto-pick reaching an alliance that would, asks **Accept** (we join it and the alliances below move up) or **Decline** (we stay captain).

## Scenarios

**Save scenario** keeps the setup and picks for every strategist. **New scenario**, **Save as new**, **Rename** and **Delete** are under **Saved scenarios** and the ⋯ menu.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.raidrobotics.org/raidscout/strategy-guide/mock-alliance-selection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
