01 / DIRECT ANSWER
How do I make FC 26 Live Editor changes save permanently?
Prove five separate checkpoints. A green result at one checkpoint cannot stand in for the next.
- 01Back up
Untouched Career slot.
- 02Commit entity
Player / Team Save.
- 03Refresh view
Exit and re-enter screen.
- 04Save Career
Separate test slot.
- 05Reload exact slot
Same ID and game date.
- 06Test survival
Match, day, restart.
Record the first boundary where the new value becomes old. That boundary—not the generic phrase “not saving”—owns the next investigation.
02 / FIVE DIFFERENT PROOFS
What does each Save checkpoint actually prove?
Live Editor, the current FC screen and the Career slot are three separate state holders.
A control accepted the number or option.
NOT APPLIED YETPlayer, Team or row-specific action ran.
LIVE STATEFC 26 displays the new live state.
VISIBLE STATEA named test slot records current state.
PERSISTENT CANDIDATEReload, match and restart agree.
PROVEN RESULT03 / DESTINATION BEFORE ACTION
Are Career Save, Save Squads and runtime changes the same?
No. Choose the object and destination before deciding that a write failed.
Normal Player/Team entity Save, refresh, then FC Career Save.
Customize → Profiles → Save Squads; later load/use current squads.
Automatic apply; only Career-file tables survive restart.
Game recalculates attributes; normal Player Save is not permanent.
Runtime override visible only while using the tool.
FUT, Clubs/Pro Clubs and Volta are outside creator scope.
04 / RECOVERY BEFORE PROOF
How should I protect the Career before a persistence test?
Use two slots: one untouched recovery point and one disposable test write.
Use Save As before opening the entity. Never overwrite this slot during diagnosis.
Build the full backup →Record the Career name, in-game date, entity ID, field and exact before/after value.
84 → 9105 / CHECKPOINT 01
Which Save action belongs to the Live Editor field?
Use the rule documented for that object—generic Save, row Save or automatic apply.
Normal edits require Player → Save or Team → Save before the game can own the new entity state.
Complete the nested name dialog, then follow the surrounding entity workflow where documented.
The Team Wiki gives the fixture edit its own Save button.
These exact surfaces are described as automatic; do not invent another confirm action.
No confirmation is needed, but apply and permanent storage remain different questions.
06 / INTERACTIVE FULL-TIME REVIEW
Where did my Live Editor change first revert?
Answer from one edit timeline. Later checkpoints remain locked until the earlier proof exists.
Manager Career, a squad file, created Player Career and Database Editor do not write to the same destination. Choose the state in which you made the edit.
LOCAL INPUT ONLY · No Career slot, player, table, mod or account is inspected.
07 / DOCUMENTED OVERWRITE
Why does FC 26 Edit Player undo Live Editor changes?
It can hold an older player snapshot. The creator explicitly warns that leaving FC’s own Edit Player screen can overwrite the tool’s change.
Live Editor writes a new value while FC still owns an older form state.
The older in-game data can be written back over the live edit.
No FC Edit Player form is waiting to overwrite the entity.
08 / CHECKPOINT 03
Can the edit be saved while the screen still shows the old value?
Yes. The creator tells users to leave and re-enter the current screen before judging the result.
- 01Close the overlay
Keep the Career running; do not reload yet.
- 02Exit the current FC screen
Leave Squad Hub, Transfer Hub or the current cached view.
- 03Enter it again
Force FC 26 to rebuild the visible view.
- 04Compare the same entity
Use ID and field, not a similar player or another save.
Player names have an extra documented cache caveat: save the Career, exit and load it again when the displayed name remains stale. This is not the same as a globally blank Live Editor Name column; separate those identity surfaces first →
09 / CHECKPOINT 04
How do I prove the edit entered the FC 26 Career save?
Write a separate slot and identify it before reload. Autosave is not an isolated diagnostic control.
SAVE AS
EXACT SLOT
Continue to match/day/restart survival.
Preserve the slot, exact versions and one-field timeline.
10 / DIFFERENT DESTINATION
How are Live Editor squad-file changes saved?
They use the FC squad-profile workflow, not an existing Career slot.
The current Reddit playstyle report tests a created player in Kick Off and sees the value disappear. That symptom is useful mode evidence, but it does not turn Career Save into the correct squad-file action.
11 / STORAGE SCOPE
Why do Database Editor changes reset after restarting FC 26?
Not every game database table is stored in the Career file. Automatic apply does not expand what the Career format contains.
The creator recommends using RDBM25 to inspect which tables the Career actually stores.
APPLY → CAREER SAVE → RELOADThe Wiki says these tables reset every time the game restarts.
APPLY → RESTART → RESETDo not insert guessed primary keys or mass-edit rows while testing. The creator warns that relational database mistakes can brick the Career.
12 / GAME-OWNED RECALCULATION
Why do Player Career attributes or playstyles revert after a match?
Created Player Career is VPRO, and its real attributes are owned by the growth tree rather than a normal persistent player record.
The players table changes during the session.
The game restores the growth-owned value.
The creator says permanent normal editing is impossible for this VPRO attribute path and documents a script/mod model that must be applied when playing. Do not generalize a Manager Career Player Save tutorial to a created VPRO.
13 / ROUTE THE FIRST RESET
What does each reset time mean?
Timing identifies the owner more reliably than repeating the Save button.
Reopen the same entity and compare the value before leaving the screen.
Checkpoint 01 →Repeat outside FC Edit Player.
Checkpoint 02 →Verify exact slot, field and versions.
Evidence packet →VPRO is the documented example; identify the owning system.
VPRO boundary →Check database table scope; issue #31 remains unresolved.
Storage scope →Custom team names live in creator CSV files and require the tool.
Creator rule ↗14 / PRESERVE SIGNAL
What should I avoid, and what belongs in a persistence report?
Do not change the platform to explain an edit that already worked live. Report one timeline with one divergence.
It cannot add a missing entity Save or change VPRO ownership.
Not a repair for a value visible in the current session.
Video #16/#17 fail provenance and safety boundaries.
Keep Slot A untouched and Slot B disposable.
- 01
FC build + Live Editor version
- 02
Mode, Career slot/date, entity ID
- 03
Exact field: before → after
- 04
Editor action and FC screen
- 05
Refresh and Career Save result
- 06
First reset: reload / match / restart
Issue #31 reports the symptom on FC 26 v1.6.1. It has no assignee, label, maintainer diagnosis, linked development or verified workaround. Use it as a report boundary, not a universal repair.
Inspect issue #31 ↗15 / QUICK QUESTIONS
FC 26 Live Editor saving FAQ
01Do I need to save in Live Editor and FC 26?+
For normal Player and Team edits in Manager Career, yes. Use Player → Save or Team → Save, refresh the current FC screen, then save the Career in FC 26.
02Why is the old value still visible after I press Save?+
The current FC screen may be cached. Exit that screen and re-enter it before deciding the edit failed. Player-name display can require saving, exiting and reloading.
03Why do my created Player Career attributes reset after a match?+
The creator documents that VPRO attributes are owned by the growth tree and ordinary player-table edits are overwritten. The normal Manager Career save chain cannot make those VPRO attributes permanent.
04Why does a Database Editor value reset after restart?+
Database changes apply automatically, but only tables stored in the Career file persist. Tables outside that file are documented to reset when the game restarts.
05Why does a custom team name disappear without Live Editor?+
The creator describes custom team names as temporary overrides stored in Live Editor CSV files and visible only while playing with the tool.
16 / EVIDENCE
Sources and verification boundaries
Creator Wiki pages control save mechanics and limitations. Issues and community posts prove symptoms only; videos expose workflows and unsafe search pollution.
Controlling Player persistence sequence: avoid FC Edit Player, use Player → Save, refresh the game screen and save the Career.
Team → Save and Career Save, auto-saved fields, Save Squads route and temporary custom-team-name storage.
Automatic database apply plus the explicit limit that only tables stored in the Career file survive restart.
Created Player Career growth-tree ownership, post-match reversion and runtime script requirement.
Manager name has a distinct dialog Save; the page does not document a universal persistence chain.
Version-specific context including the v26.1.3 Player Career playstyle-reset fix.
Current complete FC26.exe build → accepted Live Editor range; compatibility is separated from field persistence.
Open current restart-reset report on FC 26 v1.6.1; no maintainer diagnosis, fix or workaround.
Current display/list symptom used to prevent misclassifying a missing label as erased persistent data.
Current ???? display report; open and unresolved, not evidence that a Career value was deleted.
Audience mode-confusion evidence. Creator VPRO/Player documentation controls the conclusion.
Shows a user separating visible edits, Career Save and a later vanilla-launch concern; no universal persistence diagnosis.
Creator-linked visible Player edit flow reconstructed beside the current Wiki; exact instructions come from the Wiki.
Current audience use cases and in-save vocabulary; no controlled reload/restart proof.
Clear per-entity Save and active-Career behavior. FC 25 footage cannot establish current FC 26 support.
Demonstrates a live-update mental model that omits Editor Save and Career Save; third-party download route rejected.
Search-pollution evidence only: unrelated package and global Defender shutdown are rejected.
Checked: 11 August 2026 against five creator Wiki pages, manifest/changelog, three current public issues, two current community cases and seven video audits.
Current reference: FC 26 v1.6.6 build 1.0.139.20381 → Live Editor v26.3.5–v26.3.6.
Test limitation: this environment cannot run licensed FC 26; the five-checkpoint protocol is reproducible but not presented as our own completed in-game test.
Wiki boundary: Player/Team/Database/VPRO pages own persistence rules. The Manager page only documents its name dialog and does not justify a universal manager-save promise.
Issue boundary: #31, #35 and #42 are open without maintainer diagnosis. Display symptoms are not automatically persistence failures.
Video boundary: three new caption tracks were normalized; two current topic results had no captions. Third-party download and Defender-disable instructions were rejected.
Review trigger: creator save-rule change, manifest/changelog update, issue resolution or changed FC Career/squad navigation.
Classify crash timing: before game window, during injection, after the menu, opening an editor, applying an edit or loading a Career.