01 / DIRECT ANSWER
A transfer ban closes two incoming lanes—not the whole window
In the exact Career, open F9 → Features → Teams → team → Edit → Team → Transfer Ban. Set the team or league state and end date, use the dialog’s own Save, keep running the Career through Live Editor, then test one incoming and one outgoing move.
02 / ENTITY CLASSIFIER
Club, league, player and every team are four different jobs
The UI covers a selected team and its league. Player records and the database-wide script belong to Lua.
Full team rule
Selected club’s league
Consequences unpublished
Global write
03 / INTERACTIVE CLEARANCE BOARD
Classify the restriction before touching the registry
This browser-only planner validates context, entity, date, save lane and recovery proof. It never connects to FC 26 and contains no fake Ban, Save or Run Script action.
Transfer Clearance Board
Plans a receipt · writes no game data
Select the real execution context
Preview the record, not a fake action
Close the correct persistence lane
C:\FC 26 Live Editor\extensions\careers\<SAVE_UID>\transfer_bans.jsonTransfer Ban dialog Save → transfer_bans.json → reload via Live EditorThe plan is in scope. Finish the backup and identity receipt before changing the real registry.
Club · ban · 0/3 recovery checks04 / EXACT TEAM EDITOR ROUTE
The Transfer Ban dialog is nested under the selected team
Run a compatible Live Editor, load the intended Career, then identify the team before opening the feature.
- 01Backup Career
Use another save slot.
- 02Load through LE
The runtime enforces bans.
- 03Press F9
Features → Teams.
- 04Exact team
Find → Edit.
- 05Team menu
Transfer Ban.
05 / MODAL ANATOMY
Two Yes/No controls decide the target population
The creator screenshot shows team identity, current state, Team Is Transfer Banned, Ban All Teams In League, Day/Month/Year and explicit Save/Cancel.
06 / TRANSACTION MATRIX
“Transfer ban” is deliberately asymmetric
The published team rule restricts arrivals while departures remain possible. It is not a total transaction freeze.
07 / END-DATE MODEL
Use a real date; “forever” is only a far-future approximation
The UI defaults to roughly one year. Lua accepts an unsigned integer in YYYYMMDD format. The creator suggests a year near 2100 for a practical long-term ban—there is no permanent Boolean.
Human-readable form fields.
Official all-team script value.
08 / LEAGUE-WIDE OPERATION
The selected team supplies the league scope
To ban the league, select a member club and set Ban All Teams In League → Yes. For a league-wide removal, use No. Hidden teams, later promotion/relegation and exception behavior are not documented.
09 / UNBAN PATHS
Reverse the same entity—do not widen the rollback
One club: Team Is Transfer Banned → No. One league: league flag → No. One Lua team/player: RemoveTeam or RemovePlayer, followed by API Save.
10 / RUNTIME DEPENDENCY
A saved JSON record is not a standalone game rule
The creator says the restriction works only while playing the Career with Live Editor. Launching the same save without the runtime breaks the enforcement contract.
Supported lane.
Do not assume the JSON becomes native save data.
11 / JSON OWNERSHIP
The save UID—not the Career filename—owns the external registry
Back up the file beside the Career slot. A Career-only backup may not preserve this separate restriction state.
C:\FC 26 Live Editor\extensions\careers\<YOUR_SAVE_UID>\transfer_bans.jsonCareer binary + matching save-UID extension file = complete recovery set.
12 / TWO SAVE LANES
UI Save and Lua Save reach the same external registry differently
The dedicated Wiki does not prescribe a second generic Team Save after its modal. Lua mutations do require the manager’s Save method for restart persistence.
transfer_bans.json→Reload via LETRANSFER_BAN_MANAGER:Save()→Reload via LE13 / TEAM VS PLAYER
A documented API record does not publish its gameplay matrix
AddPlayer, RemovePlayer and IsPlayerBanned exist. But no creator page explains player sale, loan, release, recall or negotiation behavior. Keep that record in a controlled verification lane.
Buy and loan-in blocked; sell and loan-out allowed.
Transaction consequences remain unknown.
14 / LUA METHOD MAP
Mutate, query and persist are separate operations
Dates are unsigned YYYYMMDD integers. Query calls do not write state; mutation calls do not replace Save.
AddTeam(teamid, date)AddPlayer(playerid, date)RemoveTeam(teamid)RemovePlayer(playerid)IsTeamBanned(teamid)IsPlayerBanned(playerid)GetAllBans()Save()Required for restart persistence.
15 / ALL-TEAM SCRIPT AUDIT
The official script is a global write with no safety rails
The current file iterates every valid row in teams, calls AddTeam(teamid, 20990101), saves once and displays Done. It has no league filter, exceptions, dry run or unban branch.
lua/transfer_ban_all_teams.lua- Load manager
- Read teams table
- Add every team ID
- Save once
16 / SEARCH-INTENT SEPARATION
Four common “ban” searches belong to other systems
Live Editor Transfer Bans are offline Career records. They neither cause nor remove platform enforcement.
Platform enforcement.
Online access state.
Career narrative mechanic.
Base-game Career setup.
17 / PROOF & ROLLBACK
Verify both directions before trusting the embargo
A correct receipt proves identity, persistence and the asymmetric result—not just a checked UI flag.
- 01Before receipt
Slot, UID, versions, target and current ban list.
- 02Write once
Dialog Save or API Save—not both.
- 03Reload through LE
Open the same Career and same target.
- 04Test arrivals
Buy and loan-in should be blocked.
- 05Test departures
Sell and loan-out should remain open.
18 / VIDEO RESEARCH
Fifty-five unique results exposed the audience—and heavy intent pollution
Four fresh searches returned 60 slots and 55 unique videos. Creator documentation and scripts therefore control operations; videos contribute language and use cases.
Academy/rebuild motivation and the no-buy story; base-game context only.
UI CORROBORATIONTeam or league periodUseful visual fragment; Wiki controls exact behavior.
FC 26 OVERVIEWClub transfer banConfirms audience vocabulary, not persistence.
Account, FUT, repack, first-window and Football Manager collisions removed.
19 / FAQ
Transfer-ban questions answered at the correct entity boundary
01Where is Transfer Ban in FC 26 Live Editor?+
Load the Career through Live Editor, press F9, open Features → Teams, find the exact team, choose Edit, then Team → Transfer Ban.
02What does a team transfer ban block?+
The creator says it blocks buying players and loaning players in. Selling and loaning players out remain allowed.
03Can I ban every club in one league?+
Yes. In the selected team’s Transfer Ban dialog, use Ban All Teams In League → Yes to ban the league, or No when removing the league-wide ban.
04How long does a transfer ban last?+
The dialog uses an end date and defaults to roughly one year. A far-future year such as 2100 is an approximation for forever, not a permanent flag.
05Does the ban work without Live Editor running?+
No. The dedicated Wiki says it works only while the Career is played through Live Editor.
06Where are transfer bans saved?+
In C:\FC 26 Live Editor\extensions\careers\<YOUR_SAVE_UID>\transfer_bans.json, outside the Career binary.
07Do I need Team → Save after the Transfer Ban dialog?+
The dedicated dialog has its own Save button and the feature Wiki does not instruct a second generic Team Save. Use the dialog Save, preserve the JSON and verify after a Live Editor reload.
08Can Lua ban one player?+
Yes. The API exposes AddPlayer, RemovePlayer and IsPlayerBanned, but the creator does not publish the exact player-level sale and loan consequences.
09How do I persist a Lua transfer ban?+
Call TRANSFER_BAN_MANAGER:Save() after AddTeam, AddPlayer, RemoveTeam or RemovePlayer, then reload through Live Editor and verify.
10Is there an official script to ban every team?+
Yes. The current script iterates the teams table, adds every team through 20990101 and saves once. It has no dry run, filter or exceptions.
11Is there an official script to unban every team?+
No matching bundled global-unban script was found. The API can remove individual records, but this guide does not invent an official bulk recipe.
12Is this the same as an EA account or FUT Transfer Market ban?+
No. This is an offline Career restriction enforced by Live Editor; it does not unlock or modify EA account enforcement or FUT market access.
20 / EVIDENCE LEDGER
Creator sources own behavior; the audit preserves every uncertainty
Official Wiki pages, API records, scripts, screenshots, changelog and manifest control claims. Videos explain audience intent and never fill an unpublished product gap.
Controls Career/runtime scope, UI route, team transaction rules, league toggle, end date and JSON path.
Controls the F9 Team Editor entry and separate Career backup instruction.
Defines Add/Remove/Is/Get methods, YYYYMMDD dates and the required API Save call.
Defines id, date_end and member_type 0 Team / 1 Player.
Proves the all-team loop, 20990101 end date and one final Save call.
Shows the creator’s current team/player audit output.
Confirms team/league toggles, date fields and explicit modal Save/Cancel controls.
Visually confirms Team → Transfer Ban.
Dates Transfer Bans in Team Editor to v26.1.2.
Current compatibility snapshot for FC 26 and Live Editor.
Defines the PC Live Editor product and offline editor family.
Current audience overview names giving a club a transfer ban; creator docs control scope.
Corroborates team-period and league language without replacing the official guide.
Explains academy/rebuild intent and no-buy/sell-allowed expectations in a base-game pre-save context.
Included transparently as an audited candidate; subtitle retrieval failed, so it supports no operational claim.
Checked: 18 August 2026 against eleven creator-controlled surfaces, three useful video transcripts and a four-query video audit.
Verified team contract: Career + Live Editor · buy/loan-in blocked · sell/loan-out allowed · dialog Save → save-UID JSON.
Lua boundary: team/player records and Save are documented; exact player transaction behavior and bundled global unban are not.
Local-test boundary: no controlled FC 26 Career fixture was available, so this page does not claim a locally executed ban.
Review trigger: Wiki/API/script change, JSON schema publication, current FC 26 screenshots, manifest change or a controlled before/after Career test.