FC 26 Gameplay Attribulator: Lua API, Paths & Test Lab

01 / DIRECT ANSWER

Use the Attribulator as a runtime experiment—not a mystery preset dump

The manager can shorten the feedback loop because the creator says a changed value can be tested by restarting the match instead of FC 26. That does not explain every variable. The repeatable unit is one path, one typed baseline, one candidate, fixed match conditions and one restoration record.

API SURFACE9 methods

One export, four setters, one type inspector and three typed getters.

CREATOR WORKFLOWRestart match

Re-enter the match after a change; a whole-game restart is not the stated loop.

EVIDENCE LIMIT2 exact paths

Only float ball radius and integer track-back duration have complete examples.

02 / ENTITY MAP

Separate FET source groups, runtime roots and export names

The Wiki names three browsable source-group locations, shows two runtime-root forms and lists five export database names. They are related labels, but the documentation does not publish a universal path-conversion rule.

01FET SOURCE

Gameplay / PreMatch / PerksFifa/Attribulator/…/groups

Browse candidate definitions and schema names.

→

02RUNTIME

AttribDBRuntime_…gameplayattribdb · simulation

Two roots are explicit in the typed float example.

→

03EXPORT

Five DB namesgameplay · prematch · perks · simulation · penta

Listed in the parameter table, with a signature mismatch.

03 / ORIGINAL EXPERIMENT TOOL

Build a one-variable match test from two exact creator examples

The local board only exposes the two paths whose type and sample output are published. It calculates a candidate delta, holds the setter until four human gates are checked and exports observe, apply and restore drafts with a test receipt.

LOCAL LAB / TWO CREATOR-DOCUMENTED PATHS

ONE-VARIABLE MATCH BOARD

Turn one typed runtime value into a baseline, candidate and restoration receipt. Nothing on this page connects to FC 26.

BASELINE4MATCHES

CANDIDATE4MATCHES

ONE VARIABLESoccerball radiusAttribDBRuntime_gameplayattribdb

01 / SELECT A DOCUMENTED PATH

02 / RUNTIME DATABASE

The creator says realistic gameplay may require the simulation runtime root.

EXACT RUNTIME PATHAttribDBRuntime_gameplayattribdb/gp_physics/gp_physics_soccerball/Soccerball_Radius

EXPECTED TYPEfloat

03 / OBSERVED BASELINEThe Wiki prints 0.365 for this exact path. Replace it with your live read.04 / ONE CANDIDATELab input range 0.2–0.6; not an official safety limit.

05 / REPEAT COUNT PER CONDITION

THREE-SCRIPT REVIEW

01 / OBSERVEREAD FIRST

local p = "AttribDBRuntime_gameplayattribdb/gp_physics/gp_physics_soccerball/Soccerball_Radius"
print(LE.gameplay_attribulator_manager:GetVarType(p))
print(LE.gameplay_attribulator_manager:GetFloatValue(p))

02 / CANDIDATEONE CHANGE

local p = "AttribDBRuntime_gameplayattribdb/gp_physics/gp_physics_soccerball/Soccerball_Radius"
LE.gameplay_attribulator_manager:SetFloatValue(p, 0.38)

03 / RESTORESAME SETTER

local p = "AttribDBRuntime_gameplayattribdb/gp_physics/gp_physics_soccerball/Soccerball_Radius"
LE.gameplay_attribulator_manager:SetFloatValue(p, 0.365) -- observed baseline

NO SAFETY CLAIM: the board’s input limits are conservative UI guardrails, not creator-published valid ranges. It cannot prove a variable’s meaning, valid domain, match-load timing or compatibility with another gameplay mod.

04 / NINE-METHOD SURFACE

Reads and setters are typed; no setter returns a receipt

ROLEMETHODRETURNCONTRACT NOTE

EXPORTSaveToFilevoid

JSON snapshot; declaration/parameter mismatch

AUTO SETSetVarvoid

String input; type auto-detection; documented as slower

TYPED SETSetFloatValuevoid

float

TYPED SETSetIntValuevoid

int

TYPED SETSetBoolValuevoid

bool

INSPECTGetVarTypestring

Example outputs float and __int32

TYPED GETGetFloatValuefloat

Exact soccer-ball example

TYPED GETGetIntValueint

Exact track-back example

TYPED GETGetBoolValuebool

No example path published

VOID IS A BOUNDARY: a setter completing without an error does not prove that the path, type, candidate or perceived football outcome was correct. Read back the same typed path and preserve a match comparison.

05 / TYPE-SAFE WORKFLOW

