01 / DIRECT ANSWER
How do you transfer a player safely?
Make a separate Career save, press F9, open Features → Players and open the exact player. For a permanent move use Player → Transfer → Transfer Player, verify the destination and every live form value, then press Finalize Transfer once. Confirm the new club in-game, save to a new slot, reload and match the same player ID. A closed window or club transfer ban does not block the creator-documented direct move.
02 / ACTION CLASSIFIER
Start with the expected football state, not a familiar verb
Current club → destination
Permanent club membershipParent ⇄ temporary club
Temporary club membershipTemporary → parent club
End an active loanCurrent club → Free Agents
Remove club membershipSame club + market flag
No club movementRelease is not Delete. Release changes membership; deleting a player removes the entity and belongs to the separate create/clone/delete workflow.
03 / INTERACTIVE CLEARANCE DESK
Rehearse the route before opening the live transaction
This browser-only desk does not read FC 26 or change a save. It exposes invalid state/action combinations and builds the proof checklist you must close in the live Career.
Transfer Clearance Desk
Plans a route. Never reads or changes FC 26.
Choose the football transaction
Declare where the player is now
Standard starting state for a new transfer, loan, release or list change.
EVIDENCECurrent GUI Wiki + form + creator video
Names are documented visually. Public GUI ranges, units and validation are not.
Close the clearance checks
This desk cannot read the save. Close every evidence check against the live Career.
0/6 checks · TRANSFER · At current club04 / CURRENT GUI ROUTE
The permanent-transfer path has four accountable checkpoints
Enter the game mode
F9 → Features → Players
Open the exact player
Player → Transfer → Transfer Player
The live form is the final authority. Check player name/ID, destination team and all values before using Finalize Transfer. This guide intentionally provides no imitation of that destructive control.
05 / OFFICIAL FORM CONTRACT
Six labels are visible; their universal ranges are not published
Do not import legacy Lua units into the GUI. Public evidence does not establish universal form ranges, contract-length units, currency conversion or validation behavior.
06 / PERMANENT TRANSFER
A direct transfer changes the player’s club immediately
The creator documents transfers both from and to your team. The move can go through with the normal transfer window closed or the team transfer-banned, so never use base-game availability as evidence that a direct edit cannot happen.
07 / START A LOAN
A loan preserves the parent-club relationship
The current Wiki documents either the Loan menu item or the Is Loan? checkbox in the transfer form. Record both parent and temporary clubs; “the player appears elsewhere” is not enough proof of a correct loan.
08 / TERMINATE LOAN
Terminate is a return operation, not a release
Terminate Loan was added as a current feature in v26.1.4. The exact return-to-owning-club semantics come from the creator’s legacy Lua API, not a detailed current GUI page; verify the result in your version and Career.
09 / RELEASE FROM TEAM
Release removes club membership; it does not erase the player
Current feature/menu; destination semantics are legacy-documented and require live proof.
A separate Player Editor operation with a different risk and recovery model.
10 / ON-LOAN CONFLICT
An already-loaned player is a hard stop
The creator’s legacy API warns that moving or releasing an already-loaned player can damage the Career. Current GUI documentation does not promise an automatic resolver. Preserve a separate save and terminate the active loan first.
11 / MARKET LIST STATE
Listed is an availability signal, not a transaction
Market flag for permanent-move interest.
Market flag for a temporary move.
Choose one natural state. Legacy creator documentation warns against making a player both transfer-listed and loan-listed simultaneously.
12 / CONTRACT STATE
Clause and contract fields travel with the move form
Visible in the current transfer form; range and clearing behavior unpublished.
Do not assume that a legacy Lua “months” parameter defines the current GUI unit.
Record the exact displayed value before finalizing and compare after reload.
13 / OVERRIDE BOUNDARIES
Direct movement and normal Career negotiations are separate layers
Current transfer Wiki statement.
Separate v26.2.5 changelog items for base-game approaches.
14 / TRANSACTION PROOF
The safe result is a reloaded football relationship
Save a separate Career slot
Record player name + ID
Confirm current / parent club
Capture destination + live fields
Use the current GUI once
Re-enter squad/transfer view
Write a new Career slot
Match identity + destination
For a loan, prove two clubs. The temporary destination and the parent/owning relationship must both survive reload.
15 / ROLLBACK
Transfer History is secondary; the recovery slot is universal
Works as the recovery boundary for transfer, loan, release and list-state mistakes.
Backup & restore guide →The README says transfers can be quickly undone. It does not promise every loan, release or flag appears there.
QUEUED DEEP GUIDE · ARTICLE 5016 / SCOPE BOUNDARIES
Do not combine three different transfer systems
This article’s current GUI route.
Base-game current-squads workflow; not an active-Career Live Editor proof.
A different request-and-negotiation path.
The legacy Lua docs also state Career-only/tested boundaries for some scripted calls. Those statements cannot establish current GUI support in every game mode.
17 / DIAGNOSIS
Route failure by identity, state, input or persistence
Stop saving; compare name and player ID.
Record version, mode, menu and exact symptom.
Check parent, temporary and destination clubs.
Separate editor result from Career save slot.
“Only Save/Edit Player’s Club” is a reported symptom, not a diagnosed cause. Official issue #1 remains open without a published resolution; do not invent a universal fix.
18 / VIDEO AUDIT
The creator clip proves the route; fresh YouTube results define the boundaries
Open player, form, finalization and loan alternative.
CURRENT FC 26 CONTEXTBroad Live Editor showcaseF9 and visible immediate move; no field-range or reload proof.
Results split across base-game Edit Teams, Player Career, older editors and uncaptained uploads.
Four fresh searches added current base-game Club Transfers and Player Career transcripts, plus a general transfer-system analysis. All are useful for entity boundaries; none overrides the current creator Wiki, screenshots or changelog.
19 / FAQ
Player transfer questions, answered by state
01How do I transfer a player in FC 26 Live Editor?+
Back up the Career, load the game mode, press F9, open Features → Players, open the exact player, then use Player → Transfer → Transfer Player. Verify the live form, press Finalize Transfer once, confirm the new club in-game, save to a new Career slot and reload.
02Can Live Editor transfer a player when the transfer window is closed?+
Yes. The creator’s current Player Transfers Wiki says the transfer goes through even when the window is closed.
03Can it transfer a player from a transfer-banned club?+
Yes. The same current Wiki says a team transfer ban does not block the direct Live Editor transfer.
04How do I loan a player instead of transferring them permanently?+
The current Wiki documents two routes: choose Loan from the transfer menu, or open the transfer form and enable Is Loan?. Confirm parent and temporary clubs before finalizing.
05What does Terminate Loan do?+
It ends an active loan. The return-to-parent-club meaning is documented in the creator’s legacy Lua API; because current GUI documentation is brief, verify that exact destination in your live Career.
06What does Release Player From Team do?+
It removes the player from the current team. The Free Agents destination is documented in the creator’s legacy API, so treat it as a legacy-derived expectation and prove the current GUI result after reload.
07Is releasing a player the same as deleting them?+
No. Release changes club membership; delete removes the player entity and belongs to a different Player Editor workflow. Do not use the verbs interchangeably.
08Can I transfer or release a player who is already on loan?+
Stop and resolve the loan first. The creator’s legacy API warns that transferring or releasing an already-loaned player can damage the Career. Current GUI documentation publishes no automatic conflict repair.
09Which fields are in the Transfer Player form?+
The creator screenshot shows To Team, Transfer Sum, Wage, Release Clause, Contract Length and Is Loan?. Public documentation does not define universal GUI ranges, units or validation rules.
10Does transfer-listed or loan-listed move the player?+
No. Those are market/list-state flags while the player remains at the same club. Legacy creator guidance warns against setting both at the same time.
11Do I need the negotiation or approach bypass for a direct transfer?+
No prerequisite is documented. The changelog lists Disable negotiation status check and Always allow transfer & loan approach as optional Miscellaneous features; the direct Player Editor transfer is documented separately.
12How do I undo or prove a Live Editor transfer?+
Keep a separate pre-edit Career slot. After the move, verify the player ID, destination and loan relationship, save to a new slot and reload. The README says Transfer History can quickly undo current-season transfers, but does not promise coverage for every loan, release or list-state edit.
20 / EVIDENCE LEDGER
Sources, role and confidence boundary
Creator documentation controls the current feature. Legacy creator material is labelled wherever it supplies semantics or risk warnings. Community and video sources explain audience intent or system boundaries—not hidden GUI rules.
Current GUI route, closed-window/transfer-ban behavior, form screenshot and loan alternatives.
Feature chronology: clause, transfer/loan/release/terminate, list states and optional approach checks.
Between-team transfer capability and current-season Transfer History quick undo statement.
Backup-first rule, Manager Career focus, refresh and Career/Squads persistence.
Explicitly legacy semantics and on-loan risk warnings; not a current GUI range authority.
Current editor tier/version snapshot at the research freeze.
Open player → Transfer Player → form → finalize; loan as alternate action or checkbox.
Exact six visible GUI field labels and Finalize Transfer control.
Transfer Player, Loan Player and Release Player From Team menu labels.
Observed “Save/Edit Player’s Club only” symptom; no confirmed cause or fix.
Current demand when AI clubs refuse loans and prospects need minutes.
Current confusion between temporary and permanent movement.
Release/re-sign intent only; not technical authority.
Current base-game player-transfer friction; not proof of an editor fix.
Current negotiation/contract pain point; not editor behavior evidence.
F9 and forced-transfer visual context; no GUI-range or reload authority.
Different main-menu current-squads workflow and team-sheet proof boundary.
Different My Agent/objectives route; entity boundary only.
Different base-game transfer/loan path; boundary evidence only.
Audited and rejected for Live Editor fees, loan math and clause rules.