Database editor guide

The editor changes the shipped database — the one every new career is built from. Correct a bowling style, fix a date of birth, rename a player, retire someone who has stopped playing in real life. It is on the main menu rather than inside a career, because that is what it edits.

Your changes are never written into the game's own data. They go into a small text file alongside it, which is what makes them survive updates — and what makes them shareable.

1. 1Open Database Editor from the main menu.
2. 2Pick a country from the dropdown on the left, or type into Search name…. Retired players are included — you need to find a man to un-retire him.
3. 3Click a player. His details open on the right.
4. 4Change whatever you like, then click Save. Do that for as many players as you want.
5. 5Go back to the main menu. The database rebuilds itself as you leave, which takes a second or two. Nothing is applied until you do this.
6. 6Start a new career to play with your changes.

To undo a change, open the player again and click Revert player, which drops every change you have made to him and puts him back to how the game shipped. Batting position is the one field you can revert on its own, by clearing the box. Everything else is all-or-nothing per player.

A player retires from formats one at a time, and there are six of them: Test, ODI and T20I for internationals, and first-class, List A and T20 for the domestic game that contains them. Retiring from Tests at 34 and playing on in first-class cricket is ordinary, so the six tick boxes are separate.

The reverse is not possible, and the game enforces it rather than trusting the boxes: a man who has retired from first-class cricket cannot be playing Tests. Retire him from first-class and Test is ticked for you and locked, naming first-class as the reason. The same goes for List A over ODI, and domestic T20 over T20I.

• Skills and ratings. Batting, bowling and the physical attributes are not editable yet — that is a later pass, and the file format is built so adding them will not break patches already being shared.
• Players created inside a career. Youngsters who come through as your career runs exist only in that save, so there is no shipped database row to edit.
• Teams, venues and fixtures. The editor covers players.

Everything the editor writes goes into a patches folder, as 99-my-edits.tsv. That one file holds all your changes, one line per changed field.

macOS

~/Library/Application Support/com.lslventures.cricketteammanager/patches/

Windows

%APPDATA%\com.lslventures.cricketteammanager\patches\

Your careers are kept separately, one file each:

macOS

~/Library/Application Support/com.lslventures.cricketteammanager/saves/

Windows

%APPDATA%\com.lslventures.cricketteammanager\saves\

On Windows you can paste %APPDATA% straight into the Explorer address bar. On a Mac, use Go → Go to Folder in Finder and paste the path — the Library folder is hidden by default.

Send someone 99-my-edits.tsv. That is the whole of it — there is nothing to export and no format to convert. If you have built something worth having, post it on r/CricketTeamManager (opens in a new tab), which is where players swap them.

Rename it to something that says what it is before you hand it over — 20-real-names.tsv, 30-bowling-styles.tsv — and keep the number at the front. That number is the install order, and leaving it as 99-my-edits.tsv means the next person's own edits and yours are the same file.

1. 1Put their .tsv file in the patches folder above, beside your own.
2. 2Quit the game and open it again. Files are read at startup.
3. 3Start a new career.

Files are applied in filename order, and the last one to set a field wins. Because the editor always writes 99-my-edits.tsv and 99 sorts last, your own changes sit on top of everyone else's — so installing a file can never quietly overwrite something you typed yourself. Number the files you install below that to choose the order between them.

Because each line changes one field, files stack rather than fight. A names file and a bowling-styles file both apply in full even where they touch the same player, and neither has to know the other exists. To uninstall one, delete it while the game is running, then quit and open the game again — that reverts it. Delete it with the game closed and Steam Cloud puts it back the next time you launch.

You only need this to build a big patch by hand or to check one someone sent you. It is a plain text file, three columns, separated by tabs — not spaces, and not commas.

stable_key	field	value	player
# lines starting with a hash are ignored, and so are blank ones
yurkymhq9v	first_name	Terry	Terry Armstrong
yurkymhq9v	last_name	Armstrong	Terry Armstrong
yurkymhq9v	bowling_style	SLA	Terry Armstrong
yurkymhq9v	batting_position.TEST	7	Terry Armstrong
yurkymhq9v	retired.T20I	1	Terry Armstrong

The first column is the player's key, which the editor shows in the top-right corner of his details. It is how a file identifies a player, so the same file works for everyone regardless of version. The fourth column is a comment — the game ignores it, and it exists so the file can be read by a human. The header line is optional, and blank lines and lines starting with # are skipped.

These are the fields, spelled exactly as the game expects them:

Nothing in one of these files can run code or touch anything but the fields above — every value is checked before it goes anywhere near the database, which is what makes it safe to install a file from a stranger.

• Nothing changed after you edited a player — you are probably looking at a career that was already under way. Start a new career and check there.
• Nothing changed after you installed someone else's file — quit the game completely and open it again. On a Mac, closing the window is not quitting.
• One file seems to be ignored — if any line in it is malformed the whole file is skipped, and every other file still applies. Check the file in a text editor: three columns, separated by real tabs, and a field name spelled exactly as in the table above.
• A player in the file is missing from your game — that is normal if the file was made against a newer version. Those rows are counted and skipped, and the rest of the file still applies.

Still stuck? Email support@cricketteammanager.com with the file attached, or ask on r/CricketTeamManager (opens in a new tab).