HOW IT'S BUILT
The work behind R7S Legends Database
A legends database should still behave like Football Manager years into a save. That means researching and rebuilding far more than names, ages and ratings.
MORE THAN A RETRO SEASON
Built as a living football world.
R7S Legends Database brings generations of legendary players and managers into one Football Manager universe, but the objective is not simply to make every famous player powerful. The objective is to make each person belong naturally inside the same long-term career.
The work extends through playing history, attributes, positions, preferred foot, personality, traits, contracts, club allocation, home-grown data, finances, youth development, youth-intake environments, managers, staff and the structural details that determine whether a save still makes sense several seasons later.
Many thousands of hours have accumulated across historical research, editing, reconstruction, forensic auditing, testing and repeated correction passes. Community reports then feed back into the same process when a missing player, wrong club, questionable rating or technical defect is found.
PLAYING HISTORY
Career chronology, clubs, seasons, appearances, goals and linked registration data.
IDENTITY FIRST
Native FM identities are preferred; donor creation is a last resort and is audited afterwards.
CLUB WORLD
Contracts, finances, transfer structures and long-term club systems receive dedicated passes.
YOUTH SYSTEMS
Youth development and youth-intake environments are reviewed as part of the wider save.
FORENSIC QA
Duplicate, clone, donor-contamination, wrong-club and staff/player conflicts are actively searched for.
VALIDATION
Structural checks protect the master before a separate fresh-career runtime test.
CURRENT VALIDATED MASTER — v3.5.168
Depth you can measure.
7,202
PEOPLE IN MASTER
664
CLUBS IN MASTER
672,642
TOP-LEVEL DB CHANGES
22,874
STRUCTURED OPS VALIDATED
v3.5.168 is the latest structural-validation checkpoint. Its static validation is complete; fresh-career runtime validation remains a separate release gate before a pre-runtime master should be treated as runtime-approved.
THE PIPELINE
How one correction becomes a safe release.
Historical research
Establish the player, era, club legacy, career path and the version of the player we are trying to recreate.
Native identity search
Use the genuine FM identity wherever possible before considering donor reconstruction.
Donor reconstruction
Only when a suitable native identity is genuinely absent: rebuild the person fully and audit donor contamination.
Attributes & CA/PA
Build technical, mental and physical attributes, then make CA fit the recreated stage of development while PA represents the historical ceiling.
14-position profile
Rebuild the full positional map rather than only the player's headline position.
Feet, personality & traits
Preferred foot, personality data, hidden characteristics and player traits are reviewed so the player behaves like himself.
Playing history
Career clubs, seasons, appearances, goals and chronology are reconstructed instead of treating history as decoration.
Home-grown & eligibility
Club-trained, nation-trained, registration and identity-linked data are checked alongside the player's career history.
Contracts & club systems
Contracts, transfer status, club allocation, finances and other long-term career systems are reviewed so the save remains believable.
Youth environment
Youth development and youth-intake environments are reviewed as part of the club world, not isolated from the legends themselves.
Forensic audits
Duplicate identities, donor leakage, cloned profiles, staff/player conflicts, wrong clubs, loans and structural inconsistencies are hunted down.
Validation & runtime
Static structural validation protects the XML before a separate fresh-career runtime gate confirms how the release behaves in FM26.
NEW AGE-NORMALISATION MODEL
Legends should develop, peak and decline.
The new age process avoids making every historical legend the same age. A player's original birth era sets the recreated starting stage, while naturally younger modern players are not artificially aged upward.
The original historical day and month of birth are preserved wherever possible. PA remains the player's historical ceiling, while CA and the attribute profile are reviewed against the recreated stage of development instead of applying a blind multiplier.
Early bloomers and late developers are treated as exceptions. Signature qualities are preserved so the player remains recognisable, but a young recreated legend should still have room to become his greatest version. Playing history and unrelated identity data are preserved rather than erased by the age conversion.
KEEPING THE PROJECT MOVING
Every download stays free.
Optional support does not unlock content. It helps justify the time required to research another player, rebuild another history, audit another club, test another release and keep the database improving.