ARTICLE 74MATCHDAY CONTROL / MIXED GUIDE

STAGE THE FIXTURE.
DON’T CONFUSE THE CLOCKS.

Match Setup builds the scene before kickoff: stadium, weather, fixture time and crowd. Gameplay controls belong to a second, live pass: CPU vs CPU, never tired players, unlimited substitutions, match time and score. Separate the passes, prove one change at a time and never mistake a fixture override for a permanent club edit.

STADIUMWEATHERFIXTURE TIMECROWDCPU VS CPULIVE SCOREOFFLINE ONLY

01 / DIRECT ANSWER

Build the match card first. Touch live state second.

Use Miscellaneous Features → Match Setup before entering the fixture. Capture the original card; override one of stadium, weather, fixture time or crowd attendance; enter that exact match and prove the visible result. If you also need CPU vs CPU, unlimited substitutions, stamina, clock or score, open the separate Gameplay group after the match loads and record a second proof.

BEFORE KICKOFFMatch Setup

Venue, atmosphere, presentation and attendance.

INSIDE MATCHGameplay

Control mode, stamina, substitutions, clock and score.

IDENTITYOne fixture

Same Career, competition, teams and scheduled match.

PROOFTwo passes

Never use a live score change to prove a pre-match setting.

02 / THE CRITICAL DISTINCTION

Fixture Time is not Match Time

The creator’s release ledger places them in different feature groups and different releases. That taxonomy is the strongest available contract.

PASS A · v26.1.5PRE-MATCH
20:45Fixture Time

Part of the match presentation prepared before kickoff, beside stadium, weather and crowd.

PROVE → KICKOFF PRESENTATION
≠
PASS B · v26.2.0LIVE STATE
67:24Match Time

Part of the Gameplay group, beside CPU vs CPU, stamina, substitutions and score.

PROVE → IN-MATCH SCOREBOARD

WHY THIS MATTERS: if the in-match clock changes, that does not prove Fixture Time worked. If the evening presentation changes, that does not prove live Match Time is writable.

03 / ORIGINAL LOCAL INSTRUMENT

Plan the atmosphere and live controls as separate passes

Choose a release band and story, enable only the controls you intend to test, then complete the five human gates. The board creates a deterministic call sheet locally; it never connects to FC 26.

LOCAL / ZERO-CONNECTION PLANNER

Match Director Board

Build two separate passes: the match card before kickoff, then optional live gameplay controls after the match loads.

01 / RELEASE BAND
02 / MATCH STORY
PASS ABefore kickoff
v26.1.5
PASS BInside match
v26.2.0
03 / FIVE HUMAN GATES
NO GAME CONNECTIONNO SAVE WRITE · NO INVENTED ENUMS · TWO PASSES, TWO PROOFS

NO INVENTED RANGES: enter the exact label or value visible in your installed UI. The official release notes name the controls but do not publish accepted stadium IDs, weather enums, attendance bounds, clock limits or score validation.

04 / RELEASE GATE

Two additions, one current workflow

22 OCT 2025v26.1.5Match Setup arrives
  • Override Stadium
  • Override Weather
  • Override Fixture Time
  • Override Crowd Attendance
CREATOR POST ↗
19 NOV 2025v26.2.0Gameplay arrives
  • CPU vs CPU
  • Never tired players
  • Unlimited subs
  • Match time & score
CREATOR POST ↗
CHECKED 18 AUG 2026v26.3.5–v26.3.6Both groups are current

FC 26 v1.6.6 build 1.0.139.20381 maps to Live Editor v26.3.5–v26.3.6. Public/Bronze is v26.3.5; Silver is v26.3.6.

LIVE MANIFEST ↗

05 / PASS A · BEFORE KICKOFF

Four controls direct the match card

01Stadium

Choose a venue for this fixture. Record the original venue and prove the tunnel, pitch or establishing shot—not a club database field.

ANCHOR → FINALS · GROUND-SHARES · RTG
02Weather

Current video shows familiar visible options including clear, rain, snow and overcast. The exact UI in your build controls the choice.

ANCHOR → WINTER · DRAMA · REALISM
03Fixture Time

Prepare the kickoff presentation before loading the match. Do not confuse it with the live clock in Gameplay.

ANCHOR → NIGHT GAME · BROADCAST
04Crowd attendance

Create empty, reduced or full-stand stories using only the exact values exposed by your version.

ANCHOR → RTG · SANCTION · SELLOUT

06 / PASS B · INSIDE MATCH

Five live controls belong on the other side of kickoff

01CPU / CPU

Watch the match as a spectator or tactical observer.

02NEVER TIRED

Control stamina behavior during the runtime test.

03UNLIMITED SUBS

Change the substitution constraint for the active match.

04MATCH TIME

Adjust live clock state; not the scheduled fixture presentation.

05MATCH SCORE

