Support

Email support@cricketteammanager.com. It is read by the person who wrote the game, so be as technical as you like.

A reply usually takes a day or two. For anything that is not really a bug — how other people are playing it, sharing database edits, arguing about selection — there is r/CricketTeamManager (opens in a new tab). If you bought on Steam the community hub works too, but email is faster for a fault.

Four things turn a report into a fix:

• What you were doing, in enough detail to try it again.
• What you expected, and what happened instead.
• Your operating system and the game version (shown on the main menu).
• The save file, if it is one particular career — the single most useful thing you can send.

Each career is a single .sqlite file. Copy it to back it up; copy it back to restore it.

macOS

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

Windows

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

There is a database editor on the main menu, and your edits are saved as a small text file you can share with anyone. How to use it, where the file lives and how to install someone else's edits are all in the database editor guide.

Generous — there is no 3D renderer to feed. Anything from the last decade will run it.

Windows

Windows 10 (version 1803) or later, 64-bit

macOS

macOS 11 Big Sur or later, Apple silicon or Intel

Memory

4 GB RAM

Storage

Around 200 MB

Bought on Steam, refunded on Steam — under two hours played and within fourteen days, through the normal Steam process. Outside that window, email and ask; a game that does not work for you is not a sale worth keeping.