01 / DIRECT ANSWER
Replace the ceiling; prove the replacement
Download the current `LIVE_EDITOR_LIMITS.json`, keep all 16 members and place it in the documented FootballCompEng compdata legacy path. Change one capacity, run Live Editor, enter Career Mode and match both the file-load line and the exact old-to-new value line. Then inspect the responsible in-game competition artifact. The JSON does not create content or guarantee stability.
Current repository artifact, not a hand-copied list.
File discovery plus every changed value.
The accountable competition surface still decides.
02 / FAILURE CLASSIFIER
Capacity, content and retention fail differently
This page owns the executable item limit and its log proof.
Create and connect the actual compdata/database/legacy content first.
The sister unsupported-team CSV owns the keep/delete hook.
Use the competition-state editor; changing a maximum is not an edit.
03 / ACCOUNTABLE SOURCE CONFLICT
One zero separates the Wiki from the file
MAX_FCEDATA_STATISTICS2,400The page has two revisions and keeps this value.
MAX_FCEDATA_STATISTICS24,000Initial commit, reset commit and current artifact agree.
EDITORIAL RULING: use `24000` when reconstructing the current template. Treat `2400` as an unresolved Wiki-table conflict—not a recommended decrease.
04 / CHANGE MANIFEST
Record six identities before raising one number
05 / ORIGINAL JSON EXPERIMENT
Make every delta answerable
Load a local file or the adversarial fixtures. The desk checks the current 16-member contract, detects duplicate and unknown names, exposes decreases and source conflict, builds a delta manifest and matches it against creator-published log grammar.
COMPDATA CHANGE CONTROL
02 / FILE CONTRACT
CURRENT 16-MEMBER OBJECT03 / STRUCTURAL REVIEW
Exact filename, 16 unique members and positive integer values pass.
A baseline file can prove discovery, but it should not emit value-change evidence.
Matching logs prove reported replacement attempts, not competition stability. Inspect the exact in-game artifact.
VIEW CHANGE RECEIPT +
FILE / LIVE_EDITOR_LIMITS.json CONTRACT / BASELINE MEMBERS / 16/16 DELTAS / 0 (0 UP · 0 DOWN) FINDINGS / 0 ERROR · 0 WARNING PROTOCOL / 0/6 LOAD SIGNALS / 0 CHANGE MATCH / 0/0 PROOF / AWAITING LOG IN-GAME COMPETITION PROOF / REQUIRED
06 / VALIDATION RESULTS
Ten fixtures define what the lab can prove
16 exact members · zero deltas
Standings + objectives increases
Tenfold decrease versus repository
Invalid JSON syntax
Parser interoperability risk
Partial behavior unpublished
Not in current template
Not a positive safe integer
Valid file is not execution proof
Still needs in-game artifact
07 / FILE DISCOVERY
Two delivery routes meet at the same legacy file
dlc\dlc_FootballCompEng\dlc\FootballCompEng\data\compdata\LIVE_EDITOR_LIMITS.jsonAdd the JSON to this legacy directory in the mod project.
C:\FC 26 Live Editor\mods\legacy\dlc\dlc_FootballCompEng\dlc\FootballCompEng\data\compdata\LIVE_EDITOR_LIMITS.jsonThe root can differ; preserve the internal chain.
ACTIVE-COPY RULE: if both delivery routes contain the file, record which mod/dataPath is active. Public precedence behavior is not documented.
08 / JSON CONTRACT
Syntax is the first gate—not the last
Exact creator-published discovery filename.
Current template contains 16 name/value members.
Conservative lab rule; private parser tolerance is unknown.
RFC 8259 warns duplicate-name handling can differ.
SHA-256 351162c8…0311bc09 / CURRENT DEFAULT LEDGER
Sixteen capacities; eleven named owners
MAX_FCEDATA_ACTIVETEAMS64activeteams.txtKNOWNMAX_FCEDATA_ADVANCEMENT4,500advancement.txtKNOWNMAX_FCEDATA_COMPAVGS115compids.txtKNOWNMAX_FCEDATA_COMPOBJECTS2,500compobj.txtKNOWNMAX_FCEDATA_COMPTEAMS500initteams.txtKNOWNMAX_FCEDATA_FIXTURES5,000?UNMAPPEDMAX_FCEDATA_SCHEDULING8,500schedule.txtKNOWNMAX_FCEDATA_SCRIPTFUNCS1,020tasks.txtKNOWNMAX_FCEDATA_SETTINGS5,500settings.txtKNOWNMAX_FCEDATA_STAGEADVANCE115?UNMAPPEDMAX_FCEDATA_STANDINGS6,000standings.txtKNOWNMAX_FCEDATA_STATISTICS24,000?CONFLICTMAX_FCEDATA_WEATHER420weather.txtKNOWNMAX_FCEDATA_OBJECTIVES670objectives.txtKNOWNMAX_FCEDATA_STADIUM100?UNMAPPEDMAX_FCEDATA_DEEPSIM50?UNMAPPEDVERSION LABEL: the Wiki calls these FC 26 v1.6.0 defaults. The current repository template reviewed against the v1.6.6-era manifest contains the same values except the exposed Wiki `STATISTICS` conflict.
10 / SOURCE-FILE OWNERSHIP
A key name does not prove its entire dependency graph
`activeteams.txt` and `initteams.txt` are named.
Only advancement has a published source-file name.
Schedule is mapped; fixtures remains `?`.
Standings is mapped; statistics remains `?` and has a value conflict.
`settings.txt` and `tasks.txt` are named.
Fixtures, stage advance, statistics, stadium and deep sim show `?`.
11 / ONE-VARIABLE DESIGN
One changed member creates one accountable hypothesis
Same game, editor, mod and disposable save.
Change only the member tied to observed evidence.
Match old/new and inspect the in-game owner.
ESCALATION: only add a second delta after the first experiment is reproducible. This OAT protocol is the article’s safety design, not a published engine requirement.
12 / CREATOR-PUBLISHED EXAMPLE
The screenshot supplies deltas—not safe maxima
MAX_FCEDATA_STANDINGSLog grammar and original template history agree.
MAX_FCEDATA_OBJECTIVESCurrent template was reset to 670 after the example.
The values demonstrate how a replacement is reported. The guide never labels 6500 or 800 as universal recommendations for every mod.
13 / UNKNOWN UPPER BOUNDS
No public number turns capacity into safety
No upper bound per collection.
No “raise A, therefore raise B” graph.
No exhaustive crash/silent-truncation matrix.
No guarantee for values below defaults.
STOP CONDITION: if a bigger value removes one symptom but creates scheduling, standings, progression or save instability, revert and capture the smallest reproducible case. Do not keep multiplying every limit.
14 / LOAD LIFECYCLE
The file becomes evidence only inside an isolated run
15 / THREE PROOF GATES
Discovery, replacement and outcome are separate
Load LIVE_EDITOR_LIMITS.jsonLive Editor reports the exact file loaded.
STANDINGS: 6000 → 6500Member, old value and new value match the variant.
Fixtures, standings, objectives or another specific surface works.
16 / ROLLBACK
Return the allocation—then verify the return
Use the preserved 545-byte artifact or before-copy.
Keep build, mod and save identity fixed.
Do not confuse a remaining second copy with rollback.
File state alone cannot prove game state.
17 / FAILURE DIAGNOSIS
Follow the first missing proof gate
Verify the deep chain and which legacy layer is launched.
Compare all 16 names and proposed values.
Match the same run, exact member and repository default.
Audit source file, relations and other accountable arrays.
Revert the last delta and return to one variable.
The creator says original code returns without Live Editor.
18 / TOOL BOUNDARY & VIDEO AUDIT
Capacity is one layer of a playable competition
How many items can an executable collection hold?
Do files, entities and relationships actually exist?
Does new-Career logic keep the typed team/league?
Eight searches found no current tutorial for the 16-key JSON, the `STATISTICS` source conflict, deep paths and exact log matching. Results were broad Live Editor, FC Editor Tool creation, World Cup mods, repacks and FIFA 14-era compdata.
19 / SUPPORT QUESTIONS
FC 26 compdata limits FAQ
01What does LIVE_EDITOR_LIMITS.json change?+
It supplies replacement ceilings for 16 compdata item collections that the creator says are otherwise hard-coded in the FC 26 executable. It changes capacity, not competition content.
02What is the exact filename?+
LIVE_EDITOR_LIMITS.json. The browser lab rejects other filenames because the creator documents this exact discovery name.
03Where does the JSON file go?+
Use the documented FootballCompEng compdata legacy directory in FIFA Editor Tool, or the same deep chain under the Live Editor mods\legacy directory. Both exact paths are printed on this page.
04Do I always need Live Editor?+
Yes. The official FAQ says the override logic is implemented in Live Editor; without it the game uses its original code. FIFA Editor Tool can package the legacy file but does not replace the runtime hook.
05Is MAX_FCEDATA_STATISTICS 2400 or 24000?+
The current official repository template and both template commits use 24000. The Wiki table says 2400, so this page exposes it as an unresolved documentation conflict rather than silently copying it.
06What is the safe maximum for each limit?+
The creator publishes defaults but no safe upper bounds, dependency graph or universal multiplier. Raise one accountable member at a time and prove its log and in-game effect.
07Can I provide only the key I want to change?+
Partial-file behavior is not publicly specified. This page conservatively requires all 16 current repository members exactly once.
08Can I lower a compdata limit?+
The JSON format accepts numbers, but the product documentation does not explain shrink behavior. The lab marks decreases for review and recommends testing only in an isolated disposable setup.
09How do I know the file was loaded?+
The official guide says the active log should contain Load LIVE_EDITOR_LIMITS.json after entering Career Mode. That proves reported discovery, not individual value changes.
10How do I prove a value changed?+
Match a Set New Compdata Max Items line to the same member, old default and proposed new value, then inspect the accountable competition artifact in game.
11Is this the same as keeping unsupported teams and leagues?+
No. This JSON changes capacity ceilings. The sister CSV page controls a separate hard-coded Career keep/delete decision for typed team and league IDs.
12How do I roll back?+
Restore the current repository template or your preserved before-copy, restart the isolated session, confirm the reverted old-to-new log line is absent and re-check the competition artifact.
20 / EVIDENCE LEDGER
File contract, documentation and audience context stay labeled
Reviewed 18 August 2026. The creator Wiki, current template, two template commits, screenshots and manifest control product claims. RFC 8259 controls generic JSON vocabulary only. Videos explain demand and adjacent workflows—not FC 26 limit semantics.
Primary mechanism, paths, v1.6.0 table, dependency on Live Editor and exact log phrases.
Current 545-byte, 16-member JSON artifact and repository-owned values.
Direct machine-readable artifact used by the local forensic check.
Initial 24000 statistics value and 6500/800 example state.
Reset standings and objectives while leaving statistics at 24000.
Two Compdata Limits revisions on 1 June 2026.
For Mod Creators classification and offline Live Editor product identity.
Current FC executable and Live Editor release mapping reviewed 18 August 2026.
Logs-folder ownership and logging-level vocabulary.
Exact standalone deep path and filename in Explorer.
Load plus standings/objectives old-to-new evidence.
Sister keep/delete hook that must stay separate from capacity.
JSON grammar and duplicate-name interoperability risk; not product-parser evidence.
Current official editor/tool identity for the packaged legacy path.
Current mod-creator demand context; not limit procedure.
Current content-creation workflow, distinct from capacity replacement.
Older competition-creation vocabulary only.
Older compdata demand context; not the FC 26 JSON contract.