01 / DIRECT ANSWER
How do you force a player into the starting XI?
Create a backup, stay outside FC’s built-in Edit Player screen, press F9 → Features → Players, open the exact player and choose Other. Set Selection Bias to 1000 to ensure that player will play. Keep Position on Pitch at auto for Manager AI placement, or choose a current UI position after bias is above zero. Use Player → Save before clicking Play Match, then verify the actual kickoff XI.
No selection influence. Position on Pitch is inactive.
AI OWNS XIHigher value, higher inclusion chance. No percentage formula exists.
WEIGHTEDThe creator says the selected player will always play.
PLAYER STARTS02 / TWO-FIELD CONTRACT
Inclusion comes first; placement depends on it
0 disables influence. Higher values increase the chance. 1000 is the documented guarantee anchor.
auto leaves placement to Manager AI. Any explicit position needs bias above zero.
Position on Pitch is not a registered-position edit. It changes match placement, not the player’s stored primary/secondary positions, development plan or FC IQ role.
03 / INTERACTIVE SELECTION ROOM
Model one target, the match scope and kickoff proof
Use the local planner to see the bias-position dependency, preserve the creator’s CPU-vs-CPU uncertainty and build a seven-checkpoint proof card. It never accesses FC 26.
No game or Career access
Choose the player. Leave ten decisions alive.
The creator publishes two exact anchors—0 means no bias; 1000 ensures the player will play. The 250 option below is only a synthetic positive test, never a 25% probability.
Position on Pitch cannot take effect while Selection Bias is zero.
04 / DOCUMENTED VALUE ANCHORS
Three states—not a probability calculator
Manager AI uses its normal selection logic.
DOCUMENTEDThe direction is known; numeric odds are not.
NO FORMULACreator wording: the player will always play.
GUARANTEE ANCHORDo not say “500 = 50%.” The documentation identifies 0, a monotonic direction and 1000; it publishes no percentage mapping and does not call 1000 the maximum.
05 / POSITION DEPENDENCY
auto and explicit placement answer different questions
Manager AI still chooses where the player stands.
ISOLATES THE XI TESTUse the exact label exposed by the current dropdown.
SECOND TEST VARIABLEThe official screenshots visibly show auto, GK and LS examples. They do not publish a complete position list, so this guide invents none.
06 / SAVE-BEFORE-MATCH WORKFLOW
The timing gate sits before Play Match
Confirm ID, team and upcoming opponent.
Change one variable on a restored branch.
Apply the Player Editor change.
Do not enter the match first.
Capture XI and actual position.
Re-enter the relevant FC surface to refresh it and save the Career test slot for permanence. The source does not establish how many future fixtures retain the intervention.
07 / MODE & MATCH SCOPE
Two documented uses, one uncertainty, one hard stop
Explicitly named by the creator.
DOCUMENTED USEChoose selected players in the team you are about to face.
DOCUMENTED USECreator says the field is probably ignored.
UNCERTAINOutside Live Editor’s documented scope.
UNSUPPORTED08 / SELECTION BIAS VERSUS FREEZE LINEUP
Choose partial control or own all eleven slots
- One/few guaranteed players
- Manager AI fills remaining places
- Player → Save
- Whole starting eleven frozen
- User owns every slot
- Formation → Save
The Wiki’s “1, 2 or 3 players” wording is an example of partial control—not a documented maximum of three.
09 / ONE-PLAYER A/B TEST
Separate inclusion from position in restored branches
Capture normal XI for this fixture. OVR alone does not predict selection.
RESTORE CHECKPOINTVerify the player starts while Manager AI owns placement.
ACTUAL KICKOFF XIVerify the exact displayed position on a second restored branch.
ONE NEW VARIABLENO LICENSED CURRENT FIXTURE This is a reproducible protocol, not a fabricated guarantee test or lineup screenshot.
10 / MULTIPLE-PLAYER ESCALATION
Add targets one at a time; conflict behavior is undocumented
Identity, save timing, XI and placement.
Restore, save both and capture the complete XI.
Stop when two requested positions collide.
No priority, overflow or duplicate-position rule is documented.
11 / BASE-GAME MANAGER AI
A weaker-looking XI is not automatically a broken XI
EA says less important matches may give weaker players minutes.
EA’s example lets an in-form 80-rated striker start over an out-of-form 83.
Use 1000 only when you deliberately want to override the choice for one player.
Form and importance explain the no-bias control; they do not cancel the creator’s explicit 1000 guarantee.
12 / FOUR DIFFERENT POSITION ENTITIES
“Position” can mean four incompatible things
Primary/secondary identity and development conversion.
Where the biased player appears in the match XI.
Behavior within an in-/out-of-possession tactical shape.
One place in the complete team structure.
13 / FIRST-FAILURE DIAGNOSIS
Route the failed proof before changing another value
Verify player/team/opponent, Player Save, before-Play-Match timing and Player/Manager Career context.
At zero the position is inactive; at auto Manager AI owns placement.
Do not treat this context as the decisive persistence test.
Injury, suspension and squad-absence override behavior is undocumented.
No position conflict or priority resolver is published.
Selection Bias is the wrong ownership model for all eleven.
14 / FRESH VIDEO AUDIT
No current YouTube result proved the complete field chain
Four searches returned 36 rows / 32 unique videos on 17 August 2026. The exact Team Selection Bias query returned zero. Remaining results mixed Career advice, Player Career critique, registered positions, tactics, mod showcases, crashes and entertainment.
No 0 → 1000, auto → position, Save → kickoff proof.
Useful whole-XI contrast; not Bias field evidence.
Career setup, mod showcase, registered position and tactics.
Search noise supports a creator-doc-first evidence order.
EVIDENCE DECISION Creator Wiki controls values, dependency, scope and timing. EA controls base-game selection inputs. Videos define adjacent boundaries only.
15 / FAQ
Starting-XI and Position on Pitch questions
01How do I make a player start in FC 26 with Live Editor?+
Back up the Career, stay outside FC’s built-in Edit Player, press F9 → Features → Players, open the exact player, choose Other and set Selection Bias. The creator says 1000 ensures that player will play. Use Player → Save before clicking Play Match, then verify the actual kickoff XI.
02What does Selection Bias 0 mean?+
Zero means no selection bias. Manager AI owns inclusion, and Position on Pitch cannot take effect at zero.
03Does Selection Bias 1000 guarantee the starting XI?+
The creator documentation says setting 1000 ensures the player will always play. Test the intended fixture after Player Save; the documentation does not say whether injury, suspension or squad absence can be overridden.
04Is Selection Bias 500 a 50% starting chance?+
No percentage formula is published. Higher values mean a higher inclusion chance, but intermediate numbers must not be converted into odds.
05What does Position on Pitch auto mean?+
Auto leaves the player’s match position to Manager AI. It does not disable Selection Bias itself.
06Why does Position on Pitch not work?+
Selection Bias must be greater than zero. Also verify the exact player, current match context, Player Save and that the change was saved before Play Match.
07Does Position on Pitch change the player’s registered position?+
No. It is a match-lineup placement field. Registered position conversion, development plans and FC IQ roles are different systems.
08Can I use Selection Bias in Player Career?+
Yes. The creator explicitly names Player Career as a use case.
09Can I edit the next opponent’s lineup in Manager Career?+
Yes. The creator explicitly recommends Selection Bias for selected players in the next opponent’s starting XI.
10Does Selection Bias work in CPU-versus-CPU matches?+
The creator says it is probably ignored. Preserve that uncertainty and do not rely on it for autonomous CPU-vs-CPU simulation.
11What is the difference between Selection Bias and Freeze Lineup?+
Selection Bias can ensure a few selected players while Manager AI decides the rest. Freeze Lineup belongs to Formation Editor and locks the complete eleven.
12Can I force more than three players?+
The Wiki gives one, two or three only as examples, not a published cap. Add one player at a time because no conflict resolver or priority formula is documented.
16 / EVIDENCE LEDGER
Creator wording owns the intervention; EA owns normal AI
Primary field semantics, 0/1000 anchors, Position dependency, mode caveat and pre-match timing.
Freeze Lineup comparison, team-editor route and Formation Save contract.
Team Selection Bias introduction in Player Editor v26.2.1.
Windows PC, offline product and Career-focused scope.
Mapped FC/Live Editor pair at the research freeze.
Visible Player Editor → Other fields, 0.000 and auto labels.
Visible 1000.000 examples with auto, GK and LS placement.
Creator-linked whole-XI alternative and Formation → Save flow.
Official match-importance and form inputs to base-game lineup selection.
Adjacent base-game team-sheet symptom; not Live Editor authority.
Adjacent team-management boundary; separate from Position on Pitch.
Current opponent-XI, position and return-fixture tracking vocabulary.
Current frustration with AI-selected positions in Player Career.
Persistent strong-player-on-bench intent; historical context only.
Base-game setup context; contains no Selection Bias evidence.
Different editor/mod context; rejected as exact field authority.
Development-plan position conversion, used only to separate entities.
Roles and in/out-of-possession shape, not Position on Pitch.
Audience context only; no Live Editor action proof.
No current licensed kickoff fixture was available. The page does not invent probability percentages, a three-player cap, an exhaustive position list, unavailable-player overrides, CPU-vs-CPU reliability or persistence across future fixtures.