01 / DIRECT ANSWER
Start with the narrowest script that proves the football job
The official FC 26 repository contains 35 top-level Lua scripts: six inspection tools, two CSV exporters, seven event automations, nine player-data edits, seven appearance/unlock files and four Career-wide actions. Do not treat the folder as a one-click mod pack. Match one file to one goal, read its actual loop and defaults, record the game/editor pair, preserve a recovery state and run it once. This audit places one published file on HOLD and eleven behind a BACKUP gate.
Use the current flat `/lua/` source—not reuploads or stale Wiki example paths.
One ID, one squad, every player and every team are different operations.
Version, target, before-state, after-state and recovery close the run.
02 / SOURCE-DERIVED INVENTORY
Thirty-five files split into six football jobs
The categories come from executable behavior in repository snapshot c3bf990, not from filenames alone. Counts are mutually exclusive so every source file has one accountable home.
Reads tables or event names and reports findings without an intentional database write.
Reads Career data and creates or replaces CSV files on the Windows Desktop.
Registers a Career event handler and reapplies a value after documented football boundaries.
Changes attributes, potential, age, retirement, modifier or contract role fields.
Changes head, tattoo, kit or customization availability records.
Deletes players, extends contracts or applies a transfer policy across a broad population.
03 / ORIGINAL DATA TOOL
Filter by job, then inspect the executable scope
The Selection Room runs entirely in this browser. It neither downloads a script nor touches FC 26; it turns the chosen source into a five-gate run receipt.
SCRIPT SELECTION ROOM
Filter the creator’s 35 FC 26 files, inspect blast radius, then build a run receipt before opening Lua Engine.
RUN CONTROL / track_cm_events.lua
CLASSIFICATION LIMIT: this is static source analysis against the current public repository. It does not claim that every branch was executed inside every Career configuration.
04 / FOUR GATES
Risk follows scope and reversibility—not code length
No intentional game-data write found; still verify the output and current context.
Targeted, cosmetic, file-output or event-driven change; preserve a before-state and prove the target.
Broad, destructive or difficult-to-reverse change. Use an isolated recovery slot and narrow the scope first.
Static audit found a blocking defect or unresolved version contract. Do not execute unchanged.
05 / INTENT ROUTING
Choose from the result you need in football
Use list_players, list_transfer_bans, squad diagnostics or the Career event tracker. Preserve the log and change nothing yet.
The two exporters create Desktop files. Season stats are reset at rollover; fixtures additionally use memory offsets.
Fitness, form, morale, sharpness and PAP PlayStyles register callbacks. Re-running can duplicate policies.
Prefer the team-ID scripts only after resolving the ID and target count; do not use an all-player rewrite for convenience.
The downloaded head map contains a live swap example; the tattoo file is held by static audit.
Generated-player deletion, world contracts and all-team bans have the largest and least reversible blast radius.
06 / STATIC SOURCE AUDIT
Five findings change how the files should be used
These are line-level observations and conservative inferences. They do not rewrite the creator’s files or silently convert uncertainty into a “fixed” download.
custom_tattoos_to_playerid.lua`table_count(headmodels_map)` references a name never defined in that file. The intended map appears to be `tattoos_map`, but that repair is an inference and the published file should not be run unchanged.
fix_players_headmodels.luaIts embedded valid-head list says it is current through game v1.6.1. The creator manifest now maps v1.6.6, so the list is not a current-build guarantee.
auto_max_user_team_morale.luaThe immediate Career path writes 100; later event callbacks write 120. A single “max morale” expectation would hide two executable outcomes.
mass_edit_squadrole.luaThe comment says “players in your club,” while the executable loop has no explicit team-ID filter. Its effective population must be proven from career_playercontract, not assumed from prose.
Events Wiki examplesThe Wiki links examples under `/lua/scripts/`, which currently returns 404. The same named files exist in the repository’s flat `/lua/` folder.
Source inspection, version pairing and an isolated test tell you whether it fits this save.
07 / THREE DIFFERENT BADGES
Repository date, game build and editor version answer different questions
Proves which files and lines were classified—not runtime compatibility.
The creator manifest maps executable 1.0.139.20381 to these editor versions.
The head-model fixer’s own data label is older than the current game pair.
NO INVENTED MINIMUM: most files declare no minimum Live Editor version. Their presence in the FC 26 repository is not converted into a fictional “v26.1.0+” badge.
08 / WHERE THE EFFECT LIVES
Runtime state, external files and Career data need different rollback
Console + Live Editor log
Preserve or close logWindows Desktop file
Rename/archive before rerunCurrent Lua runtime
Remove exact ID or restartLoaded table / eligible Career state
Restore values or recovery saveFeature-specific external registry
Use matching manager removalPlayer entity graph
Recovery copy—not “undo”09 / ONE CONTROLLED RUN
Open source first; execute only after the target manifest exists
- 01PAIRRecord FC build and LE_VERSION
Do not use the repository date as a substitute for compatibility.
- 02SOURCEOpen the exact official file
Read constants, defaults, loops, writes, event registration and file output.
- 03TARGETResolve IDs and row count
Write down one player, one team or the explicit global population.
- 04RECOVERYProtect an untouched state
Use a separate Career slot or disposable dataset before broad writes.
- 05EXECUTEF9 → Features → Lua Engine
Open the reviewed file, execute once and preserve the first output.
- 06PROVECheck positive and negative controls
Verify the intended target changed and an excluded target did not.
- 07RELOADTest persistence, then decide
Keep, reverse exact values or abandon the test and restore recovery.
10 / FAILURE ROUTING
The first wrong boundary tells you where to stop
Confirm the official `.lua` file and a fully extracted Live Editor install.
Some files explicitly require an active Career context.
Verify the ID, table population, expected field and reload surface.
Stop re-executing and remove the exact handler or restart clean.
Stop, preserve evidence and restore recovery; do not “counter-script” blindly.
Do not rerun. Return to the before-state and keep the exact source/build receipt.
11 / VIDEO & INTENT AUDIT
Video demand concentrates on opening files and assigning faces
Four searches produced 60 result slots and 32 unique videos. The closest current FC 26 results explain the visual open/execute route or promote third-party face assignment; none supplies an authoritative, complete audit of the creator’s 35 files.
FC26 REALFACES description gives F9 → Lua Engine → File/Open → Execute; no captions.
FC26 FACEMOD SCRIPT promotes external auto_headassign.lua; no captions.
FC25/26 GUIDE caption request returned HTTP 429.
FC25 GUIDE has no caption track and cannot control FC 26 source claims.
No third-party download link is promoted as a substitute for source inspection.
12 / FAQ
Lua script library questions, answered by source scope
01Where are the official FC 26 Lua scripts?+
The current creator repository stores 35 Lua files directly under the /lua folder. This catalog links to those source pages, not mirrors or reuploads.
02Does “official repository” mean every script is safe to run unchanged?+
No. Publication establishes provenance, not fitness for your save or current build. The static audit found an undefined variable, version-locked data and several broad defaults.
03Which script should a beginner try first?+
Use an observation-only file such as print_team_jersey_numbers.lua or small_squad_find.lua on a backed-up Career. Read its target parameter and expected log first.
04How do I execute a Lua file?+
The Lua API v2 Wiki documents Features → Lua Engine → execute. Current FC 26 video descriptions also show F9 → Features → Lua Engine → File/Open → Execute.
05Which scripts are read-only?+
Six catalog entries are classified READ: the two squad diagnostics, player list, transfer-ban list, shirt-number report and Career event tracker. The tracker still registers runtime state.
06Why is a CSV exporter not labelled READ?+
It does not intentionally change the Career database, but it creates or replaces files on the Desktop. The fixtures exporter also reads process memory through fixed offsets.
07Will a database write persist after restarting the game?+
The official Database Editor guidance says only tables stored in Career Mode persist in a Career save. Persistence therefore depends on the table, save action and script—not the .lua extension.
08How do I stop an event automation script?+
Do not blindly clear every handler. Use the events-and-hotkeys guide to identify and remove the exact handler ID, or restart the runtime and verify the policy is gone.
09Why is the tattoo mapper on HOLD?+
Its executable code counts `headmodels_map`, but that variable is not declared in the file. The likely correction cannot be treated as creator-confirmed without an upstream fix.
10Is fix_players_headmodels.lua current for FC 26 v1.6.6?+
The repository contains it, but the file itself labels its embedded list current through v1.6.1. Treat it as version-locked until the list is verified against the running build.
11Can I download Lua scripts from a YouTube description?+
A video can demonstrate intent, but a third-party file can differ from the creator repository. Inspect the source, IDs, defaults and writes before allowing it near a Career save.
12What should I record after running a script?+
Keep the FC/LE pair, source URL and commit, target manifest, before-state, visible or logged result, reload result and recovery decision. The library generates that run receipt locally.
13 / EVIDENCE LEDGER
Primary code for effects; video only for workflow demand
The creator repository, Wiki, manifest and changelog control technical claims. Individual source files control the audit findings. Video metadata contributes user intent and visible route vocabulary only.
Primary 35-file inventory and source provenance.
Creator-owned project identity and current repository tree.
Lua 5.4.6 and the documented Features → Lua Engine execution route.
Table-editing and Career persistence boundary.
Handler lifecycle used by seven automation/tracker files.
Console and log-file evidence contract.
Current game/Live Editor pair: v1.6.6 with v26.3.5–v26.3.6.
Release chronology and current Lua-related additions.
Minimal logging script and event-registration pattern.
Memory-read and multi-file CSV behavior.
Current-season scope and Desktop CSV output.
Primary evidence for the undefined-name HOLD.
Primary evidence for the immediate 100 / event 120 split.
Primary v1.6.1 embedded-list declaration.
Primary destructive threshold and DeletePlayer call.
Primary world-scale policy and explicit Save call.
Description supplies the current open/execute workflow; no caption track.
Current demand for third-party head assignment; no caption track.
Current broad workflow demand; captions returned HTTP 429.
14 / ATOMIC API LABS
Continue from the library to the exact runtime boundary
This Mixed page is the controlled parent for four narrow Support studies. Each lab owns one API entity, its version gate, proof protocol and rollback boundary.