Next steps
After you have run the 5 minute matchmaker reference implementation to test connections, you can now start to connect your game itself to the matchmaker.
Initial setup
Depending on the Architecture you are using, there is two ways to connect your backend/players to the matchmaker.
The following explain step-by-step how to get setup:
If you are planning to use 3rd-party Game-Backend-as-a-Service solutions (e.g. Pragma, Accelbyte), see Game backends for more information on how to set them up and reference code.
Customize your matchmaker
By default the matchmaker has the following configuration:
Configuration | Default setting |
---|---|
Game mode | 1v1 |
Target-waiting-time | 1 sec. |
There is a number of things to adjust depending on the needs of your game.
Adjust the 'target waiting time'
By default the value is set to 1 sec. This facilitate connection testing. When moving towards a real-world application, we recommend setting the value to 20 sec. (For details see Target-waiting-time).
Customize your matchmaker
By default the matchmaker is set to the game mode 1v1, with no further matching constraints. If you have further requirements for the matchmaker to consider, adjust its configuration:
To make changes to the configuration, please see customize matchmaker
Set up rating and ranking
If your game requires rating and ranking, set this up (see Configure rating).
Get production-ready
Before you go into production, there is a couple of things we recommend taking care of.
Move to WebSocket
The REST api is only recommended for initial testing. For proper integration, we recommend switching to WebSocket (see REST vs. WebSocket)
Realistic testing
To get a feel for the behavior of matchmaking, you need to create a test where you constantly enqueue players with different skill levels. This is necessary in order for the matchmaker to learn the distribution of skill and the stochasticity/patterns of players enqueueing (see Notes on testing).