> For the complete documentation index, see [llms.txt](https://mbground.gitbook.io/game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mbground.gitbook.io/game/about-game/matchmaking.md).

# 🎮 Matchmaking

To start a game in ranked mode, two players are required. The matchmaking system will search for two players with similar skill levels. Mercenary Battleground creates matches based on fairness, differences in player skills, queue time, and the number of available players. The longer it takes for the system to find the required number of players, the higher the skill level difference between the players will be. The game uses a win/loss rating system rather than a performance-based system (such as income, MVP, etc.). This is done to reward players who play for victory rather than artificially inflate their stats in ways that could potentially harm the game. Rating changes for wins and losses take this into account. If you play against stronger opponents, you will gain more rating for a victory and lose less rating in case of defeat.

After the game is completed, the matchmaking system will award or deduct rating points based on the expected skill gap between the two players (by taking the average rating points for each player).


---

# 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://mbground.gitbook.io/game/about-game/matchmaking.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.