Fields read by the server or the client, or assembled from other files. The description says what the field means and how it acts; below it — where that was established.
Chef\ItemEffectList.txtclient file
Total 4Known 3Derived 0Unused 1
Schema
text table (effects.md §4.3)
Registry level
ready for full
Digest
item effects by upgrade level
Offset
Field
What it is and how it acts
Assembled from
Server readers
Role
Status
Data
—
model (`%x`)
key — item model (+0x48 of the Item.edf record)
effects.md §4.3
—
—
—
known
—
—
column 0
pattern number for the male mesh
effects.md §4.3
—
—
—
known
—
—
column 5
pattern number for the female mesh
effects.md §4.3
—
—
—
known
—
Chef\PatternList.txtclient file
Total 2Known 2Derived 0Unused 0
Schema
text table (effects.md §4.3)
Registry level
ready for full
Digest
item effects by upgrade level
Offset
Field
What it is and how it acts
Assembled from
Server readers
Role
Status
Data
—
pattern number
first number of the line
effects.md §4.3
—
—
—
known
—
—
9 effect numbers
effect number at upgrade levels 0…8; 0 — none
effects.md §4.3
—
—
—
known
—
Unused parameters
Fields that neither the server nor the client reads. For each: why it was decided so and where that was established. The editor keeps their bytes as they are.
Chef\ItemEffectList.txtclient file
Offset
Field
Why unused
Data
—
columns 1–4
pattern numbers for columns 1–4; empty in all corpora (AoP, GU); the studio writes 0
effects.md §4.3 [code]: all calls of 009122A0 (0046E730, 0046EC00, 0046F1D0) and 00910030 pass column 0 or 5