MatchZy Setup: admins.json, Database, Demos and Key Convars
Once MatchZy is running, three things decide how useful it is: who can run admin commands, where match stats go, and what happens to the demos. All three live in files under cfg/MatchZy.
The details below are from MatchZy's configuration page, checked November 21, 2026. It's third-party software, so confirm anything critical against your own copy. The folder sits at game/csgo/cfg/MatchZy/ on a ChicagoServers server, which you can open on the Files tab. For installation, see the install guide.
On this page
Admins: admins.json
The file maps a SteamID64 to a flag string. Flags are separated by spaces or commas, and @css/root grants everything. MatchZy creates the file if it's missing.
{
"76561190000000001": "@css/root"
}- An empty flag value grants every MatchZy admin command, including
!rcon. - A mistyped flag counts as no flags, and a warning is logged.
- CounterStrikeSharp's own admin file at
addons/counterstrikesharp/configs/admins.jsonworks too, using anidentityplus aflagsarray per admin. .reload_adminsreloads the file without a restart.
Whitelist
whitelist.cfg holds one SteamID64 per line. Whitelisting is off by default, and the .whitelist command toggles it.
Stats database: database.json
MatchZy uses SQLite by default and sets it up for you. MySQL is optional, and it's useful if several servers share one set of stats. To switch, edit database.json. These are the fields:
{
"DatabaseType": "MySQL",
"MySqlHost": "127.0.0.1",
"MySqlDatabase": "matchzy",
"MySqlUsername": "matchzy_user",
"MySqlPassword": "change-me",
"MySqlPort": 3306
}A MySQL database can be created on the Databases tab when your plan includes one. Use the host and details the panel shows. Don't copy the example values.
The stats go into two tables, matchzy_stats_matches (match ID, team names, scores) and matchzy_stats_players (kills, deaths, assists and more). After a match, MatchZy also writes a CSV to csgo/MatchZy_Stats, one file per map, named match_data_map{mapNumber}_{matchId}.csv. It holds the same data as the players table. The docs note the match score isn't in it yet.
Demos
| Setting | Default | Notes |
|---|---|---|
matchzy_demo_path | MatchZy/ | No leading slash, must end with a slash. An empty value uses the csgo root. |
matchzy_demo_name_format | {TIME}_{MATCH_ID}_{MAP}_{TEAM1}_vs_{TEAM2} | Supports {TIME}, {MATCH_ID}, {MAP}, {MAPNUMBER}, {TEAM1}, {TEAM2}. Leave off .dem and keep {TIME} so names stay unique. |
matchzy_demo_upload_url | empty | If set, each demo uploads when the map ends. Put the URL in double quotes. |
The README says recording needs tv_enable 1. The configuration page doesn't name a separate convar that turns demo recording on, so we haven't listed one.
The convars you'll touch most
| Convar | Default | What it does |
|---|---|---|
matchzy_knife_enabled_default | true | Knife round on by default. Toggle in match with .roundknife. |
matchzy_minimum_ready_required | 2 | Ready players needed to start. |
matchzy_ready_mode | 0 | 0 means players type .ready. 1 counts joining as ready. |
matchzy_time_to_start | 0 | Time limit to start a match. 0 means no limit. |
matchzy_max_tech_pauses | 0 | Technical pauses allowed. 0 means unlimited. |
matchzy_tech_pause_time | 0 | Length of a technical pause. |
matchzy_kick_when_no_match_loaded | false | Kicks players when no match is loaded. |
matchzy_stop_command_available | false | Whether players can use the stop command. |
matchzy_autostart_mode | 1 | 1 means match mode on start. |
matchzy_hostname_format | MatchZy | {TEAM1} vs {TEAM2} | Server name during a match. |
matchzy_chat_prefix | [{Green}MatchZy{Default}] | Prefix on plugin messages. The docs say it should end with {Default}. |
There are many more, including remote logging and remote backup options. The page doesn't list all the console commands and defaults, so use the project's documentation for the rest. To reload after a change, the docs give exec MatchZy/config.cfg; execifexists MatchZy/config_override.cfg.
Keep it tidy
- Back up
cfg/MatchZybefore updating. The.cfgfiles in it are replaced by updates. - Put your edits in
config_override.cfgif you can, since the reload command above runs it after the main config. - Don't paste database passwords into Discord or a support ticket.
Frequently asked questions
How do I make someone a MatchZy admin?
Add their SteamID64 and a flag string to <code>cfg/MatchZy/admins.json</code>. <code>@css/root</code> grants everything, and an empty value also grants all MatchZy admin commands.
Does MatchZy use MySQL or SQLite?
SQLite by default, configured automatically. Edit <code>database.json</code> to use MySQL instead.
Where do MatchZy demos go?
To <code>matchzy_demo_path</code>, which defaults to <code>MatchZy/</code>. You can also set <code>matchzy_demo_upload_url</code> to upload each demo when the map ends.
Where are MatchZy stats saved?
In the SQLite or MySQL database, plus a CSV per map in <code>csgo/MatchZy_Stats</code>.
What does matchzy_everyone_is_admin do?
It makes every player an admin, including access to rcon. It defaults to false, and you should leave it there.