01 / DIRECT ANSWER
Lua is the programmable layer behind repeatable FC 26 jobs
Press F9, open Features → Lua Engine, load the reviewed `.lua` file and execute it once. Before that click, record LE_VERSION and the FC build, identify one target and one excluded control, classify the effect as log, file, runtime, Career, network or process memory, and decide the exact proof and recovery. API v2 is the current documentation path; the old API page warns that its functions may stop working.
Creator-published engine version.
Lua Engine → open → execute.
Global runtime version string.
Not an online or console workflow.
02 / ORIGINAL ROUTING TOOL
Choose the football mission before the API primitive
Mission Control runs only in this browser: it makes no game connection, sends no request, accepts no memory address and executes no Lua. It converts eight common jobs into a version gate, owner, proof and recovery receipt.
01 / FOOTBALL JOB
02 / INSTALLED EDITOR
The version gate changes the route—not the documentation.Official Lua source + Lua Engine
Best first route when the job already exists in the creator repository.
- OWNER
- One reviewed top-level .lua file
- EFFECT
- Depends on source: log, file, runtime or Career rows
- VERSION GATE
- Current repository snapshot
- PROOF
- Match the target population, run once and compare one excluded control.
- RECOVERY
- Use the file passport: remove handler, restore value or return to recovery save.
03 / RUN CONTROL
Close four gates before execution04 / LOCAL RECEIPT
PREFLIGHTFC 26 LUA MISSION CONTROL MISSION: Choose a ready script VERSION: public/bronze v26.3.5 PRIMITIVE: Official Lua source + Lua Engine OWNER: One reviewed top-level .lua file EFFECT: Depends on source: log, file, runtime or Career rows RISK: CONTROL VERSION GATE: Current repository snapshot PROOF: Match the target population, run once and compare one excluded control. RECOVERY: Use the file passport: remove handler, restore value or return to recovery save. PREFLIGHT: 0/4 DECISION: PREFLIGHT
READY MEANS ROUTED: it confirms that the plan is accountable, not that an unknown value, address, server or third-party file is safe.
03 / SYSTEM MODEL
A script crosses four accountable boundaries
The Lua Engine is not one universal editor action. Source, runtime object, effect owner and proof are separate entities; confusing any pair creates the familiar “executed but nothing happened” failure.
Exact creator code, constants and target loop.
Loaded inside the running Live Editor context.
DB, event, file, HTTP, manager or memory primitive.
Log, output, runtime, save, remote or process state.
If a purpose-built manager owns the job, prefer it to lower-level table or address work. A smaller surface gives the proof and recovery a clearer owner.
A void return or success banner is not evidence. Inspect the output file, named row, response fields, runtime getter or reloaded save that owns the result.
04 / DRMAX CLUSTER GATEWAYS
Two Mixed pages carry every narrow Lua question
This Target page classifies the system. The Mixed gateways own implementation detail and lead one click deeper to atomic events, HTTP, Memory and Gameplay pages without duplicating their complete procedures here.
Choose by football job, inspect source scope, version badge, persistence and rollback; continue to the exact API lab from one controlled map.
Separate the official 16-field season-stat exporter from the 10-field per-competition fixture exporter and validate the first output locally.
05 / SOURCE-AUDITED API SURFACE
Seventy-two documented calls sit behind eleven published surfaces
The count includes methods/functions linked from the current API v2 index plus the eight HTTPRequest setters; it excludes fields, enums, old v1 functions and undocumented database helpers. The public Wiki shows 72 callable entries, 23 object/class fields and one global version variable across these surfaces.
Installed editor string
Read-onlyConsole + logs folder
Read-onlyCurrent Lua runtime
Callback-definedRemote + local follow-up
ExternalCurrent FC process
Expert / crash boundarySave-UID registry
Career extensionLoaded Aardvark DB / CSV
Runtime/configRuntime + JSON evidence
RuntimeIn-game loc strings
Until restartCareer extension JSON
Load / SaveLegacy path → output
v26.3.6VISIBLE DOCUMENTATION GAP: the v2 index promises improved database-operation performance but does not link a complete database-object contract. Current scripts visibly use LE.db; unknown helpers stay outside the counted surface instead of being invented.
06 / SIX EFFECT LANES
Persistence decides the rollback—not the script filename
Two short scripts can have completely different blast radii. Classify where the result lives before choosing the recovery action.
Logs / no state mutation
No “success” inference from silenceExternal file
Protect first output; export is not importCurrent process / match
Remove handler or restore captured baselineLoaded Career or extension JSON
Named recovery save + reload proofExternal service
Remote effects may be irreversibleBuild-scoped process memory
Invalid provenance is a stop, not a guessRead/log or reversible local output with an exact receipt.
Runtime, file, remote or Career effect needs a before-state.
Broad delete, raw memory or unsupported version evidence stops the run.
07 / FIRST CONTROLLED RUN
Seven steps turn Execute into a reproducible experiment
- 01PAIRRecord FC build + LE_VERSION
Current build 1.0.139.20381 maps to Live Editor v26.3.5–v26.3.6.
- 02SOURCEOpen the exact official file or v2 page
Do not copy code from a video description or stale v1 example without source review.
- 03TARGETName one included and one excluded object
Player ID, team ID, table row, event name, host, file or documented runtime path.
- 04OWNERClassify where the effect lives
Log, external file, runtime, Career/extension, network or process memory.
- 05RECOVERYProtect the before-state
Capture a value, preserve the first file, save a separate slot or stop if no recovery exists.
- 06EXECUTERun once and preserve the first signal
Do not click repeatedly while an event handler or remote effect may still be active.
- 07PROVERead the owner, reload when relevant
Verify the intended target changed, the excluded control did not and recovery still works.
08 / API GENERATION CONTROL
Old v1 names are reference material—not the default path
The creator’s old page says “switch to Lua API v2,” warns that its listed functions may soon stop working and states Cheat Engine Lua scripts will not work. Open issue #27 shows why that boundary matters: a current FC 26 user found old transfer-budget names nil or ineffective.
- Flat helper names
- Functions explicitly marked at risk of removal
- Cheat Engine scripts incompatible
- Stale names can be nil
- Object-oriented surfaces
- Improved database operations
- Events and native HTTP
- LE_VERSION for runtime pairing
Check the installed version, current v2 documentation and official source. If the contract remains absent, log the gap instead of publishing executable speculation.
09 / VERSION TIMELINE
The engine, gameplay API and hotkey/memory controls arrived separately
“Lua support” is not one timeless feature badge. The changelog establishes three different gates, while the manifest decides which editor version the user actually has.
First working release lists Lua Engine.
Gameplay Attribulator joins the API.
Lua hotkey assignment, three Memory calls and two Legacy File functions.
FC v1.6.6 · executable 1.0.139.20381 accepts both.
10 / FAILURE ROUTING
Stop at the first broken boundary
Do not answer a missing file, nil function, absent output and crash with the same shotgun fix. Each symptom points to a different owner.
Confirm a complete `.lua` file from the creator repository and a fully extracted tool folder.
Check API v2 first. Issue #27 shows current FC 26 users can hit stale v1 names.
A script message does not prove the file path, row, remote response or persistence owner.
List handlers, remove the exact ID or restart before executing the file again.
Stop. Preserve the log and restore recovery; do not counter-script a broad write blindly.
Do not rerun. Record version, exact call, source line and first error before restoring.
11 / VIDEO & INTENT AUDIT
Videos show open/execute demand—not the API contract
Six fresh YouTube searches returned 90 real result slots and 44 unique video IDs. Results cluster around opening Lua files, assigning faces, broad Live Editor showcases, legacy FC 25 workflows and unrelated mod/install content. No video documents the complete current v2 object map, 72-call count, version gates, six effect owners and rollback model.
6 queries × 15 results
after deduplication
creator docs remain primary
7TxfMEFFEag / current FC 26Description supplies F9 → Features → Lua Engine → File/Open → Execute; no API lifecycle proof.
G605TbnxnyQ / current v26.3.5 titleCaptions express demand for custom scripts; its broad “everything updates live” claim is rejected.
KNo-TidZ4MU / FC 25Focused Lua workflow demand only; no caption track and no current API authority.
Search pollutionRepack/no-ban claims, Cheat Engine, FIFA Editor Tool, generic Lua and online-cheat material were excluded.
12 / FAQ
Lua Engine questions, routed to an accountable owner
01What Lua version does FC 26 Live Editor use?+
The creator Wiki identifies Lua 5.4.6 as the scripting language used by the Live Editor engine.
02Where do I run a Lua script?+
Open the Live Editor overlay, then use Features → Lua Engine → execute. Current workflow videos also show the visual File/Open route, but the creator Wiki controls the product path.
03Can Cheat Engine Lua scripts run in Live Editor?+
Do not assume so. The creator’s legacy API page explicitly says Lua scripts created for Cheat Engine will not work.
04Should I use API v1 or API v2?+
Start with API v2. The old page says to switch to v2 and warns that its listed functions may stop working; open issue #27 demonstrates the practical stale-name risk.
05How do I check the installed Live Editor version in a script?+
Read the global LE_VERSION variable. It contains the running Live Editor version string. Pair it with the exact FC executable build before testing version-sensitive code.
06Are all API v2 calls safe?+
No. “Documented” describes provenance, not blast radius. Calls range from logging to remote requests, Career writes and raw process-memory patches.
07Does Execute success prove the script worked?+
No. Issue #22 records a user seeing code success without locating the expected CSV. Prove the actual owner: log line, file, row, remote response, runtime value or reload result.
08How many current official Lua scripts are public?+
The creator repository snapshot from 10 August 2026 contains 35 top-level Lua files. The Script Library classifies every file by job, effect and rollback risk.
09Can I bind a Lua script to a hotkey?+
The current changelog adds Lua-script hotkey assignment in v26.3.6. The public/bronze manifest is v26.3.5, so do not present that control as universal yet.
10Does exporting JSON or CSV make a change persistent?+
No. Export proves an output file exists. It does not imply an import method, automatic load order or Career-save ownership.
11When should I use the Memory API?+
Only when a higher-level manager, database object or documented script cannot own the task and you have current-build address provenance. Start read-only and treat invalid evidence as a stop.
12Is Lua supported online or on console?+
This guide covers the Windows PC Live Editor and offline use. The creator README describes the anticheat bypass as offline-only; do not carry this workflow into online modes or console.
13 / EVIDENCE LEDGER
Creator sources control product facts; videos control intent only
Every technical claim is tied to the official repository, Wiki, changelog, manifest or issue tracker. Issue reports prove observed symptoms, not universal fixes. Video content is used only for audience language and visual route demand.
Lua 5.4.6, execute route, v2 improvements, LE_VERSION and linked object map.
PC/offline product boundary and custom-engine definition.
Current 35-file public script corpus.
Lua Engine v26.1.0, Attribulator v26.2.2 and v26.3.6 additions.
Current public/bronze v26.3.5, silver v26.3.6 and game-build pairing.
Explicit v2 migration warning and Cheat Engine incompatibility.
Five log-level methods and logs-folder owner.
Four handler functions, two event families and callback boundary.
Request-send-response chain.
Current 22-method low-level surface.
Eight manager methods and persistence Save.
Seven loaded-config get/set/export methods.
Nine typed runtime/export methods.
Two real-time string methods and restart boundary.
Load/add/remove/save lifecycle.
Two v26.3.6 existence/export functions.
Current FC 26 evidence that old API names can be nil or ineffective.
User intent and proof gap after an Execute success message.
Real bad-argument/undefined-variable evidence; no speculative fix adopted.
F9 → Lua Engine → File/Open → Execute vocabulary only.
Audience desire for custom scripts; broad instant-update claims rejected.