Build a basic matchmaker configuration
edgegap_build_matchmaker_configBuilds a ready-to-upload Edgegap matchmaker JSON config with team rules, latency limits, and wait-time expansions; verify the app version and save the file for manual dashboard upload.
Instructions
Generate a ready-to-upload Edgegap matchmaker JSON configuration with one profile: team count and size, optional latency rule, and optional expansions that relax the rules the longer a player waits. Checks the referenced application version exists and has ports. Edgegap has no API for creating a matchmaker, so this tool does NOT create one: save the returned config to a file (e.g. matchmaker-config.json) and have the developer upload it on the Matchmaker page of the dashboard. The matchmaker starts an authoritative dedicated server for each match, which is the recommended setup for multiplayer games.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"profile_name": "<profile_name>",
"application": "<application>",
"version": "<version>",
"team_count": "<team_count>",
"min_team_size": "<min_team_size>",
"max_team_size": "<max_team_size>"
},
"name": "edgegap_build_matchmaker_config"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| inspect | No | Expose the inspection API for debugging. Default true; turn off for production. | |
| version | Yes | Version the matchmaker deploys. | |
| expansions | No | Rule relaxations after a player has waited this long, e.g. [{after_seconds: 20, min_team_size: 1}]. Keep each below ticket_expiration. Not needed for partial matches: min_team_size below max_team_size already allows them. Expansions cost the matchmaker performance, so add one only to relax a rule. | |
| team_count | Yes | Teams per match. 1 for free-for-all or co-op. | |
| application | Yes | Application the matchmaker deploys. | |
| profile_name | Yes | Profile clients will queue into, e.g. "casual-2v2". | |
| max_team_size | Yes | ||
| min_team_size | Yes | ||
| max_latency_ms | No | Adds a latency rule: drop players above this ping to the chosen region. Needs beacon pings from the client. | |
| verify_version | No | Look up the application version first. Default true. | |
| ticket_expiration | No | Default "30s", so a developer testing alone is matched or told to retry within 30 s instead of waiting minutes. Raise it only for production queues. | |
| allowed_cors_origins | No | Origins of web pages allowed to call the matchmaker, e.g. ["https://mygame.example.com", "http://localhost:8080"]. Required when game clients run in a browser (WebGL): browsers block matchmaker calls from any origin not listed. Scheme and host only, no path. | |
| latency_difference_ms | No | Max ping spread between matched players. Default 100. |