Docs

Beginner guide

Custom player database

Upload a JSON file with your own player names and ratings. Optional — only if you have the right to use that data. The default game world stays fictional.

Need schema, scopes, or every optional field? Advanced guide

What to do

New club career

Onboarding → Player database → Custom file, then pick your club. clubKey shows on the selected card.

World pack or team file with clubKey + players

Add one player

Squad → Add to squad → Import player file

Single player JSON — no clubKey needed

National team

Squad → Import national pool (not Settings)

One player adds; many replaces the pool

Refresh mid-season

Settings → Import squad database. Pick Names, Ratings, or Full. clubKey shown at top.

Team or pack file — club careers only

How it works

Your file overlays names and ratings onto the squad the game already generated. It does not replace the whole world or create new clubs.

Whole game loads your DB

Only matched players on matched clubs update

New clubs from your file

Club must already exist in the save

Club career import

Onboarding, Settings, or Squad (one player)

National career import

Squad → Import national pool only

Import did nothing? Wrong clubKey skips the whole club. Wrong shirt number fails matching (number first, then name). Fix the key in onboarding or Settings, align numbers, or use Squad → Import player file to add someone new.

Files & clubKey

textReference
One player     →  name, number, position, age, nationality
One team       →  clubKey + players[]
One league     →  full pack, league scope (advanced)
Many countries →  full pack, world scope (advanced)

Shorthand files work — the app normalizes bare players and team objects automatically. League and world packs → Advanced guide.

clubKey format

{country}-t{tier}-{slot} — e.g. eng-t1-01, usa-t1-03. Shown on the onboarding club card or at the top of Settings → Import squad database.

One player

jsonplayer.json
{  "number": 10,  "name": "Jordan Pike",  "position": "ST",  "age": 24,  "nationality": "United States",  "ovr": 81}

Positions: GK, CB, LB, RB, CDM, CM, AM, LW, RW, ST

One team

jsonclub.json
{  "clubKey": "eng-t1-01",  "players": [    { "number": 1, "name": "Sam North", "position": "GK", "age": 27, "nationality": "England", "ovr": 80 },    { "number": 10, "name": "Elliot Crane", "position": "AM", "age": 23, "nationality": "England", "ovr": 84 }  ]}

Import depth

Settings → Import squad database only. New careers always use Full.

Names

Name, nationality, age, squad number

Ratings

+ position, OVR, potential, attributes, traits

Full

+ season stats, career totals

Troubleshooting

Import OK, few changes

Check clubKey and shirt numbers

League scope does not match…

Use a world pack, or match country + tier

This team file targets …

File clubKey ≠ your club

Used Settings on national career

Squad → Import national pool

Need full schema

Advanced guide

CHRONAFC · Manager edition

Related