Ask GetVarType before choosing the getter and setter

01INSPECTGetVarType(path)

The examples establish float and __int32, not a complete enum.

→

02READGetFloat / GetInt / GetBool

Capture the live value from the exact root and path.

→

03CHANGEMatching typed setter

Avoid string coercion when the type is already known.

→

04VERIFYRead back + match

Restore with the same setter after the condition.

GENERIC FALLBACKSetVar(path, string)

The creator says it detects type automatically and may be slower. Convenience does not remove the need to inspect and record the type first.

06 / TWO OFFICIAL FIXTURES

Only two complete path-and-output examples are published

FLOAT / PHYSICS0.365

Soccerball_Radius

AttribDBRuntime_gameplayattribdb/gp_physics/gp_physics_soccerball/Soccerball_Radius

The Wiki’s getter prints 0.365 and its setter example changes the value to 3.0. The large sample demonstrates the call, not a realism recommendation.

REALISTIC GAMEPLAY NOTE → SIMULATION MAY BE REQUIRED

INT / ASSISTANCE90

TrackBackAssistance_MaxAssistanceDuration

AttribDBRuntime_gameplayattribdb/gp_ballhandler/gp_ballhandler_freemove/TrackBackAssistance_MaxAssistanceDuration

The Wiki’s type call prints __int32; the typed getter prints 90. No unit or valid range is stated.

NO SIMULATION-ROOT EXAMPLE PUBLISHED

07 / DATABASE ROUTING

Five names are export choices; three source groups are visible in FET

01gameplayattribdb

Gameplay source group

02prematchattribdb

PreMatch source group

03perksattribdb

Perks source group

04simulation

Alternative named in realistic-gameplay note

05penta

Listed export name; no example

DO NOT INFER A ROOT: the presence of a db_name in the export table does not, by itself, prove the exact runtime prefix, internal tree or valid variables for that database.

08 / JSON EXPORT

SaveToFile is useful evidence, but its two-argument contract is unresolved

DECLARATIONSaveToFile(string filepath)

One parameter is shown. With no filepath, the example writes the gameplay database to the default Live Editor folder.

≠

PARAMETER TABLEfilepath, db_name

A second string is listed with five allowed names, but no matching declaration or call example is published.

DOCUMENTED DEFAULTC:\FC 26 Live Editor\gameplayattribdb.json

Keep the JSON as an evidence snapshot. The Wiki documents no import method, autoload order, overwrite behavior or persistence guarantee.

09 / CONTROLLED MATCH PROTOCOL

Eight steps keep causality visible

01
PAIRRecord the exact FC build and Live Editor version
Current manifest: FC 26 v1.6.6 build 1.0.139.20381 with LE v26.3.5–v26.3.6.
02
ISOLATEChoose one gameplay-mod configuration
Do not change Mod Manager order, sliders and an Attribulator value in the same condition.
03
PATHSelect one reviewed FET variable and runtime root
Do not paste a historical FIFA path without current type proof.
04
BASELINERead type and live value
Record the getter output before the first setter call.
05
FIX CONDITIONSLock teams, difficulty, weather and controller side
Use the same observation window in every match.
06
CANDIDATEApply one small, reviewable change
Read it back; a void setter is not its own verification.
07
REPLAYRestart the match and repeat both conditions
Use multiple matches because one football sequence is noisy evidence.
08
RESTOREWrite the observed baseline and restart again
Reproduce the baseline before accepting or stacking a second change.

10 / AUDIENCE OUTCOME MAP

Measure football outcomes without pretending to know the hidden variable

Current gameplay videos cluster around the same desired outcomes: tempo, passing, defensive shape, player weight, keepers, contact and weather. Use those as observation categories—not as proof that any unpublished path controls them.

01TEMPO

Possession sequence duration · transition count

02PASSING

Completion under pressure · backward/forward choice

03DEFENDING

Line shape · engagement moment · recovery run

04PHYSICS

Ball travel · bounce · contact outcome

05KEEPERS

Catch/parry/rebound distribution

06WEATHER

Same action in dry vs wet condition

METHOD, NOT MAGIC: the creator-linked Gameplay Lab itself shows uncertainty, non-working attempts and competing explanations. A descriptive variable name is a starting hypothesis; repeated controlled behavior is stronger evidence.

11 / DOCUMENTATION AUDIT

Six unknowns must stay visible

SAVE SIGNATURE

The declaration lists filepath only, while the parameter table adds db_name.

NO DB-NAME CALL

No example demonstrates selecting prematch, perks, simulation or penta during export.

NO BOOL FIXTURE

