matchmaking and automatic region selection
Hello,
Using Godot 4.3 and Rivet Version 2.3.1, I attempted to address the following:
A) Map and Skill-Based Matchmaking
B) Automatic Region Selection
Let me explain what I did. This might help you understand a developer's perspective when upgrading your website and documentation.
Materials I Used:
• EG1: Rivet Godot Version 1.x example
• EG2: Rivet Godot Version 2.3.0 example
• DOC: Rivet module documentation https://opengamebackend.org/modules/lobbies
• MOD: Module page explaining how to get started https://github.com/OpenGameBackend/OpenGameBackend/tree/main/modules/lobbies
A) Map and Skill-Based Matchmaking
In EG2, I found code for await Rivet.lobbies.find_or_create, which takes a JSON parameter. I set tags and createConfig.tags to { "map": "sandstorm", "difficulty": "hard" }, but the server threw an error.
I referred to DOC, but it didn’t clarify the purpose of JSON keys. Then, I checked MOD, where I found two useful pieces of information:
- To enable tags, set taggable to true.
- RIVET.matchmaker.lobbies.find({ gameMode: 'default', tags: { map: "sandstorm", difficulty: "hard" } });
Next, I looked at EG1 and found that rivet.json defines matchmaker.game_modes.default. Based on this, I added the following to the rivet.json of EG2:
"matchmaker": {
"game_modes": {
"default": { "taggable": true }
}
}
After deploying the server (not sure if this was necessary), the client weren't able to connect to server due to server error.
Observations from Documentation:
1) Config https://opengamebackend.org/modules/lobbies/config
• Describes the structure of rivet.json, but it doesn’t include matchmaker or define game_modes.
2) Find API
• find_or_create: https://opengamebackend.org/modules/lobbies/scripts/find_or_create
• find: https://opengamebackend.org/modules/lobbies/scripts/find
• Neither API’s JSON parameter includes gameMode.
Using Godot 4.3 and Rivet Version 2.3.1, I attempted to address the following:
A) Map and Skill-Based Matchmaking
B) Automatic Region Selection
Let me explain what I did. This might help you understand a developer's perspective when upgrading your website and documentation.
Materials I Used:
• EG1: Rivet Godot Version 1.x example
• EG2: Rivet Godot Version 2.3.0 example
• DOC: Rivet module documentation https://opengamebackend.org/modules/lobbies
• MOD: Module page explaining how to get started https://github.com/OpenGameBackend/OpenGameBackend/tree/main/modules/lobbies
A) Map and Skill-Based Matchmaking
In EG2, I found code for await Rivet.lobbies.find_or_create, which takes a JSON parameter. I set tags and createConfig.tags to { "map": "sandstorm", "difficulty": "hard" }, but the server threw an error.
I referred to DOC, but it didn’t clarify the purpose of JSON keys. Then, I checked MOD, where I found two useful pieces of information:
- To enable tags, set taggable to true.
- RIVET.matchmaker.lobbies.find({ gameMode: 'default', tags: { map: "sandstorm", difficulty: "hard" } });
Next, I looked at EG1 and found that rivet.json defines matchmaker.game_modes.default. Based on this, I added the following to the rivet.json of EG2:
"matchmaker": {
"game_modes": {
"default": { "taggable": true }
}
}
After deploying the server (not sure if this was necessary), the client weren't able to connect to server due to server error.
Observations from Documentation:
1) Config https://opengamebackend.org/modules/lobbies/config
• Describes the structure of rivet.json, but it doesn’t include matchmaker or define game_modes.
2) Find API
• find_or_create: https://opengamebackend.org/modules/lobbies/scripts/find_or_create
• find: https://opengamebackend.org/modules/lobbies/scripts/find
• Neither API’s JSON parameter includes gameMode.
Build and scale stateful backends. Rivet Actors is a library for long-lived processes with durable state, realtime, and scalability. Easily self-hostable and works with your infrastructure.
1,419Members
Resources
Was this page helpful?
