01 / DIRECT ANSWER
Keep the entity before the new Career deletes it
Use Live Editor v26.2.6 or newer and place `LE_CM_SUPPORTED_LEAGUES_AND_TEAMS.csv` in `mods\legacy\data`. Give the exact team or league ID the current six-column decision, then start a new Career with Live Editor running. Search the active log for the published deletion phrases and verify the exact entity inside the Career. Existing Careers are not a documented reconstruction target.
March schema, exact filename, six numeric cells.
The file controls the creation-time deletion hook.
Deletion log plus exact in-Career presence.
02 / SYMPTOM CLASSIFIER
First prove this is the deletion hook
Target candidate for the hard-coded keep/delete override.
Check database, mod build, asset and active dataPath first.
Check relationships, assets and compdata capacity.
No official resurrection workflow is published.
03 / ACCOUNTABLE OWNER
The allowlist lives in code—not in a database row
WRONG FIX: changing a database row or ordinary legacy data does not alter the hard-coded allowed list. Live Editor changes the deletion decision; it does not create the club, league, players, fixtures or assets.
04 / TEST MANIFEST
Record six identities before changing one decision
05 / ORIGINAL CSV EXPERIMENT
Reject the stale contract before FC 26 sees it
Load a local CSV or use the test corpus. The lab checks filename, current header/order, binary flags, dependency rules, duplicate typed IDs and semantic conflicts—then builds a new-Career evidence receipt.
CAREER ADMISSION LAB
02 / CONTRACT INPUT
CURRENT SIX-COLUMN SCHEMA03 / FINDINGS
Exact filename, current header and conservative row rules pass.
111114KEEP0 · 0 · 0111205KEEP0 · 0 · 01337DELETE1 · 0 · 11318DELETE1 · 0 · 120DELETE1 · 0 · 1Signal count is not retention proof. Verify the exact entity inside the new Career.
VIEW EVIDENCE RECEIPT +
FILE / LE_CM_SUPPORTED_LEAGUES_AND_TEAMS.csv CONTRACT / READY DECISIONS / 5 (2 KEEP · 3 DELETE) ENTITY TYPES / 4 TEAM · 1 LEAGUE FINDINGS / 0 ERROR · 0 WARNING PROTOCOL / 0/6 LOG SIGNALS / 0 TEAM · 0 LEAGUE IN-CAREER ENTITY PROOF / REQUIRED
06 / VALIDATION RESULTS
Seven adversarial files define the safe subset
Five parseable decisions; current header.
Obsolete fifth column identified by name.
Published dependency violated.
Undocumented precedence rejected.
Binary but semantically contradictory.
Creator recommendation exposed as warning.
Discovery contract not met.
GREEN ≠ PLAYABLE: READY means the file matches the documented conservative contract. It cannot prove active mod placement, hook execution or a complete Career ecosystem.
07 / FILE DISCOVERY
One exact filename; two delivery paths
C:\FC 26 Live Editor\mods\legacy\data\LE_CM_SUPPORTED_LEAGUES_AND_TEAMS.csvThe root folder can differ; preserve the internal `mods\legacy\data` chain.
your mod → legacy files → data →LE_CM_SUPPORTED_LEAGUES_AND_TEAMS.csvThe Wiki permits adding it to the mod’s legacy `data` folder.
ACTIVE COPY RULE: document which file wins when both a standalone override and packaged mod contain the same exact filename. Public precedence is not defined.
08 / CURRENT CONTRACT
Six columns encode identity, decision and cascade
Team or League ID
1 league · 0 team
1 keep · 0 delete
1 deletes players
Requires delete_players=1
Manager deletion flag
id,is_league,is_supported,delete_players,delete_player_related_records,delete_manager09 / SCHEMA HISTORY
A six-column February file can still be obsolete
Initial fifth column; creator described its effect as uncertain.
Fix covers `teamplayerlinks`, `playerloans`, etc.; requires player deletion.
163 bytes · ASCII · LF · no BOM · SHA-256 recorded in dossier.
MIGRATION: replace the old header and review the intended semantics. Renaming a column without retesting destructive rows is not proof of equivalent behavior.
10 / KEEP TEAM
Admission uses `is_supported=1` with a typed ID
Official demonstration: Classic XI.
111205,0,1,0,0,0→Retention decision only.
Use `is_league=0`, `is_supported=1` and non-destructive zeros. Replace the demonstration ID with the exact team ID proven in your mod project.
11 / DELETE TEAM
Deletion flags can widen one row into a data cascade
Official demonstration only.
1337,0,0,1,0,1→Related-record flag remains 0.
DESTRUCTIVE PATH: do not convert a keep problem into an arbitrary delete recipe. Run destructive rows only in a disposable new Career with a preserved CSV and mod build.
12 / LEAGUE DECISION
The same numeric ID means something different when type flips
A team identity lookup.
Official sample deletes all teams in Bundesliga 2.
The documented sample is `20,1,0,1,0,1`. Do not identify an entity by the integer alone: record the `(id, is_league)` pair and the human-readable name.
13 / CASCADE MATRIX
Binary cells do not make every combination sensible
PUBLISHED DEPENDENCY: related-record deletion works only when `delete_players=1`. The public guide does not publish every cascade outcome or failure mode.
14 / FILE RELOAD LIFECYCLE
Editing the CSV is not the event that applies it
15 / A/B EVIDENCE
Compare one baseline Career with one variant
Same build and mod. Capture log plus target absence.
Capture log plus exact target presence and basic smoke test.
TWO PROOF GATES: log output proves an attempted deletion path was recorded. Only the in-Career check proves the target is present.
16 / ROLLBACK
Rollback the file—then create another Career
Return to the captured before-copy.
Preserve it elsewhere for comparison.
The creator says the game uses its original code.
Existing Careers do not reconstruct deleted data.
17 / FAILURE DIAGNOSIS
If nothing changed, inspect lifecycle before IDs
Confirm exact file and which mod copy is active.
Create a disposable new Career after reload.
Migrate fifth column and retest cascade intent.
Verify ID, is_league and is_supported=1.
Audit relations, assets and compdata limits.
Restore CSV, create new Career and review three delete flags.
18 / TOOL BOUNDARY & VIDEO AUDIT
Retention, content and capacity are three separate jobs
Does the new Career remove the typed ID?
Does the team/league actually exist and relate correctly?
Can competition files fit their teams, fixtures and standings?
No current result documented the six-column contract, March migration, new-Career refresh and exact log signals. FC Editor Tool creation, Classic/Icon and World Cup videos prove demand—not this solution.
19 / SUPPORT QUESTIONS
Unsupported teams & leagues FAQ
01Why does FC 26 delete a modded team or league when I start Career Mode?+
The creator says FC 26 v1.4.2 added hard-coded functions that delete teams and leagues outside an internal Career allowlist when a new Career is created.
02Which Live Editor version supports the override?+
The official guide requires FC 26 Live Editor v26.2.6 or newer. The feature also requires Live Editor to be running; without it, the game uses its original code.
03What is the exact CSV filename?+
LE_CM_SUPPORTED_LEAGUES_AND_TEAMS.csv. The standalone path documented by the creator is the Live Editor mods\legacy\data directory.
04Can Database Editor fix the unsupported-team deletion?+
No. The creator explicitly says the allowed list is hard-coded and cannot be altered through database tables or legacy files alone. Live Editor changes the code-layer decision.
05What does is_supported=1 do?+
It tells the Live Editor override to keep that typed ID from this deletion routine. It does not create the entity or guarantee fixtures, assets, capacity or complete Career playability.
06Is release_players_from_national_team still a valid column?+
It is the obsolete February header. On 5 March 2026 the Wiki replaced it with delete_player_related_records after a fix for teamplayerlinks, playerloans and other related records.
07When does Live Editor reload the CSV?+
The published refresh sequence is: load Career, modify the CSV, exit Career, then start a new Career. The fresh copy is loaded for new-Career creation.
08Can the CSV restore a team inside an existing Career?+
No such reconstruction workflow is documented. If the entity was deleted while that Career was created, test the corrected decision in another new Career.
09How do I prove the override worked?+
Capture the relevant deletion log lines and verify the exact typed ID/entity is present inside the new Career. A log line or a green validator alone is insufficient.
10Where are Live Editor logs?+
The official LOGGER documentation says the log file is in the logs folder in the same directory as Live Editor. Use the active attempt and search for the two published deletion phrases.
11What is the difference between this CSV and LIVE_EDITOR_LIMITS.json?+
This CSV controls the hard-coded keep/delete decision. LIVE_EDITOR_LIMITS.json changes compdata capacity ceilings. Retaining a league does not automatically increase fixture or standings limits.
12How do I roll back the override?+
Restore the previous CSV or remove the exact decision row, then start another new Career. Removing the active CSV or running without Live Editor returns to the original game logic.
20 / EVIDENCE LEDGER
Current schema, historical migration and audience demand stay separate
Reviewed 18 August 2026. Creator Wiki, repository template, history, changelog and manifest control product claims. RFC 4180 supplies only generic CSV vocabulary. Videos are context, never parser authority.
Primary problem, path, six fields, example, logs, reload sequence and Live Editor dependency.
Current repository-owned header and five demonstration rows.
Audited 163-byte current artifact.
For Mod Creators capability and offline product boundary.
v26.2.6 introduction and current release chronology.
Current FC build and Live Editor release mapping.
Installation, extraction, launch and mod-manager isolation context.
February creation, March schema fix and later revision chronology.
Replacement of obsolete fifth column and related-record dependency.
Logs-folder location and logger ownership.
Sister JSON capacity surface and log-proof boundary.
Standalone mods/legacy/data placement evidence.
Current six-column table and example values.
General CSV terminology only; not Live Editor parser evidence.
Current control/realism demand; not CSV procedure.
Different creation workflow; does not control Career retention.
Classic/Icon Career intent only.
National-team completeness demand only.