Adjust live score state; not future-fixture match-fixing.

COMPETITION BOUNDARY: the changelog confirms feature presence, not a league-by-league rules matrix. Verify substitutions, stoppage behavior and controller ownership in the exact offline competition you intend to use.

07 / CONTROLLED MATCH PROTOCOL

One fixture, two passes, seven checkpoints

  1. 01
    PAIRRecord the exact game/editor pair

    Do not diagnose Match Setup on an unmapped or assumed build.

  2. 02
    CHECKPOINTUse an untouched save or repeatable fixture

    Keep the original fixture available for a clean comparison.

  3. 03
    BASELINECapture the original match card

    Teams, competition, stadium, weather, fixture presentation and crowd.

  4. 04
    PASS AChange one Match Setup condition

    Enter the same fixture and capture the first visible result.

  5. 05
    CLEAN RETURNRelaunch from the checkpoint

    Separate pre-match evidence from live-state evidence.

  6. 06
    PASS BEnable one Gameplay control

    Only on v26.2.0+; prove it inside the active match.

  7. 07
    ROLLBACKClose, relaunch clean and compare

    Confirm the untouched checkpoint restores the baseline.

08 / HONEST PERSISTENCE BOUNDARY

Do not promise that a fixture override rewrites the club

Public creator sources name the controls but do not document whether every value survives menu changes, match exit, save/reload or a tool restart. The safest current model is runtime/current-fixture state until directly proven.

CONFIRMEDFeature presence and grouping

Two release notes establish the names, versions and pre-match/live split.

REPORTEDClub stadium did not save

Issue #25 describes Atlanta → Eastpoint Arena, remains open and has zero comments.

NOT ESTABLISHEDUniversal persistence rule

The issue does not identify Match Setup, and no maintainer answer connects the entities.

EDITORIAL RULE: a user report is evidence that confusion exists, not evidence for a fix. This page therefore teaches an observable fixture proof and a clean checkpoint instead of claiming “press Save” or “it is permanent.”

09 / NEIGHBOURING FEATURES

Same football vocabulary, different data owners

10 / AUDIENCE ANCHORS

What match directors actually build

01 / CREATOREuropean night

Deliberate stadium, evening fixture, rain and full stand for a thumbnail-ready Career episode.

PASS A ONLY
02 / STORYTELLERRoad to Glory

Small-ground feeling and reduced attendance early in the save; bigger atmosphere as the club rises.

PASS A ONLY
03 / SPECTATORCPU showcase

Stage the venue and weather, then switch to CPU vs CPU after the match loads.

PASS A → PASS B
04 / TESTERRepeatable scenario

Same fixture, one changed condition, one screenshot, clean relaunch and baseline comparison.

CONTROL RUN
05 / CHALLENGESubstitution lab

Use unlimited subs in a known offline competition and record where native rules still appear.

PASS B ONLY
06 / DIRECTORLate-match scene

Use the live clock and score as runtime controls without calling them fixture scheduling or match-fixing.

PASS B ONLY

11 / FIRST FAILED CHECKPOINT

Route the symptom by owner and moment

OPTION MISSINGRelease / pair

Match Setup requires v26.1.5+; Gameplay requires v26.2.0+. Check the full executable build, not the marketing title.

VENUE DID NOT CHANGEFixture vs team

Confirm Match Setup, intended fixture and pre-kickoff timing. Do not stack a club stadium edit.

WEATHER DID NOT CHANGEExact UI value

Return to baseline, choose one visible value and re-enter the same fixture.

CLOCK LOOKS WRONGWhich clock?

Fixture Time is pre-match presentation; Match Time is the active-match state.

SCORE REVERTEDRuntime boundary

Record when it reverted. Do not infer that live score must become a future Career result.

STADIUM WILL NOT SAVEPersistence ambiguity

State whether you changed Match Setup or the team entity. Issue #25 has no confirmed fix.

12 / VIDEO EVIDENCE AUDIT

Interface evidence is useful; the complete proof chain is missing

Six exact searches produced 76 result slots and 70 unique videos. Results were dominated by Mod Manager, FC Editor Tool, general Career videos, repacks and unrelated tutorials. No current caption-backed video completed baseline → Match Setup → one-fixture proof → live pass → clean rollback.

13 / QUICK QUESTIONS

FC 26 Match Setup FAQ

01What can FC 26 Live Editor Match Setup override?

The official v26.1.5 release notes name four controls: Stadium, Weather, Fixture Time and Crowd Attendance. They appear under Miscellaneous Features → Match Setup.

02Is CPU vs CPU part of Match Setup?

Not in the release ledger. CPU vs CPU belongs to the Gameplay group introduced in v26.2.0, alongside never tired players, unlimited substitutions, match time and score. This guide connects the workflow but preserves the product boundary.

03When should I change stadium, weather, fixture time or crowd?

