MatchZy Match Config: JSON Fields, Veto Settings and Loading a Match
Without a match config, MatchZy is a ready-up and pause tool. With one, it becomes a proper match system: it knows who's on which team, which maps to play and how the veto works. The config is a single JSON file.
This page is based on MatchZy's match setup documentation, checked November 21, 2026. The docs say the optional fields are Get5 compatible. The docs don't give a complete schema, so anything we couldn't confirm is marked. You'll need MatchZy installed first, which is covered in the install guide.
On this page
The fields MatchZy needs
The docs list four required fields: maplist, team1, team2 and num_maps. matchid isn't required. If you leave it empty, the server makes one up.
team1andteam2each have anameand aplayersobject that maps a SteamID64 to a nickname.spectatorshas aplayersobject too.playerscan also be a plain array of SteamID64s.- Only SteamID64 is supported. Other ID formats won't work.
A working example
This one is a best-of-three scrim. The SteamID64s are placeholders, so swap in real ones.
{
"team1": {
"name": "Chicago Reds",
"players": {
"76561190000000001": "Alpha",
"76561190000000002": "Bravo"
}
},
"team2": {
"name": "Lakeview",
"players": {
"76561190000000011": "Delta",
"76561190000000012": "Echo"
}
},
"num_maps": 3,
"maplist": ["de_ancient", "de_inferno", "de_mirage"],
"skip_veto": false,
"veto_first": "team1",
"side_type": "standard"
}The docs' own example also shows map_sides, clinch_series, players_per_team and cvars. The page doesn't explain clinch_series, players_per_team or spectators beyond showing them, so we haven't described what they do.
Veto and side settings
| Field | Default | What the docs say |
|---|---|---|
skip_veto | false | If maplist has more maps than num_maps, a veto happens. Set true and the first num_maps maps are played in order. A maplist with exactly num_maps maps is always played in order. |
veto_first | team1 | Which team starts the default veto: team1, team2 or random. If you give a veto_mode, it's used as written. |
side_type | standard | Applies to maps with no entry in map_sides. Options are standard, always_knife, never_knife and random. |
map_sides | none | Per-map choices. Example values are team1_ct, team2_ct and knife. The page doesn't list every allowed value. |
Loading the match
Put the file in the server's csgo directory, which on ChicagoServers is game/csgo/ on the Files tab. Then, on the Console tab:
matchzy_loadmatch scrim.jsonTo load from a web address instead, use matchzy_loadmatch_url. It sends a plain GET request and expects JSON back. The docs say every argument should go in quotation marks, and you can add an optional header name and header value:
matchzy_loadmatch_url "https://example.com/matches/scrim.json"The docs don't describe what happens when a file is invalid or a URL request fails, or how long it waits. Watch the console after loading, and fix any error before players join.
Limits and gotchas
- Players are locked to their team. The docs say a match file locks players to their correct team and side, using the SteamID64s under each team. They don't explain the mechanism, so test with a spare account before a real match.
- Coaches can't be added directly. Put them under a team's
players, then use.coach <teamside>on the server. - Booleans accept
1and0as well as true and false. - cvars have to be real convars or MatchZy or Get5 settings. Values can't contain a double quote, a semicolon or a line break.
- Ignored and logged: console commands in
cvars, action commands such asmatchzy_loadmatch_urlorget5_endmatch,rcon_passwordandmatchzy_everyone_is_admin. - Demo paths from
matchzy_demo_pathandmatchzy_demo_name_formatmust be relative and can't contain...
Frequently asked questions
Which fields does a MatchZy match config require?
<code>maplist</code>, <code>team1</code>, <code>team2</code> and <code>num_maps</code>. <code>matchid</code> is optional, and the server generates one if you leave it empty.
How do I load a MatchZy match?
Run <code>matchzy_loadmatch <file></code> with a path relative to the csgo directory, or <code>matchzy_loadmatch_url</code> to fetch the JSON from a web address.
What ID format do the players use?
SteamID64 only. Players are listed under each team's <code>players</code> key, either as a SteamID64 to nickname object or an array of SteamID64s.
How does the veto work?
If <code>maplist</code> has more maps than <code>num_maps</code>, a veto happens, started by the team in <code>veto_first</code>. Set <code>skip_veto</code> to true to play the first maps in order.
Is the config compatible with Get5?
The docs describe the optional fields as Get5 compatible, and MatchZy also works with Get5 panel tools.