Next steps

After you have completed the connection and run the reference implementation, you can start customising and operationalising your matchmaker.

By default the matchmaker has the following configuration:

Default settings

Configuration	Default setting
Game mode	1v1
Target-waiting-time	1 sec.
Rating	Baysian

We recommend adjusting the following items as the next steps:

🔳 Move the code to your game
Take the code from the reference implementation and move it into the server orchestrating your game. If you don't want to build your own backend or don't want to have a backend in the first place, have a look at your options in our architecture section.

🔳 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).

🔳 Move to Websockets
The REST api is only recommended for initial testing. For proper integration, we recommend switching to Websockets (see REST vs. Websocket)

🔳 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).

🔳 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).

🔳 Setting up for production
Before you start going into production with your game, make sure that a payment method is stored. Otherwise the matchmaker will deny your requests, as soon as the free limit is reached (see Billing)