Treat them as pre-kickoff conditions: record the fixture baseline, select one override, then enter that fixture and prove the result. Public creator sources do not document one universal apply/reload sequence for every current build.

04What is the difference between Fixture Time and Match Time?

Fixture Time is a v26.1.5 Match Setup condition before kickoff. Match Time is a v26.2.0 Gameplay control for live match state. They are separate controls and should be tested in separate passes.

05Can I make an empty-stadium match?

The creator README lists “No crowd during matches,” and v26.1.5 names Crowd Attendance. Use the exact value exposed by your current interface. A legacy FC 25 video shows a 0–100 convention, but that does not prove the current FC 26 numeric contract.

06Which weather choices are available?

A current captioned interface walkthrough visibly cycles through Clear, Partly Clear, Rainy, Snowy and Overcast. Because the official changelog does not publish an enum, use the exact labels shown in your installed version and do not treat this observed list as an API contract.

07Does a Match Setup stadium override permanently change my club stadium?

No current creator source says it does. Match Setup is a fixture-level miscellaneous control. Editing a team’s stadium is a different entity; issue #25 reports that kind of change not saving, but has no maintainer answer and cannot define Match Setup persistence.

08Why did my stadium or weather not change?

First verify the full game/editor pair, the intended fixture and whether you changed the pre-match Match Setup control rather than a team field or live Gameplay control. Return to a clean baseline and test one variable before adding another.

09Can I set the match score before kickoff?

The official score control is listed under v26.2.0 Gameplay, not v26.1.5 Match Setup. Match-fixing an upcoming Career fixture is another feature entirely and has its own workflow.

10What does CPU vs CPU do?

It is the creator-named v26.2.0 Gameplay option for a CPU-controlled match. Current video walkthroughs show it in the live gameplay group; they do not document every competition or controller edge case.

11Can I make unlimited substitutions?

v26.2.0 officially adds unlimited subs under Gameplay. Use it only in an offline controlled match and verify behavior in the exact competition because no public creator source publishes a competition-by-competition matrix.

12Are Match Setup changes saved to Career Mode?

Persistence is not documented precisely enough to promise save-level permanence. Treat the controls as runtime/current-fixture overrides until a creator source says otherwise; keep an untouched save or checkpoint and prove the same fixture after relaunch.

13Can I use these controls online?

No. The official repository says the anticheat bypass is for offline use only. This guide excludes FUT, Clubs and all connected competition.

14Which version do I need?

Match Setup begins in v26.1.5; the live Gameplay group begins in v26.2.0. On 18 August 2026 the live manifest maps FC 26 v1.6.6 build 1.0.139.20381 to Live Editor v26.3.5–v26.3.6, so both groups are present in the current mapped releases.

15What should I include in a bug report?

Record the complete FC26.exe build, Live Editor version, Career/competition and fixture, exact control and visible value, whether it was changed before or during the match, the first failed observable result, relaunch outcome and whether a clean baseline reproduces it.

14 / EVIDENCE LEDGER

Sources and confidence boundaries

Creator-owned current sources control features, releases, compatibility and offline scope. Videos establish visible interface vocabulary and audience jobs. The issue is explicitly a report, not a confirmed product rule.

01
Official FC 26 changelog

Primary feature ledger: v26.1.5 Match Setup and v26.2.0 Gameplay are separate releases and groups.

02
Official v26.1.5 creator post

Creator-owned release page naming stadium, weather, fixture time and crowd attendance.

03
Official v26.2.0 creator post

Creator-owned release page naming CPU vs CPU, never tired, unlimited subs, match time and score.

04
Current version manifest

Current game build, compatible Live Editor interval and Public/Bronze/Silver access split.

05
Official repository README

Confirms no-crowd capability, Live Editor scope and offline-only anticheat boundary.

06
Official Getting Started Wiki

Creator-owned launch and F9 overlay context; it does not publish Match Setup apply semantics.

07
Official issue #25

Open zero-comment report about a club-stadium change not saving; used only to expose entity/persistence ambiguity.

08
Current FC 26 combined walkthrough

Caption-backed visual evidence for Career Match Setup and separate live Gameplay time/score controls.

09
Current FC 26 interface walkthrough

Caption-backed visual evidence for CPU vs CPU and Match Setup navigation; translated wording is not treated as a product contract.

10
Current FC 26 Match Setup walkthrough

Caption-backed visible weather labels and Match Settings navigation; machine translation is treated cautiously.

11
Current FC 26 feature overview

Audience vocabulary and stadium-editing demand; does not settle fixture versus team persistence.

12
Historical FC 25 complete tutorial

Legacy audience evidence for empty/full crowd storytelling; never used to define current FC 26 ranges.

RETURN / FEATURE ATLASChoose the next FC 26 Live Editor operation

Compare entity, scope, persistence and source strength before changing another layer.