SetBoolValue and GetBoolValue have empty example blocks.

NO FAILURE CONTRACT

The page defines no missing-path error, sentinel, exception or success return for setters.

NO SAFE RANGES

The creator documents two sample values, not universal minimums, maximums or semantic guarantees.

NO IMPORT LIFECYCLE

JSON export is documented; automatic reload, import order and persistence are not.

12 / FAILURE ROUTING

The first mismatch decides where the experiment stops

TYPE DIFFERSWrong path or build

Do not coerce the value. Re-open the current source and record the exact runtime root.

GETTER FAILSNo baseline

Do not call a setter. Preserve the error, path, build and Live Editor version.

READ-BACK DIFFERSSetter not proven

Stop before the match and restore from the observed value if possible.

NO MATCH EFFECTHypothesis not supported

Check load timing and root; do not multiply candidate magnitude blindly.

MIXED RESULTSFootball variance

Add repeated matches and narrower observations before adding variables.

RESTORE NOT PROVENEnd experiment

Restart the match or game, remove the script and return to a known configuration.

13 / VIDEO & INTENT AUDIT

Gameplay demand is strong; exact Attribulator coverage is absent

Six YouTube searches produced 30 result slots and 30 unique videos. Four exact Attribulator queries returned no results; broad searches surfaced Lua execution, commercial gameplay mods and slider sets. Five current gameplay videos were transcribed locally, but none documents the nine-method API, runtime roots or typed restoration loop.

30RESULT SLOTS

05NEW TRANSCRIPTS

AUDIENCE ANCHORS: ball physics, passing weight, CPU shape, defending, keepers, player movement and repeat testing.

ENTITY MISMATCH: in-game sliders and Mod Manager packages are not GameplayAttribulatorManager calls.

API AUTHORITY: creator Wiki, changelog, manifest and Wiki history.

14 / FAQ

Gameplay Attribulator questions answered at the evidence boundary

01What is Gameplay Attribulator in FC 26 Live Editor?

It is a fieldless Lua API v2 manager added in v26.2.2 for reading, changing and exporting gameplay-related attribulator databases at runtime.

02How many methods are documented?

Nine: SaveToFile, four setters, GetVarType and three typed getters.

03Which content groups are exposed?

The Wiki names Fifa/Attribulator/Gameplay/groups, Fifa/Attribulator/PreMatch/groups and Fifa/Attribulator/Perks/groups in FET.

04Which export database names are listed?

gameplayattribdb, prematchattribdb, perksattribdb, simulation and penta. The SaveToFile declaration and parameter table disagree about the second argument, so this page does not invent a selection call.

05Should I use SetVar or a typed setter?

Use GetVarType first and prefer the matching typed getter/setter when known. The creator says SetVar auto-detects type but may be slower and takes the new value as a string.

06What does GetVarType return?

For the two official examples it prints float and __int32. The Wiki does not publish a complete type-string enum.

07Does a setter return success?

No documented setter returns a value. A non-crash therefore is not a success receipt; read back the same typed path and test the match outcome.

08Do I restart FC 26 after each change?

The creator says testing can be done by restarting the match rather than the whole game. The exact moment for every variable is not separately documented.

09When should I use AttribDBRuntime_simulation?

The Wiki says realistic gameplay may require simulation instead of gameplayattribdb for its soccer-ball example. It does not publish a universal rule for every path.

10Does SaveToFile make the change permanent?

The Wiki documents JSON export only. It does not document automatic import, autoload or Career-save persistence, so do not treat the file as a persistence guarantee.

11Can an old FIFA 23 finding be pasted into FC 26?

Treat it as a hypothesis only. The creator links the older Gameplay Lab for learning, while current paths, types, build and match behavior still need FC 26 validation.

12How do I roll back a test?

Capture the typed live baseline before setting anything, restore it with the same typed setter, restart the match and reproduce the baseline condition.

15 / EVIDENCE LEDGER

Official sources define the API; community sources define questions

Product claims come from the creator’s Wiki, changelog, manifest and repository. The older Gameplay Lab and current videos reveal hypotheses and desired outcomes, but they do not override current FC 26 paths, types or version evidence.

Gameplay Attribulator Wiki

Primary nine-method contract, source groups, runtime examples and match-restart claim.

↗02

Gameplay Wiki history

Two-revision provenance; the December revision adds Perks, export names and simulation guidance.

↗03

Lua API v2 index

Official Lua 5.4.6 and manager context.

↗04

Official changelog

Assigns Gameplay Attribulator to Live Editor v26.2.2.

↗05