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

# Easy Matchmaking

Rocket Networking comes equipped with a very easy to use matchmaking system.&#x20;

{% hint style="info" %}
Credit for this idea goes to @nils0445 on discord!
{% endhint %}

What is a match? In terms of Rocket Networking, it is an RNet room right? Because players/clients in that RNet room will be able to "see" each other.

So matchmaking is just the problem of taking players/clients from some lobby (which is also a RNet room), pair them up or make a set of them and put them in this "match" RNet room. And every "match" must be a different RNet room.

## Auto Matchmaking System

If a client wants to be in the matchmaking lobby waiting, all they have to do is `ChangeRoom()` to the room name `"auto_matchmake_<size>"` , where size is the number of players that should be in your match. \
For example `ChangeRoom("auto_matchmake_2")`

Every 10 seconds, all the players in the room "auto\_matchmake\_2" will be paired up and put into some other rooms called `"auto_match_<someuniqueidentifier>"` like `"auto_match_Lb5vJ8"` and so on.

So if there are 7 players waiting in room `"auto_matchmake_2"` , then 3 pairs will be created and put into 3 different rooms like `"auto_match_7BjvM7"`,  `"auto_match_vmdk8"`, `"auto_match_osm4m"`, and 1 player will not be matched(because there is no one to match this player with) and will stay in waiting.

You can do this for a match of any size.


---

# 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://rocket-networking.gitbook.io/docs/basics-of-rocket-networking/easy-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.
